MozillaWiki

SeaMonkey/StatusMeetings/2011-07-26: Difference between revisions

Page Discussion

SeaMonkey/StatusMeetings/2011-07-26 (view source)

Revision as of 17:24, 27 July 2011

2,714 bytes added ,  27 July 2011
→‎Needing help, Unowned, Stalled
 
(16 intermediate revisions by 4 users not shown)
Line 31: Line 31:


=== Release Train ===
=== Release Train ===
* SeaMonkey will directly go to the permanent repositories, i.e. -aurora, -beta in addition to -central. Miramar is a Thunderbird-only release branch (as is comm-2.0 for SeaMonkey).
* For comm-aurora, we also should regard strings there as much frozen as possible. In the future, string freeze is the uplift from central to aurora, which matches Firefox.
* For comm-aurora, we also should regard strings there as much frozen as possible. In the future, string freeze is the uplift from central to aurora, which matches Firefox.
* If we have any actual fixes that don't need L10n changes (not enhancements) on central but not beta, they should go there if possible.
* If we have any actual fixes that don't need L10n changes (not enhancements) on central but not beta, they should go there if possible.
* SeaMonkey comm-aurora and comm-beta are buildable and tinderbox has run tests against them.
* Bug authors and/or reviewers should request relevant approvals for comm-aurora/beta when necessary.
* Callek is working on getting comm-aurora and comm-beta on MXR ({{bug|653424}}).
* Callek is working on getting comm-aurora and comm-beta on MXR ({{bug|653424}}).
* The correct version numbers are now on the release train.
* First beta of 2.3 is due out shortly and then we'll have about 3 weeks to release. Target release date is 16th August.
* First beta of 2.3 is due out shortly and then we'll have about 3 weeks to release. Target release date is 16th August.
* Bug authors have been doing a fairly good job of requesting relevant approvals for the comm-aurora/beta.


=== Extensions Compatibility Tracking ===
=== Extensions Compatibility Tracking ===
Line 52: Line 49:
** ''The FAQ should be version-agnostic and have version updates mentioned in it so Jens or whoever won't need to keep changing the version numbers.''
** ''The FAQ should be version-agnostic and have version updates mentioned in it so Jens or whoever won't need to keep changing the version numbers.''
* KaiRo created a [[SeaMonkey/Features|SeaMonkey Features]] page and sub-pages for all those that are in development.
* KaiRo created a [[SeaMonkey/Features|SeaMonkey Features]] page and sub-pages for all those that are in development.
* The whole FAQ/AddonCompat information needs to be re-thought with versions in mind but InvisibleSmiley lacks the time to do it. It's a wiki so we can try to offload it. Ratty suggests involving imput from seamonkey-members and/or mozilla.support.seamonkey.


=== SeaMonkey 2.2 ===
=== SeaMonkey 2.2 ===
Line 66: Line 64:
** 2.0->2.2 is a major update (MU) and is online now, too.
** 2.0->2.2 is a major update (MU) and is online now, too.
* 2.2 had ~43300 ADU yesterday, 112457 downloads so far.
* 2.2 had ~43300 ADU yesterday, 112457 downloads so far.
** vs. 63682 on 2.0 (and 4437 on 2.1) so about 20k have migrated from 2.0 to 2.2 in the last week.
* The release notes should also mention (or provide a link to) any fixed security issues in order to support our mantra that you need to install updates to stay secure.
* The release notes should also mention (or provide a link to) any fixed security issues in order to support our mantra that you need to install updates to stay secure.


==== Follow-ups and Issues ====
==== Follow-ups and Issues ====
* Lost Bookmarks {{Bug|673474}} and Cookies {{Bug|673672}} on auto-update from 2.0.14 to 2.2.
* Lost Bookmarks {{Bug|673474}} and Cookies {{Bug|673672}} on auto-update from 2.0.14 to 2.2.
** Bookmarks can be re-imported from bookmarks.html.
* A XUL Core bug causing symptoms like:
* A XUL Core bug causing symptoms like:
** {{Bug|671192}} Command "Paste without Formatting" in message window is missing.
** {{Bug|671192}} Command "Paste without Formatting" in message window is missing.
** {{Bug|672258}} Wrong context menu can be shown if two different windowtypes have the same contextmenu id and xul cache is enabled.
** {{Bug|672258}} Wrong context menu can be shown if two different windowtypes have the same contextmenu id and xul cache is enabled.
** IanN is testing out a workaround suggested by Neil for the context menu issue, the core bug is still there though, but only we seem to be exposing it at the moment.
* Regression in Addressbook ({{Bug|671251}} Cannot drag & drop contacts to another address book) [fixed].
* Regression in Addressbook ({{Bug|671251}} Cannot drag & drop contacts to another address book) [fixed].
* Regressions in the Mail Advanced Search Window ({{Bug|671605}} Search window does not allow to open second message from result list) [fixed].
* Regressions in the Mail Advanced Search Window ({{Bug|671605}} Search window does not allow to open second message from result list) [fixed].
* Users are unhappy about various UX and usability issues with the new Data Manager.
* Users are unhappy about various UX and usability issues with the new Data Manager.
** Ratty proposes that until all the major pain points are addressed, links to the old individual managers be established (probably from the various Data Manager panes).
** Ratty proposes that until all the major pain points are addressed, links to the old individual managers be established (probably from the various Data Manager panes).
* [InvisibleSmiley] We need to try harder to fix regressions ASAP. I feel there is still too much delay. IMO regressions from the last stable version need to be addressed with top priority, especially in light of the rapid release train.


=== SeaMonkey 2.3 ===
=== SeaMonkey 2.3 ===
Line 84: Line 86:
[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&target_milestone=seamonkey2.3 fixed] (14)<br>
[https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&target_milestone=seamonkey2.3 fixed] (14)<br>


SeaMonkey 2.3 Beta 1 will probably be released tomorrow Wednesday 27th July.
* SeaMonkey 2.3 Beta 1 will probably be released tomorrow Wednesday 27th July.
* The release date for 2.3 final is still about 16th August.
 
Several breakages (AB, opening MailNews search results) have only been fixed after 2.3b1 was tagged. Should we respin?
* [Kairo] I'm against a respin, that's what a b2 is for and we'll need one anyhow.
* [IanN] My preference is that the b1 release notice, mentions the known issues.


Further 2.x scheduling
Further 2.x scheduling
Line 134: Line 141:
* {{Bug|87098}} [SeaMonkey] Delete key should delete location bar history list entry.
* {{Bug|87098}} [SeaMonkey] Delete key should delete location bar history list entry.
** Note: Our location bar history doesn't and can't use autocomplete at all.
** Note: Our location bar history doesn't and can't use autocomplete at all.
* {{Bug|515734}} Individual SeaMonkey components are not properly handled by the Windows 7 taskbar.
* {{Bug|654009}} Reply to list: automatically determine From: address
** Note: The actual task here is to port {{Bug|45715}} "Reply to List" [button/(context) menu item]


