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

SeaMonkey/StatusMeetings/2016-05-24 (view source)

Revision as of 15:35, 24 May 2016

1,050 bytes added , 24 May 2016

→‎status meeting part 1

Frg

647

edits

@@ Line 10: / Line 10: @@
 == Agenda ==
-* Who's taking minutes? -> '''TBD'''
+* Who's taking minutes? -> '''frg'''
 * Nominees for Friends of the Fish Tank:
-** '''TBD'''
+** '''frg''' for doing a bunch of bustage fixes lately
 === Action Items ===
@@ Line 19: / Line 19: @@
 '''NEW'''
-* [Ratty:] '''rkent''' has stated that he will not uplift the suite parts of changesets to SeaMonkey branches that are perma-CLOSED unless he gets a perma-APPROVED from SeaMonkey team. Since he is the TB module owner and a TB-driver I think it's a reasonable request.
+* [Ratty:] '''rkent''' has stated that he will not uplift the suite parts of changesets to SeaMonkey branches that are perma-CLOSED unless he gets a perma-APPROVED from SeaMonkey team. Since he is the TB module owner and a TB-driver I think it's a reasonable request. '''approved by meeting participants'''
+*  Google just announced V4 of the safebrowsing api. No actions currently needed.
 * &mdash;
 '''OPEN'''
 * Google API key for Safe Browsing. Ewong/Callek about getting it loaded onto the build machines.
 ** Per {{bug|903439#c10}}, ewong has a Google API key (stating that for Geolocation service). Safe Browsing key is apparently still missing.
 * '''IanN''' to review members mailing-list and council appointments (IanN to talk to mcsmurf about members list)
 ** TODO: Add Adrian Kalla to RelEng team.
@@ Line 60: / Line 61: @@
 === Release Train ===
-* Next release will be 2.43 (no ETA yet).
+* 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.
-* All fixes for 2.43 are in comm-release but some patches for building Lightning 4.8b1 were not checked in. Ratty will inquire and will check them in if required.
 * {{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.
 * 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.
@@ Line 74: / Line 74: @@
 * There is still no matching Lightning version for 2.43 and since Thunderbird skipped the TB 46.0 beta, there may not be any (Lightning 4.8b1).
 ** '''[Fallen]''': If you generate one using <tt>--enable-calendar</tt>, which produces all the locales similar to how this candidates directory looks like: http://ftp.mozilla.org/pub/calendar/lightning/candidates/4.5b1-candidates/ then I can upload that to AMO.
-** Trunk is now built with <tt>--enable-calendar</tt>, see [[#Fixed Stuff Since Last Meeting]] above.
-** some patches which only landed on the Thunderbird 45.1b1 release branch may still need to be transplanted to comm-release default.
 * We are looking for a new place to host the [[SeaMonkey/AddonCompat|Addon Compatibility Listings]] for the Add-on Converter in order to make it easy to maintain and to serve as the main database for the AMO browsing extension in the future. The details are in [http://forums.mozillazine.org/viewtopic.php?p=14168717#p14168717 this post].
 * '''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.
@@ Line 83: / Line 81: @@
 ** 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.
-* Adrians patch in {{Bug|516026}} 'Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled' is now ready for check-in. The first Seamonkey version which will come with Lightning is 2.44.
 === 2.x (Last, Current, Next) ===
@@ Line 94: / Line 91: @@
 * See [[SeaMonkey/StatusMeetings/Basics|Basics]] page for the usual reminders.
-==== 2.40 ====
+==== 2.40 current release ====
 <!-- let's maintain two sections, this one for the *current* release -->
 [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&field0-0-0=cf_tracking_seamonkey240&type0-0-0=equals&value0-0-0=%2B open tracking] (0)
@@ Line 102: / Line 99: @@
 * [http://www.seamonkey-project.org/releases/seamonkey2.40/ SeaMonkey 2.40 Release Notes]
-==== 2.43 ====
+==== 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?&field0-0-0=cf_tracking_seamonkey241&type0-0-0=equals&value0-0-0=%3F tracking requests] (5)
+[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)
+==== 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?&field0-0-0=cf_tracking_seamonkey242&type0-0-0=equals&value0-0-0=%3F tracking requests] (5)
+[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)
+==== 2.43 planned next 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)
@@ Line 108: / Line 117: @@
 [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?resolution=---&target_milestone=seamonkey2.43 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_seamonkey243&f2=target_milestone&f5=cf_status_seamonkey242&f6=cf_status_seamonkey241&v2=2.43 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_seamonkey243&f2=target_milestone&f5=cf_status_seamonkey242&v2=2.43 fixed] (11)
 ==== 2.Next ====