SeaMonkey/StatusMeetings/2009-12-01: Difference between revisions

m
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<small>[[SeaMonkey:StatusMeetings:2009-11-17|&laquo; last meeting]] | [[SeaMonkey:StatusMeetings|index]]</small>
<small>[[SeaMonkey:StatusMeetings:2009-11-17|&laquo; last meeting]] | [[SeaMonkey:StatusMeetings|index]] | [[SeaMonkey:StatusMeetings:2009-12-15|next meeting &raquo;]]</small>


'''SeaMonkey Meeting Details'''
'''SeaMonkey Meeting Details'''
Line 35: Line 35:
** Need for a form history editor to edit/delete incorrect entries. We can make use of an existing bug ({{Bug|480734}}) to track a native Forms editor.
** Need for a form history editor to edit/delete incorrect entries. We can make use of an existing bug ({{Bug|480734}}) to track a native Forms editor.
** For some users cut&paste isn't working for some Windows 7 users. Specifically, nothing gets pasted ({{Bug|525601}}.
** For some users cut&paste isn't working for some Windows 7 users. Specifically, nothing gets pasted ({{Bug|525601}}.
** This has been traced to the McAfee Site Advisor component of the McAfee Internet Security Suite. A regression range has been identified (2007110103/2007103102). This regression range corresponds to a similar cut and paste problem in Thunderbird 3.0a but not involving McAfee.
*** This has been traced to the McAfee Site Advisor component of the McAfee Internet Security Suite. A regression range has been identified (2007110103/2007103102). This regression range corresponds to a similar cut and paste problem in Thunderbird 3.0a but not involving McAfee.
** The McAfee techs would like a developer from the SeaMonkey side to assist them in tracking down the problem. Do we have someone with the required skillset? Perhaps Neil.
*** The McAfee techs would like a developer from the SeaMonkey side to assist them in tracking down the problem (({{Bug|525601}} Comment 20). Do we have someone with the required skillset? Perhaps Neil.
** We seem to have accidentally migrated from 1.1 all the "browser.toolbars.showbutton.*" preferences when we shouldn't. The most common case appears to be the home button. Our button pref listener are still active because of the Go and Search buttons in the URL bar. Ratty has filed {{bug|531526}} for this.
** See the previous meeting notes for more details: [https://wiki.mozilla.org/SeaMonkey:StatusMeetings:2009-11-17#SeaMonkey_2.0_Final StatusMeetings:2009-11-17#SeaMonkey_2.0_Final]
** See the previous meeting notes for more details: [https://wiki.mozilla.org/SeaMonkey:StatusMeetings:2009-11-17#SeaMonkey_2.0_Final StatusMeetings:2009-11-17#SeaMonkey_2.0_Final]
** BenoitRen notes increasing reports about problems with mailnews, possibly due to shipping code from a beta Thunderbird 3.0.


=== SeaMonkey 2.0.1 ===
=== SeaMonkey 2.0.1 ===


*Should be released in sync with Firefox 3.5.6, [https://wiki.mozilla.org/Releases currently scheduled for December 15].
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0.1%2B open blockers] (3)
*How ready are we for it?
[https://bugzilla.mozilla.org/buglist.cgi?field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=blocking-seamonkey2.0.1%3F blocker requests] (7)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=wanted-seamonkey2.0.1%2B open wanted] (0)
[https://bugzilla.mozilla.org/buglist.cgi?keywords_type=nowords&field0-0-0=flagtypes.name&type0-0-0=equals&value0-0-0=wanted-seamonkey2.0.1%3F wanted requests] (0)
 
* Should be released in sync with Firefox 3.5.6, [https://wiki.mozilla.org/Releases currently scheduled for December 15].
** Even though the SeaMonkey-specific fixes are only some smaller ones, the improved mailnews maturity and the core crash and security fixes sound like they're worth it
* How ready are we for it?
** Blocker nominations need to be triaged, but probably can be put off to 2.0.2.


=== Feature List, Planning ===
=== Feature List, Planning ===
Line 50: Line 59:
* Fixing rate down as we all take a breath after this.
* Fixing rate down as we all take a breath after this.
* Triage rate down from 58 at last meeting.
* Triage rate down from 58 at last meeting.
* We need to do more triaging. We should probably start to look at trashing 1.x-only bugs as well (and see if any still happen on 2.x).


Major wanted/needed features:
Major wanted/needed features:
Line 193: Line 203:
* EOL date for SeaMonkey 1.1?
* EOL date for SeaMonkey 1.1?
** The plans for Gecko 1.8 are rather murky at the moment. KaiRo will probably try to get a clearer view when a 1.8.1.24 will be prepared possibly in December.
** The plans for Gecko 1.8 are rather murky at the moment. KaiRo will probably try to get a clearer view when a 1.8.1.24 will be prepared possibly in December.
* IanN asks can we combine stop and reload buttons?
** Nobody else likes this idea.
* It would be good to have some of the icons that firefox now has for browser, and some more non-default toolbar buttons like "Print Preview". But we need suitable graphics for both themes.
Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083

edits