![]() ![]() ![]() Communication with the release coordination, release engineering, and automation teams is key. Reference (and migration / signoff plan: )ĭuring the Beta cycle, there are at least 9 beta releases. Should have testing plans for features that we know may be turned off /on conditionally.Track feature milestones (for example the e10s tracking flags.).e10s will be ready to move to Beta if stability and fixes are up to an acceptable quality level. Test e10s issues.ĭuring the 48 Developer Edition cycle we will be working to help determine the state of the Electrolysis (e10s) project. Conditional signoff for merge: (date, who signed off)Ĭontinue triaging incoming bugs with community help.What, if any, conditions would actually block or delay the move to aurora?.We should encourage the use of "feature" or verification needed keywords/flags.Continue assigning QA contact, verification + or -? What do we want to do with the iteration process.(Different for startup, plugin, crashes or specific platforms) We should decide on a threshold for "crisis" level crash spikes/crash rates.Each topcrash should have a developer assigned, a QA contact, and tracking + or.The earlier we can get these bug reports into shape for developers to prioritize them and work on them, the more likely they'll be fixed by release in April. Meet the entire QA team and hear what they're working on!ĭuring the 6 weeks that Firefox 48 is on the Nightly channel, QA will focus on helping with the Firefox iteration planning, as well as with crash reporting and triaging newly reported bugs. Meet the Desktop QA team and hear what they're working on Raise quality concerns with the Release Management team Review testing and sign off every beta release MilestoneĬonduct daily stability and bug triage, ensure features are ownedĬonduct testing to ensure Firefox 48 Aurora builds are okay, sign off for updates on FridayĬontinue daily stability and bug triage, ensure features are tested Please consult the Rapid Release Calendar for more information. Our current walkthrough of the release and QA process might be changing due to recent reorgs. This is intended to be a minimal set of information to help Firefox QA understand and communicate the quality of upcoming releases. ![]() This page is to track testing of Firefox 48 from mozilla-central (Nightly) through to mozilla-release. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |