SeaMonkey/StatusMeetings/2017-01-10: Difference between revisions

m
mNo edit summary
Line 110: Line 110:
** {{Bug|1231349}} is currently causing problems building l10n versions. Currently only a workaround exists.
** {{Bug|1231349}} is currently causing problems building l10n versions. Currently only a workaround exists.
** {{Bug|1279851}} CRASH when benchmarking webm decoding performance on YouTube page. Fixed in {{Bug|1279348}} which is in 2.47+. If possible it should be included in a special m-r SeaMonkey release branch for 2.46.
** {{Bug|1279851}} CRASH when benchmarking webm decoding performance on YouTube page. Fixed in {{Bug|1279348}} which is in 2.47+. If possible it should be included in a special m-r SeaMonkey release branch for 2.46.
** gtk3 will be disabled in the release build in {{Bug|1213152}}.
* '''SeaMonkey 2.48 Release TBA'''.
*** There are at least two problems with gtk3 builds which can not be resolved in time ({{Bug|1269145}}, {{Bug|1267982}}).
** Ready for L10N signoffs. Changesets to be provided by Callek.
*** 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}}).
** [rsx1m] GTK2 vs GTK3: comm-beta is still on gtk3; it appears that there is no movement in the gtk3-related bugs, thus I think we should stick with gtk2 at least for c-r until those are resolved or gtk2 is retired by a significant distro.
*** Building releases with gtk2 is only a short time solution. Probably a meta bug for gtk3 compatibility should be created.
** Lightning it needs a patch for l10n which doesn't exist yet. It was during the repack where the wget failed.
** '''frg''' suggests shipping 2.46 without cZ and DOMi if the l10n problems can not be fixed in time.
*** likely to happen for all locales including (en-US)


* ewong: Suggests the following:
** Officially release a linux64 build (incl. tests)
*** Start with 2.50 (or if we don't make it, 2.51) trunk.
*** Not entirely sure what is needed to make it official. Need to correspond with Callek.
** Build an unofficial (contributed build) Win64 build.  [akin to the status that Linux64 has now.]
*** Start with 2.51 (we need to iron out the build issues, though right now, having just finished a W64 build, we might be able to have it available with 2.50; but I don't know how the tests are going to work(though this will need to wait).
*** Currently tracked by {{bug|482143}}.
* Backup plan in case we need it is to do some releases off comm-esr52. These would be 2.49.x releases. No current plans until Mozilla suddenly removes full theme support or anything else which would severely break SeaMonkey.
** 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.
** Thunderbird solved l10n issues with their 49.0 beta, hopefully that procedure is transplantable to 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]
** '''Next merge day is scheduled for January 23rd''' (mozilla-beta → mozilla-release January 16th).
** '''Next merge day is scheduled for January 23rd''' (mozilla-beta → mozilla-release January 16th).
Confirmed users
2,595

edits