MozillaWiki

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

Page Discussion

SeaMonkey/StatusMeetings/2009-12-01 (view source)

Revision as of 01:15, 21 January 2011

66 bytes added ,  21 January 2011
m
moved SeaMonkey:StatusMeetings:2009-12-01 to SeaMonkey/StatusMeetings/2009-12-01: / is a much nicer separator :)
 
(12 intermediate revisions by 5 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 13: Line 13:


'''NEW'''
'''NEW'''
* '''KaiRo''' to add to the known issues page additional items from the SeaMonkey 2.0 Final/Feedback section from the previous meeting.
* '''KaiRo''' to add to the known issues page additional items from the SeaMonkey 2.0 Final/Feedback section from the previous meeting. Somebody needs to go through the items and sort out what needs to be added.
* '''Ratty''' to draft out some messages to encourage extension authors to make their extensions compatible with SeaMonkey 2.0. Once the Council approves them, we can forward to AMO for dissemination. The messages should target two groups:
* '''Ratty''' to draft out some messages to encourage extension authors to make their extensions compatible with SeaMonkey 2.0. Once the Council approves them, we can forward to AMO for dissemination. The messages should target two groups:
** Existing SeaMonkey extensions that haven't been upgraded to 2.0.
** Existing SeaMonkey extensions that haven't been upgraded to 2.0.
** Firefox and Thunderbird extension authors encouraging them to make their extensions compatible with SeaMonkey 2.0.
** Firefox and Thunderbird extension authors encouraging them to make their extensions compatible with SeaMonkey 2.0.
** Ratty filed AMO {{Bug|527919}} for this. Once the messages are approved, they should be forwarded to AMO and they will take care of sending these out to extension developers.
** Ratty filed AMO {{Bug|527919}} for this and attached some drafts. Once the messages are approved, they should be forwarded to AMO and they will take care of sending these out to extension developers.


'''OPEN'''
'''OPEN'''
* Get permission from Google to use their geolocation JSON service '''[KaiRo]'''. Contact at Google says: "We don't have a good estimate for when GLS will be opening up more broadly, but I will be sure to let you know when we take that step.  Sorry that I can not be more specific at this time." - We can only wait right now.
* Get permission from Google to use their geolocation JSON service '''[KaiRo]'''. Contact at Google says: "We don't have a good estimate for when GLS will be opening up more broadly, but I will be sure to let you know when we take that step.  Sorry that I can not be more specific at this time." - We can only wait right now.
** KaiRo emailed Google again more than 8 weeks ago and again 5 weeks ago, no reply yet, even though the MoCo geolocation contact has poked the Google contact as well.
** KaiRo emailed Google again more than 8 weeks ago and again 5 weeks ago, no reply yet, even though the MoCo geolocation contact has poked the Google contact as well.
** KaiRo will try to get this process restarted.


'''CLOSED'''
'''CLOSED'''
Line 29: Line 30:
* '''Shipped on October 27'''!
* '''Shipped on October 27'''!
* [https://bugzilla.mozilla.org/buglist.cgi?product=Core&product=MailNews+Core&product=SeaMonkey&product=Other+Applications&keywords=fixed-seamonkey2.0 167 fixed-seamonkey2.0 bugs] (all post 2.0b2)!
* [https://bugzilla.mozilla.org/buglist.cgi?product=Core&product=MailNews+Core&product=SeaMonkey&product=Other+Applications&keywords=fixed-seamonkey2.0 167 fixed-seamonkey2.0 bugs] (all post 2.0b2)!
* Pushed venkman perf hit and GetDefaultReader to 2.0.1.
 
* 2.0 has 19 official languages including en-US, as well as a beta/unofficial Turkish version (requested by localizer due to incomplete L10n). More to come for 2.0.1.
* What are we going to do with regards to 1.9.1.6?
** 2.0.1 will be based on 1.9.1.6 now as 1.9.1.5 was a crash-fixer released on Thursday 5th November, and KaiRo did not have enough time to generate a release that week.
** Firefox is in slushy code freeze and is on schedule for a mid-December release.
* Feedback
* Feedback
** Many positive messages.
** The new Password and Form Managers seem to be hard for people to grasp. There is an existing documentation bug, {{Bug|463903}} for form autocomplete.
** Also many posts with problems, a few common threads among those:
** 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.
*** Failure to launch when installed over 1.x - can we do something with removed-files?  Ratty has filed {{Bug|526202}} on this issue.
** For some users cut&paste isn't working for some Windows 7 users. Specifically, nothing gets pasted ({{Bug|525601}}.
**** Components dumped by extensions into the application/components/ directory are definitely a problem.
*** 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.
*** Some things already mentioned in Known Issues.
*** 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.
*** Profile migration failures - not sure how to diagnose these. Things like missing all passwords in migration are strange, but hard to debug especially if we don't have access to the users system.
** 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.
*** The migration experience for people with multiple profiles is sub-optimal and we need to find some way of making this better.
** 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]
*** Quicklaunch from SeaMonkey 1.1.x still enabled, need to see if it's possible/wanted to disable Quicklaunch during SeaMonkey 2 setup (should not be that difficult). IanN keep an eye on this issue ({{bug|526204}}).
** BenoitRen notes increasing reports about problems with mailnews, possibly due to shipping code from a beta Thunderbird 3.0.
*** The new Password and Form Managers seem to be hard for people to grasp, do we need docs on those so we can point people to them? BenoitRen to file a bug and to contact people who can potentially help to do the documentation. There is an existing bug, {{Bug|463903}} for form autocomplete.
**** One immediate issue is for a form history editor to edit/delete incorrect entries. There is a Form History Manager extension for SeaMonkey 2.0 that can do this. But we need this as a native function of SeaMonkey for a better user experience. Perhaps we can use that extension as a starting point. 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}}.
**** This has been traced to the McAfee Site Advisor component of the McAfee Internet Security Suite (also shipped with other McAfee products and with Yahoo security suites that are rebranded McAfee). 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.
*** Some users upgrading from 1.1 who never used a master password are now being prompted at every startup for a (non-existent) password. In 1.1 it was possible to set a master password but not use it if the preferences were set that way. Some users might have accidentally set a master password and forgot about it and this could have been migrated to the 2.0 profile. Unfortunately in 2.0 if a master password is set then it is used.
*** 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''' to file a bug to fix or workaround the problem in 2.0.1 for already migrated profiles. Also possibly get someone to look at the profile migrator code to not migrate these preferences.


=== 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 63: 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 136: Line 133:
==== Misak  ====
==== Misak  ====
Working on:
Working on:
* All latest sessionstore stuff (all of them ported, many of them doesn't have bug numbres yet), waiting to council decision about {{Bug|530735}}
* {{Bug|524369}} Port {{Bug|491168}} [Allow SessionStore to save/restore referrer field] to SeaMonkey.
* {{Bug|524369}} Port {{Bug|491168}} [Allow SessionStore to save/restore referrer field] to SeaMonkey.
* {{Bug|530735}} Consider to use same undo close tab mechanism as in Firefox.
* {{Bug|530735}} Consider to use same undo close tab mechanism as in Firefox.
Line 177: Line 175:


==== sgautherie ====
==== sgautherie ====
*Fixed SeaMonkey bugs:
**{{bug|531292}} Port |Bug 530723 - Disable ipc, since it requires libxul and we can't build that way (yet)| to SeaMonkey
*See also
**https://wiki.mozilla.org/Thunderbird/StatusMeetings/2009-11-24#sgautherie
**https://wiki.mozilla.org/Thunderbird/StatusMeetings/2009-12-01#sgautherie
*<i>And working on other areas... like</i>
**infrastructure to run tests
**filing bugs for leaks in (TUnit) tests
**doing a Windows comm-central-trunk SeaMonkey unit test build, filing bugs as needed; looking forward to an official build when enough new buildbot slaves can be enabled ({{bug|464325}} follow-ups).


==== Standard8 ====
==== Standard8 ====
Line 196: 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.
KaiRo
Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/186729...278886"