SeaMonkey/StatusMeetings/2017-04-23: Difference between revisions

Jump to navigation Jump to search
→‎Release Train: updates on 2.48, 2.49, and aurora channel
(→‎Release Train: updates on 2.48, 2.49, and aurora channel)
Line 95: Line 95:


=== Release Train ===
=== Release Train ===
* SeaMonkey 2.46 was released December 22, 2016, tracked in {{Bug|1294433}}
* '''SeaMonkey 2.48 beta 1 released''' April 15, 2017 — ''kudos to ewong!''
* SeaMonkey 2.48 will be the next release tracked in {{Bug|1336310}} (general beta issues in {{bug|1328886}})
* SeaMonkey 2.48 will be the next release tracked in {{Bug|1351984}} (general beta issues in {{bug|1328886}})
** SeaMonkey 2.48 beta 1 is in candidates [https://archive.mozilla.org/pub/seamonkey/candidates/2.48b1-candidates/build7/]. '''ewong''' wants to figure out if updates from 2.39b1 can be made to work so that the 2.48 release will upgrade from 2.46 without problems.
** Updates from 2.39b1 apparently did not work, relevant for the 2.48 release to upgrade from 2.46 without problems.
** l10n problems from 2.46 are still not solved. Extensions again can not be shipped bundled with this release. A removal patch has been checked in. DOMi and cZ tags have nevertheless been updated for a future release.
** l10n problems from 2.46 are still not solved. Extensions again can not be shipped bundled with this release. A removal patch has been checked in. DOMi and cZ tags have nevertheless been updated for a future release.
*** l10n problem is tracked in ({{bug|1231349}}).
*** l10n problem is tracked in ({{bug|1231349}}).
Line 104: Line 104:
*** See also {{Bug|652063}} (Enable localized ChatZilla builds).
*** See also {{Bug|652063}} (Enable localized ChatZilla builds).
** Release notes in {{Bug|1336315}}.
** Release notes in {{Bug|1336315}}.
** gtk3 will be disabled for beta and likely release builds. Building with gtk2 currently helds up the build because there are several minor problems in mozilla code. Fixes are redy and will be pushed to the beta branch. '''ewong''' is currently asking for approval because he isn't sure if we could do this. IanN and frg think we did it before and no approval is needed because its branch only.
** gtk3 will be disabled for beta and likely release builds.
*** There are at least three problems with gtk3 builds which may not be resolved in time ({{Bug|1269145}}, {{Bug|1267982}}, {{Bug|1331208}}).
*** There are at least three problems with gtk3 builds which may not be resolved in time ({{Bug|1269145}}, {{Bug|1267982}}, {{Bug|1331208}}).
*** A regression for gtk2 builds since 2.40 has been identified but is limited to certain desktop themes and doesn't seem to affect the most current OS version ({{bug|1312215}}).
*** A regression for gtk2 builds since 2.40 has been identified but is limited to certain desktop themes and doesn't seem to affect the most current OS version ({{bug|1312215}}).
Line 112: Line 112:
*** {{Bug|1274722}} Add %SYSTEM_CAPABILITIES% to the SeaMonkey app.update.url preference
*** {{Bug|1274722}} Add %SYSTEM_CAPABILITIES% to the SeaMonkey app.update.url preference
*** {{Bug|1271761}} Add CPU features/detection to update URL
*** {{Bug|1271761}} Add CPU features/detection to update URL
** 2.48 is 'lightly' blocked on our ability to migrate from AUS2 to Balrog as the above mentioned bugs might be difficult with AUS2. {{bug|1254401}}
** 2.48 is still 'lightly' blocked on our ability to migrate from AUS2 to Balrog as the above mentioned bugs might be difficult with AUS2. {{bug|1254401}}
** frg mentioned that the 2.48 is getting late and if we should jump directly to 2.49 after the 2.48 beta which is mostly done now for getting the migration to balrog tested. ewong wants a stable 2.48 release as an interim to further test the migration work.
** frg mentioned that the 2.48 is getting late and if we should jump directly to 2.49 after the 2.48 beta which is mostly done now for getting the migration to balrog tested. ewong wants a stable 2.48 release as an interim to further test the migration work.
* Discussions if we should match minor version numbers with Firefox are still underway. This would need a coordinated change for either c-c or all trees. All minor versions would be changed and the versions would need to be made available in bugzilla. Lightning version calculation needs to be changed. This will be done at a later date and not for 2.49 ESR.
* Discussions if we should match minor version numbers with Firefox are still underway. This would need a coordinated change for either c-c or all trees. All minor versions would be changed and the versions would need to be made available in bugzilla. Lightning version calculation needs to be changed. This will be done at a later date and not for 2.49 ESR.
* '''The aurora channel is discontinued per last merge on April 18''' ({{bug|1353821}}, {{bug|1354818}})
** comm-central stays on SeaMonkey 2.52 and will merge directly into comm-beta around June 12.


* ewong: Suggests the following:
* ewong: Suggests the following:
Line 127: Line 130:
** Firefox plans removal of non-WebExtension add-ons and full-theme support with Gecko 57 [https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/].
** Firefox plans removal of non-WebExtension add-ons and full-theme support with Gecko 57 [https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/].
** Patches which do not concern Thunderbird could be checked into comm-esr52 (once established) after getting approval too.
** Patches which do not concern Thunderbird could be checked into comm-esr52 (once established) after getting approval too.
** '''rsx11m''' filed {{bug|1358148}} to get status and approval flags added in bugzilla for SeaMonkey
* 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]


Confirmed users
2,255

edits

Navigation menu