User affecting changes were identified and provided to the team. Build starts at 13:00 UTC.īeta rollout bumped to 100% provided stability is good. It is rolled out to 50% of our beta population. Uplift requests are open.įirst automated beta of the cycle. These experimental features will be deactivated mid-cycle. Some experimental features are still activated to watch their behavior on a wider population. It is rolled out to 25% of our beta population. This is the end of the development cycle for Firefox 119 and the beginning of our Beta stabilization cycle.īuilt manually just after the merge. This is the day in the release cycle when we merge mozilla-central into mozilla-beta. Nightly Regression coverage is limited compared to Beta Regression testing throughout the Beta cycle. QA assess build readiness for shipping to Beta by running a set of Regression test cases and shares a test report. In order to ensure that our localizers have adequate time to translate strings, please make sure that all string changes have landed by end of day. Risky changes should be avoided after 8:00 AM UTC until after the nightly version bump on Merge Day. We are nearing the end of the nightly cycle. Soft Code Freeze starts Draft beta release notes If nightly testing was skipped then features should be in a testable state by this date for beta testing. QA has been informed (via a Jira ticket) about features that require manual testing during the nightly and/or beta cycle.įeature technical documentation is also required to draft Test Plans and Test Cases.įeatures with a QA request are ready for testing to assess feature quality and provide a formal test report by the end of Week 3 of the nightly cycle. A new Firefox Nightly is shipped every 12 hours. After merging mozilla-central to mozilla-beta, we bump the nightly version number on mozilla-central and a new development cycle starts for Firefox.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |