SeaMonkey/StatusMeetings/2015-05-12: Difference between revisions

→‎Release Train: updating for upcoming Gecko 38.0 cycle
(copied from 2015-04-28 minutes)
 
(→‎Release Train: updating for upcoming Gecko 38.0 cycle)
Line 61: Line 61:
=== Release Train ===
=== Release Train ===
* SeaMonkey 2.33.1 was released on 23 March and is the most recent release.
* SeaMonkey 2.33.1 was released on 23 March and is the most recent release.
* No scheduled ETA for 2.34 beta 1 yet - depends on fixing {{bug|1114876}}
* No scheduled ETA for 2.35 beta 1 yet - depends on fixing {{bug|1114876}}
** Need to look at possibility of a further 2.33.x release if no 2.34
** Need to look at possibility of a further 2.33.x release if no 2.35
** there were 15 [https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox37.0.1 security fixes] (5 of which critical) in the Gecko 37 cycle so far
** there were 15 [https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox37.0.1 security fixes] (5 of which critical) in the Gecko 37 cycle
** Firefox has merged mozilla-beta into mozilla-release already, in preparation of the 38.0 ESR branch
** Firefox has merged mozilla-beta into mozilla-release already, in preparation of the 38.0 ESR branch
** comm-beta hasn't merged into comm-release yet
<!-- LINK IS DEAD * Useful Firefox Release Schedule link: [https://mail.mozilla.com/home/publiccalendar@mozilla.com/Releases%20Scheduling.html Releases Scheduling] -->
<!-- LINK IS DEAD * Useful Firefox Release Schedule link: [https://mail.mozilla.com/home/publiccalendar@mozilla.com/Releases%20Scheduling.html Releases Scheduling] -->
** next scheduled merge day is 11 May
** next scheduled merge day is 11 May
* Discussion on whether it's worth it to do a 2.34 Beta or skip straight to a 2.35 beta &ndash; probably the latter.


=== Extensions and Plugins Compatibility Tracking ===
=== Extensions and Plugins Compatibility Tracking ===
Confirmed users
2,255

edits