PI team has made the criteria for feature inclusion in release scope <https://docs.google.com/document/d/1AGECCV-V_-AYMq5C_yoWBJJ6vrl5ZdzTUgX8vM52yZc/edit#> more crisp, starting with Fx72.
At the start of every Nightly cycle, all features in scope will need to provide the following information (as per Fx72 release schedule <https://docs.google.com/spreadsheets/d/10VEf3__QCWDb4EGom-W6qGPlu71R_fDQiTCLc-7Sggo/edit#gid=1793473785> ): - PI Request submitted in JIRA (Done by milestone: PI Request due -- November 1st for Fx72) - Trello card in Firefox board <https://trello.com/b/8k1hT2vh/firefox> (Done by milestone: Feature documentation due *-- *November 8th for Fx72) - Feature documentation shared (Done by milestone: *Feature documentation due -- *November 8th for Fx72) If a feature does *not *meet all the criteria listed above by *November 8th*, it will need to go through a *VP (product, engineering) release exception process* to remain in release scope. On Wed, Oct 23, 2019 at 6:28 PM Tom Grabowski <tgrabow...@mozilla.com> wrote: > > Similar to what QA did for previous Firefox feature testing prioritization > <https://docs.google.com/spreadsheets/d/1zzd0384V9FZ0bWyU4QDofvU04vChEdKKak-1Dtro3Gs/edit#gid=152864208>, > we would like to do the same for Fx72. In order to help with the process, > please *submit your pi-request > <https://mana.mozilla.org/wiki/pages/viewpage.action?spaceKey=PI&title=PI+Request>* > <https://mana.mozilla.org/wiki/display/PI/PI+Request>by *November 1*. > This is needed to assure QA will be involved in your feature development > work for the 72 cycle. Kindly ensure to update the *Priority of the PI > request *(Highest, High, Medium, Low, Lowest) as during feature > prioritization process, this will be factored in to ensure critical > features have sufficient resources assigned. > > Please note that the *Feature technical documentation* for *features > require beta testing* needs to be ready before *November 8*. Please > follow the Feature Technical Documentation Guidelines Template > <https://docs.google.com/document/d/1h6F5A_PW4X-20zBmrftDtZwp0jdsl9oIyjaqGNFm8YQ/edit> > and share the information with the QA owners or add the link in the PI > request in JIRA. For *features that require Nightly testing*, please > provide documentation *as soon as possible*. QA cannot start working on > your feature without documentation. > > *Q: What happens after the deadline?* > A: After the deadline QA will come back with a prioritized list of work > that represents what we are committing to for the next cycle. We want to > ensure this list matches eng and product expectations. > > * Q: What if I miss the deadline?* > A: We reserve the right to say that we can't pick up work for late > requests in the current cycle. You can still develop and execute your own > test plan or defer the work to the following cycle. > > * Q: What about unknown or unexpected requests? What if there is a > business reason for a late request? What do we do with experiments and > System* > A: In order to remain flexible, we will keep some percentage of time open > for requests like these. > > *Q: There's no way I'm going to remember to do this.* > A: Do it now! I'll also send out a reminder next week. > > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
