SeaMonkey/StatusMeetings/2016-05-24: Difference between revisions

 
(8 intermediate revisions by the same user not shown)
Line 37: Line 37:
** '''Callek:''' Regarding the windows systems, sadly no progress yet. I'm hopeful we can get done sooner than later, I'm realistic expecting it won't be  any time soon.
** '''Callek:''' Regarding the windows systems, sadly no progress yet. I'm hopeful we can get done sooner than later, I'm realistic expecting it won't be  any time soon.
** '''Ewong''' will set up a cron job to do semi regular builds on the loaner machine.
** '''Ewong''' will set up a cron job to do semi regular builds on the loaner machine.
** Windows nightly trunk builds are unavailable due to various bugs such as {{Bug|1092468}} and {{Bug|1108970}}. Migrating our [https://bugzilla.mozilla.org/show_bug.cgi?id=1114876 Windows builders to Win2008] and our compiler toolchain to VS2015 would likely solve this and other bustages. ''Ratty''' is currently reviewing these and other patches to make this happen Some patches have already landed.
** Windows nightly trunk builds are unavailable due to various bugs such as {{Bug|1092468}} and {{Bug|1108970}}. Migrating our [https://bugzilla.mozilla.org/show_bug.cgi?id=1114876 Windows builders to Win2008] and our compiler toolchain to VS2015 would likely solve this and other bustages. ''Ratty''' has approved a patch which will update the builders to vs2015U2 so maybe there can be some progress seen soon.
** There are also some upcoming changes to L10n build system in Q1 2015 ({{bug|1107635}}).
** There are also some upcoming changes to L10n build system in Q1 2015 ({{bug|1107635}}).
** en-US trunk hourlies and nightlies are being published again since 2016-04-25 for L32, L64 and Mac but not Windows. Still no new langpacks or localized builds at ftp.m.o.
** en-US trunk hourlies and nightlies are being published again since 2016-04-25 for L32, L64 and Mac but not Windows. Still no new langpacks or localized builds at ftp.m.o.
Line 46: Line 46:
*** OSX64: busted due to {{bug|1260362}}. Yasm 1.2 needs to be installed.  
*** OSX64: busted due to {{bug|1260362}}. Yasm 1.2 needs to be installed.  
*** Linux64 Nightly: busted due to {{bug|1275215}}
*** Linux64 Nightly: busted due to {{bug|1275215}}
*** All trees: Location bar and Back/Forwad buttons broken because of {{bug|1272401}}. Patch is being reviewed now.
** [comm-aurora]
** [comm-aurora]
*** OSX64: busted due to {{bug|1260362}}.
*** OSX64: busted due to {{bug|1260362}}.
Line 61: Line 62:


=== Release Train ===
=== Release Train ===
* Next release will be 2.43 (no ETA yet). Because 2.44 is coming up fast frg will ask ewong if he is able to get out a 2.43 sonn. Otherwise 2.43 might be skipped also.
* Next release will be 2.43 (no ETA yet). Because 2.44 is coming up fast frg will ask ewong if he is able to get out a 2.43 soon. Otherwise 2.43 might be skipped also.
* {{bug|1234012}} will be backed out in a special m-r release branch for Seamonkey 2.43. This seems to cause major problems for Enterprise users in Firefox and may be backed out there too.  
* {{bug|1234012}} will be backed out in a special m-r release branch for Seamonkey 2.43. This seems to cause major problems for Enterprise users in Firefox and may be backed out there too.  
* {{Bug|1231349}} will cause problems building l10n versions. Currently only a workaround exists.
* Backup plan in case we need it is to do some releases off comm-esr45. These would be 2.42.x releases. No current plans until Mozilla suddenly removes full theme support or anything else which would severely break Seamonkey.
* Backup plan in case we need it is to do some releases off comm-esr45. These would be 2.42.x releases. No current plans until Mozilla suddenly removes full theme support or anything else which would severely break Seamonkey.
* Patches which do not concern Thunderbird could be be checked into comm-esr45 after getting approval too.
* Patches which do not concern Thunderbird could be be checked into comm-esr45 after getting approval too.
Line 77: Line 79:
* '''Firefox & Thunderbird Add-on Converter for SeaMonkey''' [http://addonconverter.fotokraina.com/ http://addonconverter.fotokraina.com/]<br>This tool goes a little further beyond simply modifying install.rdf - it also identifies a few more other things in the code that are Firefox or Thunderbird specific and attempts to change them. Of course, not all extensions can be ported so easily to SeaMonkey since there's only so much an automated tool like that can do.
* '''Firefox & Thunderbird Add-on Converter for SeaMonkey''' [http://addonconverter.fotokraina.com/ http://addonconverter.fotokraina.com/]<br>This tool goes a little further beyond simply modifying install.rdf - it also identifies a few more other things in the code that are Firefox or Thunderbird specific and attempts to change them. Of course, not all extensions can be ported so easily to SeaMonkey since there's only so much an automated tool like that can do.
** '''[http://forums.mozillazine.org/memberlist.php?mode=viewprofile&u=217009 Lemon Juice]''' continues to improve his already impressive Addon Converter. The source is now available on GitHub [https://github.com/lemon-juice/addonconverter].
** '''[http://forums.mozillazine.org/memberlist.php?mode=viewprofile&u=217009 Lemon Juice]''' continues to improve his already impressive Addon Converter. The source is now available on GitHub [https://github.com/lemon-juice/addonconverter].
** looking for a better(?) home for extension-converter pages, along with a way to track successful and conversion-failed add-ons, and respective integration into SeaMonkey by add-on or manager overlay [http://forums.mozillazine.org/viewtopic.php?f=40&t=2834855&start=270#p14168717], {{bug|1145026}}.
** We are looking for a better(?) home for extension-converter pages, along with a way to track successful and conversion-failed add-ons, and respective integration into SeaMonkey by add-on or manager overlay [http://forums.mozillazine.org/viewtopic.php?f=40&t=2834855&start=270#p14168717], {{bug|1145026}}.
** Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. -- [[User:Rrbd|Rrbd]] ([[User talk:Rrbd|talk]]) 09:59, 16 August 2015 (PDT)
** Ratty filed {{Bug|1130390}} to add a link on [http://www.seamonkey-project.org/ seamonkey-projects.org] to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
** Ratty filed {{Bug|1130390}} to add a link on [http://www.seamonkey-project.org/ seamonkey-projects.org] to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
** The [http://addonconverter.fotokraina.com/amo-browsing/ AMO Browsing for SeaMonkey] extension, which makes AMO pages a lot more SeaMonkey-friendly, seems mature. (It had 9 successive revisions between 27 September and 3 October, and no change since then.) It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a "built-in extension" besides ChatZilla, DOMi and the like. What do you think? (See also {{bug|1145026|Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane}}; the extension actually does much more than the bug's Summary implies: for instance it gets rid of the stupid "You need Firefox 10 or later" popups.
* The [http://addonconverter.fotokraina.com/amo-browsing/ AMO Browsing for SeaMonkey] extension, which makes AMO pages a lot more SeaMonkey-friendly, is mature. It was developed by LemonJuice (of Add-on Converter fame), and Tonymec, who tested it and now uses it, supports it enthusiastically. The author proposes to add it as a "built-in extension" besides ChatZilla, DOMi and the like. What do you think? (See also {{bug|1145026|Bug 1145026: AMO Add-On-Descriptions: Add link function leading to SeaMonkey add-on-converter and filling URL input pane}}; the extension actually does much more than the bug's Summary implies: for instance it gets rid of the stupid "You need Firefox 10 or later" popups.


=== 2.x (Last, Current, Next) ===
=== 2.x (Last, Current, Next) ===
Line 101: Line 102:
==== 2.41 skipped ====
==== 2.41 skipped ====
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey241&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey241&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey241&type0-0-0=equals&value0-0-0=%3F tracking requests] (5)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey241&type0-0-0=equals&value0-0-0=%3F tracking requests] (8)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.41 targeted] (0)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.41 targeted] (0)
[https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&f1=OP&v6=fixed&o3=equals&list_id=8372932&v3=fixed&resolution=FIXED&o6=notequals&o2=equals&f4=CP&v5=fixed&query_format=advanced&j1=OR&f3=cf_status_seamonkey241&f2=target_milestone&f5=cf_status_seamonkey240&v2=2.41 fixed] (11)
[https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&f1=OP&v6=fixed&o3=equals&list_id=8372932&v3=fixed&resolution=FIXED&o6=notequals&o2=equals&f4=CP&v5=fixed&query_format=advanced&j1=OR&f3=cf_status_seamonkey241&f2=target_milestone&f5=cf_status_seamonkey240&v2=2.41 fixed] (26)


==== 2.42 skipped ====
==== 2.42 skipped ====
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey242&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey242&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey242&type0-0-0=equals&value0-0-0=%3F tracking requests] (5)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey242&type0-0-0=equals&value0-0-0=%3F tracking requests] (8)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.42 targeted] (0)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&target_milestone=seamonkey2.42 targeted] (0)
[https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&f1=OP&v6=fixed&o3=equals&list_id=8372932&v3=fixed&resolution=FIXED&o6=notequals&o2=equals&f4=CP&v5=fixed&query_format=advanced&j1=OR&f3=cf_status_seamonkey242&f2=target_milestone&f5=cf_status_seamonkey241&v2=2.42 fixed] (11)
[https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&f1=OP&v6=fixed&o3=equals&list_id=8372932&v3=fixed&resolution=FIXED&o6=notequals&o2=equals&f4=CP&v5=fixed&query_format=advanced&j1=OR&f3=cf_status_seamonkey242&f2=target_milestone&f5=cf_status_seamonkey241&v2=2.42 fixed] (21)


==== 2.43 planned next release ====
==== 2.43 planned next release ====
<!-- let's maintain two sections, this one for the *upcoming* release -->
<!-- let's maintain two sections, this one for the *upcoming* release -->
* (This should probably also include fixes that landed in 2.41 and 2.42)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey243&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey243&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey243&type0-0-0=equals&value0-0-0=%3F tracking requests] (5)
[https://bugzilla.mozilla.org/buglist.cgi?&field0-0-0=cf_tracking_seamonkey243&type0-0-0=equals&value0-0-0=%3F tracking requests] (5)
Line 149: Line 149:
** Unfortunately nobody knows exactly how addons.mozilla.works because there's no full time developer working on AMO. Ratty was given {{Bug|1009759}} as an example. So now we need someone who knows python+django.
** Unfortunately nobody knows exactly how addons.mozilla.works because there's no full time developer working on AMO. Ratty was given {{Bug|1009759}} as an example. So now we need someone who knows python+django.
** About specific aspects of this problem, see: {{bug|1230796}}, {{bug|1230804}}, {{bug|1230806}} and maybe more.
** About specific aspects of this problem, see: {{bug|1230796}}, {{bug|1230804}}, {{bug|1230806}} and maybe more.
** [Ratty] The url for the discovery pane is set in a pref. Instantbird points the URL to a chrome XUL document. If we do this we don't have to worry about the python stuff.
** [Ratty] The url for the discovery pane is set in a pref. Firefox has switched to https://discovery.addons. Instantbird points the URL to a chrome XUL document. If we do this we don't have to worry about the python stuff. The new Firefox discovery page will not serve up featured addons for SeaMonkey so we are sticking with services.* at least until they stop serving that up.
** {{Bug|1262880}} removed the add-on compatibility check from application update. rsx11m will fix our part in {{Bug|1269133}}
* [Ratty] made some progress to fix {{bug|1222817}} - Restore about:addons UI (Addons Manager) to old appearance. He found some useful ideas from the CSS in https://addons.mozilla.org/en-US/seamonkey/addon/classicish-addon-manager/ but currently doesn't have the time to continue.
** Ratty will look at {{Bug|995095}} 'Move the nsPlacesAutocomplete component to Suite'
* [Ratty] will look at {{Bug|995095}} 'Move the nsPlacesAutocomplete component to Suite'


=== Feature List, Planning ===
=== Feature List, Planning ===
739

edits