SeaMonkey/StatusMeetings/2016-10-25: Difference between revisions

m
 
(4 intermediate revisions by the same user not shown)
Line 44: Line 44:
** Various l10n and other bugs {{bug|1293943}} which might also impact the release schedule. Currently no clear overview available.
** Various l10n and other bugs {{bug|1293943}} which might also impact the release schedule. Currently no clear overview available.
** Note for this session: due to some weird horkage on the master (my bad), the master had to be restarted(and by restarted, I meant the buildbot process and not the system).  The following status isn't updated as I don't have actual information as to the actual status. (Though, I know for sure Trunk is green as that's the only tree that was built since I had restarted the master).
** Note for this session: due to some weird horkage on the master (my bad), the master had to be restarted(and by restarted, I meant the buildbot process and not the system).  The following status isn't updated as I don't have actual information as to the actual status. (Though, I know for sure Trunk is green as that's the only tree that was built since I had restarted the master).
* CZ langpacks seem to be disabled by default, so that needs to be sorted.
* DOMi still needs to be sorted.
* [25th October 2016]
* [25th October 2016]
** All nightlies are currently running({{bug|1299078}} -post-landed-review.)
** All nightlies are currently running({{bug|1299078}} -post-landed-review.)
Line 82: Line 84:
*** a regression for gtk2 builds since 2.40 has been identified but is limited to certain desktop themes ({{bug|1312215}}).
*** a regression for gtk2 builds since 2.40 has been identified but is limited to certain desktop themes ({{bug|1312215}}).
*** Building releases with gtk2 is only a short time solution. Probably a meta bug for gtk3 compatibility should be created.
*** Building releases with gtk2 is only a short time solution. Probably a meta bug for gtk3 compatibility should be created.
** Wrong Lightning version in 2.46 build 6 Release Candidate. See {{Bug|1309372}}.
* 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.
* 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.
** 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.
Line 99: Line 102:
** SeaMonkey might release a 2.49 ESR build based on FF 52 ESR code. Nothing decided yet.
** SeaMonkey might release a 2.49 ESR build based on FF 52 ESR code. Nothing decided yet.
** any workarounds or code in dom/plugins specific to other plugins may be subsequently removed.
** any workarounds or code in dom/plugins specific to other plugins may be subsequently removed.
* DOMi langpacks aren't working. Chatzilla langpacks show as disabled on a new profile.
** IanN has locale merge working for Chatzilla. He will be working on the DOMi repack issues tonight.
** See also {{Bug|652063}} (Enable localized ChatZilla builds).
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page. Please only list current changes here.
* See [[SeaMonkey/StatusMeetings/Basics|Basics]] page. Please only list current changes here.
* '''Addons are now compatible by default. The code in the addon manager that complains about incompatible version numbers has been removed. This should reduce the friction of installing older addons.'''
* '''Addons are now compatible by default. The code in the addon manager that complains about incompatible version numbers has been removed. This should reduce the friction of installing older addons.'''
Confirmed users
2,595

edits