SeaMonkey/StatusMeetings/2015-09-15: Difference between revisions

m
My cat is sad because my other cat has returned bedraggled from a wild night out, having lost all of his possessions.
m (My cat is sad because he's been honest with himself about how he's divided his time recently & it's not looking good.)
m (My cat is sad because my other cat has returned bedraggled from a wild night out, having lost all of his possessions.)
 
(8 intermediate revisions by 3 users not shown)
Line 11: Line 11:
* Who's taking minutes? -> '''TBD'''
* Who's taking minutes? -> '''TBD'''
* Nominees for Friends of the Fish Tank:
* Nominees for Friends of the Fish Tank:
** '''ewong'''
** '''ewong''' for all the hard work getting 2.35 out of the door.


=== Action Items ===
=== Action Items ===
Line 21: Line 21:
'''OPEN'''
'''OPEN'''
* {{Bug|1198340}} The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
* {{Bug|1198340}} The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
** 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.
* {{bug|1121281}} tracks the RelEng automation migration off CVS. Everything is now in a single repo, patches for using that new repo are awaiting a review from Callek.
* {{bug|1121281}} tracks the RelEng automation migration off CVS. Everything is now in a single repo, patches for using that new repo are awaiting a review from Callek.
'''CLOSED'''
'''CLOSED'''
Line 34: Line 35:
** For various reasons we don't have a working SeaMonkey Treeherder.
** For various reasons we don't have a working SeaMonkey Treeherder.
** wrt {{bug|1155011}}, we already have a Soccoro token.  The patches on {{bug|1155013}} require approval and then pushed and the work-around patches backed out.
** wrt {{bug|1155011}}, we already have a Soccoro token.  The patches on {{bug|1155013}} require approval and then pushed and the work-around patches backed out.
* [1st September 2015]
* [15th September 2015]
** All trees:
** All trees:
*** Windows platform still busted due to needing Win2008R2 installed.
*** Windows platform still busted due to needing Win2008R2 installed.
*** We have a loaner which ewong is working on (see [https://blog.seamonkey-project.org/2015/07/06/seamonkey-win32-trunk-2-39a1-nightly/ blog] for more information).
*** We have a loaner which ewong is working on (see [https://blog.seamonkey-project.org/2015/07/06/seamonkey-win32-trunk-2-39a1-nightly/ blog] for more information).
** comm-central & comm-aurora:
** comm-central & comm-aurora:
*** All platforms: Busted due to {{bug|1190256}}. {{bug|1190773}} covers the plan to fix it.
*** All platforms: Busted due to {{bug|1190256}} and {{bug|1187222}}.
** comm-release:
*** All platforms: Possibly bustage due to (early?) merge of m-b to m-r.


* See [[SeaMonkey/StatusMeetings/RelEng|RelEng]] page for the RelEng status history.
* See [[SeaMonkey/StatusMeetings/RelEng|RelEng]] page for the RelEng status history.
Line 48: Line 51:


=== Release Train ===
=== Release Train ===
* SeaMonkey 2.33.1 was released on 23 March and is the most recent release.
** there were 15 [https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox37.0.1 security fixes] (5 of which critical) in the Gecko 37 cycle
** there were 13 [https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox38 security fixes] (5 of which critical) in the Gecko 38 cycle
** there were 13 [https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox39 security fixes] (4 of which critical) in the Gecko 39 cycle (all but one also affected and fixed for 38.1.0 ESR)
** there were 14 [https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox40 security fixes] (4 of which critical) in the Gecko 40 cycle (all but 3, one of which critical, also affected and fixed for 38.2.0 ESR)
** contributed trunk/aurora builds are available for testing, see {{bug|1169140}} and [http://forums.mozillazine.org/viewtopic.php?f=42&t=2939531 Contributed SeaMonkey Win32 builds for testing]
** There are some builds up on Google Drive which Ratty has uploaded to [http://seamonkey.callek.net/contrib/ http://seamonkey.callek.net/contrib/].
** obviously, this can't be an acceptable permanent solution...
* Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling]
* Useful Firefox Release Schedule link: [https://www.google.com/calendar/embed?src=bW96aWxsYS5jb21fZGJxODRhbnI5aTh0Y25taGFiYXRzdHY1Y29AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Releases Scheduling]
** merge day was 10 August as scheduled
** merge day was 10 August as scheduled
* SeaMonkey 2.35 release:
* SeaMonkey 2.35 release:
** (ewong) is expected this week, along with, hopefully, 2.38 beta. Due to certificate server issues, we need to do a beta release from 2.38 at the latest (2.39 would have problems).
** Released September 3rd 2015.
 
* SeaMonkey 2.38b1 release:
==== SeaMonkey 2.35 Release ====
** Released September 7th 2015.
* <s>We plan to release SeaMonkey 2.35 asap in August</s>. We missed this deadline but should have a release this week (September).
* The one week early migration on the mozilla trees seems to be intentional. Callek thought we had another week, but doubts we'll get another 38 beta.
** For windows builds, we have a loaner win machine from Mozilla for us (i.e. ewong) to do manual window builds.
** (ewong): Suggesting early September, but we shall see.
 
===== ewong =====
===== ewong =====
* I have done nothing on the Nightlies/Aurora as I've been concentrating on getting Win32 builds and repacks done.
* Started doing nightlies again on the Win32, but due to the fact that they need to be triggered manually, 'nightlies' would be considered a misnomer. "Regularlies" would probably be a better word. Maybe "somewhat regularly".
** The Win32 2.35 release builds was completed on Friday (28th August 2015).
** The 2.35 l10n Win32 repacks were done on late Sunday/Early Monday (30th/31st August 2015)
*** The busted l10n linux/osx repacks (ca, fi, ja(linux), ja-JP-mac(osx), sv-SE, pt-PT) were retriggered on Monday 31st August 2015.


=== Extensions and Plugins Compatibility Tracking ===
=== Extensions and Plugins Compatibility Tracking ===
Line 114: Line 103:


==== 2.Next ====
==== 2.Next ====
* '''We have official permission to use the Firefox FxA 2.0 sync servers!''' We need someone to work on porting sync 2.0 over to replace legacy sync code. The finer details of how are so far unknown, but we should have a usable solution before legacy sync is turned off. See: [http://blog.swarnava.in/2014/02/new-firefox-sync-has-landed-in-firefox.html New Firefox Sync has landed in Firefox Nightly]. Tracked in:
** {{Bug|998807}} Sync account creation or device pairing fails with exception in BrowserIDManager.
** {{Bug|1003434}} Add support for about:sync-progress.
* Stalled. Needs a kick.
* Stalled. Needs a kick.
** {{Bug|815954}} Click-to-Play: Port {{Bug|812562}} (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
** {{Bug|815954}} Click-to-Play: Port {{Bug|812562}} (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
Line 122: Line 114:
<!--Please update-->
<!--Please update-->
* Mozilla-central bugs that affect us:
* Mozilla-central bugs that affect us:
** Change to Safe Browsing
** Changes to Safe Browsing
** Change of printing API {{bug|1146454}} needs to be ported, immediate bustage was fixed in {{bug|1190344}}.
** Change of printing API {{bug|1146454}} needs to be ported, immediate bustage was fixed in {{bug|1190344}}.
*** IanN is working on migrating comm-central to the new API [{{Bug|1195863}}].
*** IanN is working on migrating comm-central to the new API [{{Bug|1195863}}].
Line 132: Line 124:
*** further work to separate function from style in CSS for about:privatebrowsing in {{bug|1178008}} ''(3rd-party themes)''
*** further work to separate function from style in CSS for about:privatebrowsing in {{bug|1178008}} ''(3rd-party themes)''
*** '''Ratty''' restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [{{Bug|1192276}}]
*** '''Ratty''' restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [{{Bug|1192276}}]
** Our front end Sync UI needs to be updated as the old backend has gone away. See: [http://blog.swarnava.in/2014/02/new-firefox-sync-has-landed-in-firefox.html New Firefox Sync has landed in Firefox Nightly]. Tracked in:
*** {{Bug|998807}} Sync account creation or device pairing fails with exception in BrowserIDManager.
*** {{Bug|1003434}} Add support for about:sync-progress.
<!-- *** '''We have official permission to use the Firefox FxA 2.0 sync servers!''' -->
** A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
** A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
** {{Bug|566746}} (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
** {{Bug|566746}} (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
Line 165: Line 153:
***  '''FIXED''' has landed, with UI seen in non-release builds only
***  '''FIXED''' has landed, with UI seen in non-release builds only
*** but uncertain if it does anything useful to be tested
*** but uncertain if it does anything useful to be tested
* Our in content help text is badly outdated. We should import the current xhtml files into some sort of database which can then output both a set of web pages as well as the xhtml files that populate our current help content.


=== Roundtable - Personal Status Updates ===
=== Roundtable - Personal Status Updates ===
Line 172: Line 161:
==== Callek ====
==== Callek ====
==== ewong ====
==== ewong ====
* 'Fought' to release SeaMonkey 2.35 and 2.38b1.
* Trying to fix the plethora of bustages, namely:
** {{bug|1187222}} - Supporting building with GTK3 in suite/
==== IanN ====
==== IanN ====
* Usual testing, reviewing, commenting and approving.
* Usual testing, reviewing, commenting and approving.
Confirmed users
2,595

edits