SeaMonkey/StatusMeetings/2016-03-29: Difference between revisions

m
Line 49: Line 49:


=== Release Train ===
=== Release Train ===
* SeaMonkey 2.40 is out, waiting for 2.42.
* SeaMonkey 2.40 is out.
Discussion:
* We are skipping SeaMonkey 2.41
* '''KaiRo:''' We should get a 2.42 release done based on Gecko 45 ESR and then only concentrate on getting nightly to build and run well and ignore everything in between for the moment. We can then do as many 2.42.x security updates based on ESR as we want before we get something out of nightly that is in good shape again.
* Currently planning for 2.42.
* Everyone agreed to skip 2.41.
Previously on Buffy The Vampire Slayer:
* '''Frg:''' Chatzilla locale generation still broken. Frg and Adrian to deal with this.
Carried forward from discussion at last meeting:
* '''IanN''' suggests we should follow the Thunderbird release model, doing releases off the ESR-* branch but also the occasional comm-beta "release". L10N Translations might be problematic however '''rsx11m''' says using ESR would be "safer" with regard to more stability on releases and not having to cope immediately with bustages from mozilla side, but may require some "deal" to get l10n-relevant minor patches into the releases before the next ESR branch is coming. If you have a patch that applies cleanly from comm-beta to comm-esr45, translations should be done already (of course, that's just simple patches such as label changes or adding a checkbox). '''rsx11m''' would go with {comm,mozilla}-esr45 and merge any "safe" patches from comm-beta but that may need some talking to l10n if string changes are involved.
* '''IanN''' suggests we should follow the Thunderbird release model, doing releases off the ESR-* branch but also the occasional comm-beta "release". L10N Translations might be problematic however '''rsx11m''' says using ESR would be "safer" with regard to more stability on releases and not having to cope immediately with bustages from mozilla side, but may require some "deal" to get l10n-relevant minor patches into the releases before the next ESR branch is coming. If you have a patch that applies cleanly from comm-beta to comm-esr45, translations should be done already (of course, that's just simple patches such as label changes or adding a checkbox). '''rsx11m''' would go with {comm,mozilla}-esr45 and merge any "safe" patches from comm-beta but that may need some talking to l10n if string changes are involved.
* '''Adriank''' thinks we need an *own* build infra separate from MoCo. What is needed is a buildbot (Adrian use Jenkins), a Windows, Linux, and OSX virtual machine.
* '''Adriank''' thinks we need an *own* build infra separate from MoCo. What is needed is a buildbot (Adrian use Jenkins), a Windows, Linux, and OSX virtual machine.
* '''Frg:''' Chatzilla locale generation still broken. Frg and Adrian to deal with this.
<br/>
<br/>
* '''SeaMonkey 2.40 final (tracking {{bug|1233615}}) was partially released March 14, 2016'''
* '''SeaMonkey 2.40 final (tracking {{bug|1233615}}) was partially released March 14, 2016'''
<!-- I leave it up to Ratty and ewong to update the rest on the 2.40 release -->
<!-- I leave it up to Ratty and ewong to update the rest on the 2.40 release -->
** Updating failed due to PEBKAC. Currently rectifying this issue.
** Updating failed. Ewong has rectified this issue.
** Seems to work now according to [http://forums.mozillazine.org/viewtopic.php?f=3&t=2994821&start=15 MZ reports].
*** Seems to work now according to [http://forums.mozillazine.org/viewtopic.php?f=3&t=2994821&start=15 reports from Mozillazine].
* Next merges are scheduled for April 18 (beta &rarr; release: April 11).
* Next merges are scheduled for April 18 (beta &rarr; release: April 11).
** comm-release default is now on SM 2.42.
** comm-release default is now on SM 2.42.
Confirmed users
2,595

edits