Just a quick reminder that the deadline for submitting PI requests for 75
is *tomorrow*. Kindly submit your PI requests as soon as possible.

Link to JIRA *create Issue* page:  here
<https://jira.mozilla.com//secure/CreateIssueDetails!init.jspa?pid=10245&issuetype=10203>
PI Request process: here
<https://mana.mozilla.org/wiki/pages/viewpage.action?spaceKey=PI&title=PI+Request>

Thanks,
Tania


On Thu, Feb 6, 2020 at 11:51 PM Tania Maity <tma...@mozilla.com> wrote:

> Similar to what QA did for previous Firefox feature testing prioritization
> <https://docs.google.com/spreadsheets/d/1zzd0384V9FZ0bWyU4QDofvU04vChEdKKak-1Dtro3Gs/edit#gid=1946654478>,
> we would like to do the same for Fx75. 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 *Friday,
> February 14*. Please note that the Feature Technical Documentation
> <https://docs.google.com/document/d/1h6F5A_PW4X-20zBmrftDtZwp0jdsl9oIyjaqGNFm8YQ/edit>
> for *features require beta testing* needs to be ready before *
> <https://docs.google.com/document/d/1h6F5A_PW4X-20zBmrftDtZwp0jdsl9oIyjaqGNFm8YQ/edit>*
> by February 21st. This is needed to assure QA will be involved in your
> feature development work for the 75 cycle. For *features that require
> Nightly testing*, please provide documentation *as soon as possible*. QA
> cannot start working on your feature without documentation. Along with
> these, please create corresponding feature trello cards in Firefox
> <https://trello.com/b/8k1hT2vh/firefox> board by February 21st.
>
> 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.
>
> *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?*
> 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.
>
> Thanks,
> Tania
>
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to