Re: [IMPORTANT] Submit your PI Requests for Firefox 71 QA feature testing by Sep 13

2019-09-13 Thread Tom Grabowski
Hi,

Just a reminder that the deadline for Fx71 PI Requests is today. Please log
your requests ASAP if you have not done so yet.

- Tom


On Wed, Sep 11, 2019 at 4:59 PM Tom Grabowski 
wrote:

>
> Similar to what QA did for previous Firefox feature testing prioritization
> ,
> we would like to do the same for Fx71. In order to help with the process,
> please *submit your pi-request
> *
> by *September 13*.
> This is needed to assure QA will be involved in your feature development
> work for the 71 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 *September 27*. Please
> follow the Feature Technical Documentation Guidelines Template
> 
> 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. If the work is critical
> please follow the Exception approval process
> 
>
> * 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. Such requests need to follow the Exception
> approval process
> 
>
> *Q: There's no way I'm going to remember to do this.*
> A: Do it now!
>
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


[IMPORTANT] Submit your PI Requests for Firefox 71 QA feature testing by Sep 13

2019-09-11 Thread Tom Grabowski
Similar to what QA did for previous Firefox feature testing prioritization
,
we would like to do the same for Fx71. In order to help with the process,
please *submit your pi-request
*
by *September 13*.
This is needed to assure QA will be involved in your feature development
work for the 71 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 *September 27*. Please
follow the Feature Technical Documentation Guidelines Template

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. If the work is critical please
follow the Exception approval process


* 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. Such requests need to follow the Exception
approval process


*Q: There's no way I'm going to remember to do this.*
A: Do it now!
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform