SeaMonkey/StatusMeetings/2008-08-12: Difference between revisions

3,286 bytes added , 21 January 2011

m

moved SeaMonkey:StatusMeetings:2008-08-12 to SeaMonkey/StatusMeetings/2008-08-12: / is a much nicer separator :)

KaiRo

Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti

4,083

edits

@@ Line 1: / Line 1: @@
-<small>[[SeaMonkey:StatusMeetings:2008-07-15|&laquo; last meeting]] | [[SeaMonkey:StatusMeetings|index]] |</small>
+<small>[[SeaMonkey:StatusMeetings:2008-07-15|&laquo; last meeting]] | [[SeaMonkey:StatusMeetings|index]] | [[SeaMonkey:StatusMeetings:2008-08-26|next meeting &raquo;]]</small>
 '''SeaMonkey Meeting Details'''
@@ Line 11: / Line 11: @@
 * Feed Discovery -- {{bug|450205}} -- Do we want to hide feed discovery UI as described here for our first alpha build?
+** The next phase of feed work won't be done in time for the alpha.
+** KaiRo: The patch to hide the UI should be in the source tag of the (Alpha) release branch. We should set this blocking+ then so we don't miss it.
+** No objections.
 === SeaMonkey 2 Alpha ===
@@ Line 18: / Line 21: @@
 * {{bug|381157}} download manager (soft blocker)
-** Status/Progress
+** Status/Progress (Not much).
 * {{bug|390025}} kill-wallet (password manager) (soft blocker)
 ** Status/Progress
@@ Line 30: / Line 33: @@
 *** {{bug|444167}}, {{bug|444169}}, {{bug|444170}}, {{bug|445013}} and {{bug|445014}} assigned but no patches yet
 *** {{bug|445015}} not yet assigned
-* blocker triage? shipping target?
+** ETA Unknown/Variable.
+* Shipping target?
+** Standard8: TB 30.b1 code freeze is currently set for 9th September. How about we aim SM 2.0a1 alpha code freeze for that date? We can then send out emails to all those currently doing those bugs saying this is the target date, if you can't manage it, please let us know so we can move things forward so it essentially gives us 4 weeks.
+* Blocker triage?
+** We have 32 blocking? requests to triage.
+** The deadline for triage to be completed should be early enough so we can address all blocking+ bugs before the release.
+** From https://wiki.mozilla.org/Thunderbird:Shredder_a2#Flags "What should block alpha2? Not very much; mostly things that would truly impair usability on a day-to-day basis. dataloss bugs, crashers, and bugs with serious usability impact are likely to qualify."
+** Also see http://www.seamonkey-project.org/dev/review-and-flags#blocking
+** IanN will start the triaging of blockers on behalf of the SM Council.
 === Mercurial ===
 * Any notes/problems?
 ** Notes from mozilla.dev.planning:
 *** Branching for Firefox releases in Mercurial [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/c09eabb27165b50c/91e7a55724de319a]
 *** How do we sign-off on Mercurial based releases' code+locales? [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/edcb45e8be998d00/2de65dec002eb3f3]
+*** Getting L10n builds working again on hg is {{bug|446119}}
+** Missing bonsai-like features are being worked on for the pushlog in {{bug|446119}}
+** Callek: We'll need a way to specify Revision Number/tag for other HG Repo's with our client.py for releases; so a pull of our release tag actually pulls the proper code from <other project>. I'll probably address it with code/bug.
 === Longer-Term SeaMonkey 2 Planning ===
@@ Line 49: / Line 62: @@
 * biesi
 * Callek
+** Completed a buildbot patch that will let us turn win32 and linux unittest boxes green by specifying a leakThreshold to the script, and just last night readied a patch that will allow us to pull DOMi from its new[er] repo (at http://hg.mozilla.org/dom-inspector) rather than have it used in mozilla-central itself.
 * IanN
 ** Mainly been working on pref window migration bugs - coding/reviewing/advising
@@ Line 64: / Line 78: @@
 ** {{bug|428216}} (Toolbar button size/mode control): Addressing Reviews. Getting closer.
 ** {{Bug|449004}} (SeaMonkey Website Install Documentation Needs Updating): Filed on behalf of Roger Fulsom. Part of my attempt to get more end users to contribute to the non-coding parts of the project (e.g. documentation, QA).
-** Modern Theme: We have a volunteer [http://forums.mozillazine.org/memberlist.php?mode=viewprofile&u=44512 Kuden] for /mozapps/. I've asked for a progress report.
+** Modern Theme: We have a volunteer [http://forums.mozillazine.org/memberlist.php?mode=viewprofile&u=44512 Kuden] for /mozapps/. I've asked for a progress report.<br>([[User:Philip Chee|Ratty]] 15:37, 14 August 2008 (UTC)) Update: Kuden says she might have something for us by the end of August.
 * Standard8
 ** Fixed {{bug|327510}} XML Parsing Error: no element found/netError.xhtml on newsgroup msg download timout.
 *** If anyone has time to take a look at the 1.8 issues, that would be useful.
+*** Needs more testing on branch to identify why the patch isn't behaving there.
 ** Currently working on {{bug|449260}} (Replace rdf-driven addressbook popup menus with xbl based one) - reviews and updates in progress - this will lead onto completing
 ** {{bug|408613}} Migrate SeaMonkey addressing preferences pane to new style and rewrite how the AB prefs UI works.
 *** This bug should be quick to do once {{bug|449260}} is completed.
 * stefanh
+** Working on bug {{bug|444411}}.
+** {{Bug|439354}} will turn on unified toolbar on mac by default (with "a -moz-mac-unifiedtoolbar" in pinstripe's toolbar.css). We need to discuss what to do since some items in the theme (grippies and some of the buttons) don't fit too well with a unified toolbar.
+*** Kairo: so, are the problems you mention acceptable for alpha?
+*** stefanh: I think we should turn off unified toolbar until we settled those things it's easily done by adding a rule in communicator/mac/toolbar.css
+*** Kairo: Ok, such visual glitches are not blocking alpha though, so I think we should go with whatever you propose there, probably with review from Mnyromyr who also knows mac stuff.
 === Any other business? ===
+* Mnyromyr: Apropos Mac stuff: I tried to get a grip on a Mac wizard for our 10.4 punycode test failure, but no luck so far ({{bug|447999}}).
+* Callek: Same for that reftest issue that seems to be fine in Firefox but not SeaMonkey.
+* stefanh: filed {{bug|450257}} for the move of our security pref panels to comm-central I don't think I'll be able to do that, though. Looks like a bug for Kairo (moving files around).
 * bz: hijacked SeaMonkey {{bug|113934}} (Drag & Drop tabs between browser windows back end) and morphed it into a Firefox/backend bug, so he filed {{Bug|449728}} for our front end. Since there is no SM 2.0 tracking bug I'm raising it here to see if we want this for SM 2.0.

SeaMonkey/StatusMeetings/2008-08-12: Difference between revisions

SeaMonkey/StatusMeetings/2008-08-12 (view source)

Revision as of 01:01, 21 January 2011