Re: QA Firefox 60 feature testing pi-requests deadline is January 10

2018-01-09 Thread Tom Grabowski
Hi,

Just a reminder that the deadline for submitting your PI-requests for Fx60
feature testing is today.

Thanks,
Tom


On Mon, Jan 8, 2018 at 12:30 PM, Tom Grabowski 
wrote:

>
> Hi,
>
> Similar to what QA did for Fx59 feature testing prioritization
> ,
> we would like to do the same for Fx60. In order to help with the process, 
> *please
> submit your pi-request
>  by Jan 10. *This is
> needed to assure QA will be involved in your feature development work for
> the next Nightly 60 cycle.
>
>
> *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
> Add-ons?*
> 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,
> Tom
>
>
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


QA Firefox 60 feature testing pi-requests deadline is January 10

2018-01-08 Thread Tom Grabowski
As suggested by Liz, I'm adding dev-platform@lists.mozilla.org to this
announcement.

Hi,

Similar to what QA did for Fx59 feature testing prioritization
,
we would like to do the same for Fx60. In order to help with the
process, *please
submit your pi-request
 by Jan 10. *This is
needed to assure QA will be involved in your feature development work for
the next Nightly 60 cycle.


*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
Add-ons?*
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,
Tom
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform