SeaMonkey/StatusMeetings/2017-06-04: Difference between revisions

→‎Release Train: added upcoming merge day
(→‎Release Train: updates on 2.48/2.49 status)
(→‎Release Train: added upcoming merge day)
Line 139: Line 139:
** {{bug|1358148}} to get status and approval flags added in bugzilla for SeaMonkey 2.49esr completed, including approval-comm-esr52
** {{bug|1358148}} to get status and approval flags added in bugzilla for SeaMonkey 2.49esr completed, including approval-comm-esr52
* 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: '''June 12''', 2017.
* The next release after 2.48 will be 2.49.1 build from the ESR branch.  
* The next release after 2.48 will be 2.49.1 build from the ESR branch.  
** '''frg''' asked if a version of 2.49.x.x is supported to distingush between cycles and builds. '''tonymec''' thinks this might work but '''ewong''' isn't sure if the infra can cope with this.
** '''frg''' asked if a version of 2.49.x.x is supported to distingush between cycles and builds. '''tonymec''' thinks this might work but '''ewong''' isn't sure if the infra can cope with this.
Confirmed users
2,255

edits