Firefox 67 Release Date now May 21st

+Firefox Dev <firefox-dev at mozilla.org> Below is a summarized list of changes to 67, 68 milestones for this week and next: - *Feature Complete milestone* - May 10th (was May 3rd) - *Nightly Soft Code Freeze* - May 13th (was May 6th) - *First Merge* (m-c -> m-b) - May 13th (was May 6th) - *67 RC week start* - May 13th (was May 6th) - *Final Merge day* - May 20th (was May 13th) - *67 launch* - May 21st (was May 14th) Links to: - 67 Detailed milestones doc <https://docs.google.com/document/d/1feDkXleRXMJJS9lxP_vbyBApIDoEr44KchAZoYHkS54/edit> - 68 Detailed milestones doc <https://docs.google.com/spreadsheets/d/1jtNuLGugHVgZTKR3NXQGngA_EjzSGxpRBzW-DvNK3EI/edit#gid=798712201> Relman team is working on updating the release calendar and wiki to reflect the changes. These should be in sync ~1pm PST. Thanks! On Wed, May 8, 2019 at 7:05 AM Marissa (Reese) Wood <reese at mozilla.com> wrote: > Good morning! > > I want to start this message out by saying how much we *all* truly > appreciate the heroics that went into this weekend. Please do know that we > care about your health, well-being, and putting out quality products. As > such, we are going to push the release of Fx67 out by one week. > > > > *What?* > > - Fx67 will launch on May 21st (Tuesday), a week later than originally > planned for May 14th (Tuesday). > - Fx68 launch date remains unchanged, as July 9th (Tuesday). > > > > *Why is this important to you?* > > - Due to the recent add-on cert expired incident > <https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/> > , which is still active, 67 RC builds have not been completed or > tested. We also need a few more days after we ship 66.0.5 (this shipped > yesterday for Desktop and Fennec, today for ESR) to ensure release quality > is at expected levels. Nightly 68 quality is also not yet stable due to > unrelated issues. > > > > *Risks of NOT delaying**:* > > - *67 quality -* Typically, we require a week of code freeze and RC > builds to ensure the release going out the door is meeting the high > standards of quality, stability, and performance. > - *Nightly 68* - Quality is nondeterministic and combined with the new > 68 release process, we are unsure whether it is at Beta quality and ready > to be pushed to millions of beta users next week. > - *Release end-users* - Might be experiencing update fatigue (hotfixes > and dot releases pushed in quick succession). We need time to let the dust > settle on release channel owing to recent dot releases. > - *QA, relman, releng and many other teams* - have been working around > the clock and there is general fatigue. We want to minimize the window of > mistakes AND make sure that you have some time to recover! > > *Assessment Impact to other releases/projects**:* > > - EU Browser choice updates are riding 67 and 68 > > > - Google Browser choice screen is planned for slow rollout in May. > - *Risk: Low* due to Google’s slow rollout. > - Fenix MVP planned for June 25th > - Fenix will take GV68 beta build a week later. > - *Risk: Low* as they are already testing GV Nightly68 builds. > - ARM64 related impact > - *Risk: Very low* > - GPStore Aug 1st deadline for 64-bit APKs is still well within > reach. > - QC M3 hand-off can be moved out by a week. > - Project Trailhead (launch: June 4th) > > > - Nightly 69 would begin May 20th. > - No known trailhead risks with moving the Fx67 release schedule. > - *Risk: Very Low* > > > > Please feel free to contact me directly if you have any questions or > concerns. > > Again, thank you all! > > Reese > > > > *Marissa (Reese) Wood, PMP, CISSP* | Cell Phone 303-506-3282 | > reese at mozilla.com | Slack: #Marissa (Reese) > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.mozilla.org/pipermail/firefox-dev/attachments/20190508/1dd6bc2b/attachment.html>