=== Roundtable - Personal Status Updates  ===
=== Roundtable - Personal Status Updates  ===
Line 149: Line 159:
* {{Bug|668724}} {{Bug|654152}} broke the ability of all-locales to be read without specifying an path on web.
* {{Bug|668724}} {{Bug|654152}} broke the ability of all-locales to be read without specifying an path on web.
* {{Bug|668744}} Update from 2.0 leaves behind some files in some locales.
* {{Bug|668744}} Update from 2.0 leaves behind some files in some locales.
* {{Bug|672100}} comm-miramar nightly builds should be labeled 1.0b5 or 1.0b5pre instead of 1.0b4pre  
* {{Bug|672100}} [lightning] comm-miramar nightly builds should be labeled 1.0b5 or 1.0b5pre instead of 1.0b4pre  
* {{Bug|672441}} Perform checkdisk and check results from cn-sea-qm-win2k3-01.nl.mozilla.org VM.
* {{Bug|672441}} Perform checkdisk and check results from cn-sea-qm-win2k3-01.nl.mozilla.org VM.
* {{Bug|672640}} [lt] SeaMonkey 2.0 ? 2.2 Major upgrade billboard l10n (Patch by Rimas Kudelis).
* {{Bug|672640}} [lt] SeaMonkey 2.0 ? 2.2 Major upgrade billboard l10n (Patch by Rimas Kudelis).
Line 162: Line 172:
** {{bug|512378}} - Port |Bug 506985 - remove java-specific preferences from Firefox UI, hidden prefs| to SeaMonkey 2.1
** {{bug|512378}} - Port |Bug 506985 - remove java-specific preferences from Firefox UI, hidden prefs| to SeaMonkey 2.1
** {{bug|513895}} - Audit preference panes for duplicate stylesheets
** {{bug|513895}} - Audit preference panes for duplicate stylesheets
** {{bug|537153}} - message-id context lacks accesskeys
** {{bug|599731}} - Move "Recently Closed" menus to Go menu
** {{bug|599731}} - Move "Recently Closed" menus to Go menu
** {{bug|621042}} - Advanced Account Settings should mention account name
** {{bug|621042}} - Advanced Account Settings should mention account name
Line 167: Line 178:
** {{bug|635179}} - Expose browser.zoom.siteSpecific to preferences GUI
** {{bug|635179}} - Expose browser.zoom.siteSpecific to preferences GUI
** {{bug|668723}} - Update removed-files.in for bug 643816
** {{bug|668723}} - Update removed-files.in for bug 643816
** {{bug|670652}} - Audit preference stylesheets for duplicate stylesheets.
** {{bug|672101}} - Add browser.zoom.siteSpecific pref to help.
** {{bug|672101}} - Add browser.zoom.siteSpecific pref to help.


*'''Checkin-needed''':
*'''Checkin-needed''':
** {{bug|537153}} - message-id context lacks accesskeys
** {{bug|670652}} - Audit preference stylesheets for duplicate stylesheets.


*'''Needs Review''':
*'''Needs Review''':
Line 228: Line 238:


==== KaiRo ====
==== KaiRo ====
*As usual, [http://home.kairo.at/blog/ my blog] has more detailed status about my work, and [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/KaiRo/posts Mozilla Status Board Posts] also tell about my next planned steps.
* After quite some discussions, did a patch for support of bare IPv6 addresses in Data Manager ({{bug|665826}}) with some additions that also fixes potentially different but similar problems (like {{bug|635783}}). I hope this can even still land for SeaMonkey 2.3 in the current beta cycle.
* I also worked on website storage support ({{bug|588415}}), but I didn't get around yet to finish a good test for that, so people still need to wait for an official patch and add-on update.
* Discussed and somewhat-reviewed rsx11m's great work on more flexible page zoom levels ({{bug|621823}}). Nice to see other people now fixing those corners where I had to take shortcuts in heavy-lifting porting work I did for SeaMonkey.
* [http://home.kairo.at/blog/2011-07/representing_mozilla_as_sponsor_of_sotm Represented Mozilla at the SotM-EU conference]
*As usual, [http://home.kairo.at/blog/ my blog] has more detailed status about my activities, and [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/KaiRo/posts Mozilla Status Board Posts] also tell about my next planned steps - both including my non-SeaMonkey Mozilla work as well.


==== mcsmurf ====
==== mcsmurf ====
Line 277: Line 291:


=== Any other business?  ===
=== Any other business?  ===
'''[Ratty] How are we going to deal with e10s? I see stuff starting to land in mozilla/browser/ (preffed off).'''
* [InvisibleSmiley] given that Neil doesn't like ifdefs we'd probably have to hold off until something lands for good (preffed on).
* [Ratty] Do we have a plan going forward. Or are we just going to wing it on a prayer?
* [IanN] I think it would have to be discussed with TB crowd.
* In theory, any UI/widget changes will impact both us and TB but only if that UI needs to communicate with a website that sits in a content process. On the browser side, that's a lot, on the mailnews side, not so much.
* [IanN] Well I'm hoping Neil will have a good grasp of it (or at least better than me).
Jhatlak
639

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/333365...334019"