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

SeaMonkey/StatusMeetings/2016-03-15 (view source)

Revision as of 10:46, 15 March 2016

675 bytes removed , 15 March 2016

m

→‎Release Train

Philip Chee

Confirmed users

2,595

edits

@@ Line 52: / Line 52: @@
 === Release Train ===
-* {{Bug|1213721}} is a tracking bug for migration from ftp.m.o to S3 for firefox and thunderbird. There's a *scary* long list of dependent bugs over there.
+* Looks like ewong has managed to push 2.40 to the release servers at least for 2.40.
-** How close were our staging scripts to Thunderbird's prior to the S3 migration? They were relatively divergent, primarily because we don't have signing infrastructure and Thunderbird's infra uses MoCo firefox infra, and gets a lot of process for free. We should also consult Fallen to see how Thunderbird did the migration and what sort of issues cropped up.
+Carried forward from discussion at last meeting:
-** '''Adrian Kalla''' is still producing his localized builds. Ratty suggests that we should put out a notice on the default SM start page to tell people where they can download the latest 2.4x release builds (Mozilla-release is currently at Firefox 45 which corresponds to SeaMonkey 2.42).
+* '''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.
 <br/>
 * SeaMonkey 2.39 was released November 8th, 2015.