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

→‎Release Train: merges complete
(→‎rsx11m: recent activity)
(→‎Release Train: merges complete)
Line 64: Line 64:
** Need to look at possibility of a further 2.33.x release if no 2.35
** 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
** 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
** 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
** merge day was 11 May as scheduled


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

edits