733
edits
Philip Chee (talk | contribs) |
(Special status meeting notes.) |
||
| Line 7: | Line 7: | ||
* Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel] | * Location: [irc://irc.mozilla.org/seamonkey #seamonkey IRC channel] | ||
* Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]] | * Further Read: [[SeaMonkey/StatusMeetings/Basics|Basics]] | ||
* Participants (in order of appearance): | * Participants (in order of appearance): Ratty IanN rsx11m ewong jez libertyernie hrosik | ||
== Agenda == | == Agenda == | ||
* Who's taking minutes? -> ''' | * Who's taking minutes? -> '''frg''' | ||
* Nominees for Friends of the Fish Tank: | * Nominees for Friends of the Fish Tank: | ||
** ''' | ** '''Rainer Bielefeld''' for testing and doing good work with his en-us and de SeaMonkey blogs. | ||
=== Special agenda only for this meeting === | |||
* Because of the 0-day {{bug|1321066}}, the problems building 2.46 on the official build servers and the bleak outlook with XUL and classic extensions removal on the horizon the regular meeting agenda was thrown overboard for this meeting only to discuss future plans. | |||
==== 2.40.1 release ==== | |||
* Doing a 2.40.1 release was suggested until 2.46 is ready because of the 0-day bug. | |||
** Pros | |||
*** Would fix this bug and could probably be done. | |||
*** l10n building is or was working for 2.40. | |||
** Cons | |||
*** 0-day fix might not apply clean. | |||
*** Because of releng changes update might not be uploadable without changing the configs and build files. | |||
*** It would only fix this one bug. There are many other security related fixed in 2.46 and now 2.47. | |||
*** 2.40 is outdated (especially html5 and js support) and users expect a new release. | |||
** No final decision but the consensus seems to be it should not be done. | |||
==== 2.46 release and what to do ==== | |||
* 2.46 is still stalled because of {{bug|1231349}} | |||
** It was decided to remove cZ and DOMi for this build only. | |||
*** '''frg''' provided a patch which worked for him and removed the extensions. It applied clean onto the c-r rel branch. | |||
*** '''ewong''' commented that the source teee on the builder is different. | |||
*** Links to amo or alternate sites need to be provided for the removed extensions. | |||
*** Lightning did build successfully locally with the patch. {{bug|1309372}} is fixed in all trees and the next version should contain a Lightning with a correct version number. | |||
*** compare-locales was recently updated. '''frg''' used 1.2.1. '''ewong''' checks the builders. | |||
** '''IanN''' provided another patch which fixed the problem for him locally | |||
*** '''frg''' tested the patch and commented in the bug. | |||
** The feeling is that something with the builders is not ok or missing. | |||
** '''ewong''' needs to verify the source tree on the builder for changes and do another clean build. | |||
==== Release Planning in case 2.46 can not be build ==== | |||
* Many users are already using the unofficial SeaMonkey version from '''adriank'''. He now builds also for macOS. | |||
* If the current version can not be build on the official servers a short term solution is to make Adrians versions official. | |||
** This version would be 2.47 and needed to be made from provided cSets so that Linux distros can pick up an official source package. | |||
** Release tree needs to be tagged for this. | |||
** It is unclear if such a build could be uploaded to Mozilla servers. In this case it would need to go to seamonkey-project.org. | |||
* '''adriank''' knows about it and didn't say no but details still need to be worked out. | |||
==== Release Planning next release ==== | |||
* Mozilla plans to remove XUL and classic extensions by the end of 2017. While it is still unlcear if the time table is realistic the future outlook is bleak. | |||
* It is unclear if the current SeaMonkey dev team can fix the upcoming build breaks fast enough to do regular releases. | |||
* SeaMonkey 2.50a1 (FF 53) is building but this may change at any time. l20n is planned for FF 53 and might disrupt l10n building again. | |||
* The consensus seems to be to do a ESR 52 cycle for the next SeaMonkey release. This would mean SeaMonkey 2.49 will become an ESR release still providing Windows XP and Vista compatibility. | |||
* Thunderbird already does ESR only. The biggest obstacle/restriction is that no string changes are allowed. | |||
* Doing a 2.49 ESR will give the dev team a breather to fix the upcoming breaks in the mozilla source tree. | |||
* Forking the Mozilla source tree is not an option. The dev team is too small and would not be able to even fix all upcoming security bugs in a forked Gecko engine. | |||
==== Release Planning mid/long term ==== | |||
* Mid/Long term release planning was not discussed because of time constraints. It will be put on the agenda of the next status meeting. | |||
* It was suggested that we set up own builders to become more independent of Mozilla. '''adriank''' already has a working build system based on Jenkins. '''Ratty''' and '''ewong''' would like to set up one based on buildbot. No decision needed right now but this needs to be worked out. | |||
* A new build system should provide try builds and should us also enable doing automated tests again. | |||
<!--original agenda not updated for this meeting--> | |||
=== Action Items === | === Action Items === | ||
(who needs to do what that hasn't been recorded in a bug) | (who needs to do what that hasn't been recorded in a bug) | ||
| Line 58: | Line 104: | ||
** All nightlies are currently running({{bug|1299078}} -post-landed-review.) | ** All nightlies are currently running({{bug|1299078}} -post-landed-review.) | ||
** [comm-central]: | ** [comm-central]: | ||
*** All Platforms: "Crimson red" due to the XPCOM bug. {{bug|1318735}} | *** All Platforms: "Crimson red" due to the XPCOM bug. {{bug|1318735}}. '''Fixed after the meeting.''' First tinderbox builds already out. | ||
*** See {{bug|1319091}} for current breakages. | *** See {{bug|1319091}} for current breakages. | ||
*** No longer able to drop a url into the browser. {{bug|1319212}} | *** No longer able to drop a url into the browser. {{bug|1319212}} | ||
edits