[IMPORTANT] QA Firefox 63 feature testing pi-requests deadline is June 20

[Tom Grabowski]

Hi,

Similar to what QA did for previous Firefox feature testing prioritization
,
we would like to do the same for Fx63. In order to help with the
process, *please
submit your pi-request
 by June 20. *This is
needed to assure QA will be involved in your feature development work for
the Nightly 63 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

Fwd: [IMPORTANT] QA Firefox 63 feature testing pi-requests deadline is June 20

[Tom Grabowski]

Hi,

Just a quick reminder to everybody that the deadline for PI Requests for
Fx63 is this *Wednesday June 20th*.

Thank you,
Tom

-- Forwarded message -
From: Tom Grabowski 
Date: Fri, Jun 8, 2018 at 3:16 PM
Subject: [IMPORTANT] QA Firefox 63 feature testing pi-requests deadline is
June 20
To: , , QA Leads <
qa-le...@mozilla.com>


Hi,

Similar to what QA did for previous Firefox feature testing prioritization
<https://docs.google.com/spreadsheets/d/1Rn-F3Kg_1_VznIxxXkAGGL8mVMSAdamZZI4f1O2r8HA/edit?pli=1#gid=1005402927>,
we would like to do the same for Fx63. In order to help with the
process, *please
submit your pi-request
<https://mana.mozilla.org/wiki/display/PI/PI+Request> by June 20. *This is
needed to assure QA will be involved in your feature development work for
the Nightly 63 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

Re: QA Firefox 62 feature testing pi-requests deadline is May 2

[Tom Grabowski]

Hi,

Just a reminder that today is the deadline for submitting PI requests for
Fx 62.

Regards,
Tom


On Tue, Apr 24, 2018 at 9:16 PM, Tom Grabowski <tgrabow...@mozilla.com>
wrote:

> Hi,
>
> Similar to what QA did for previous Firefox feature testing prioritization
> <https://docs.google.com/spreadsheets/d/1Rn-F3Kg_1_VznIxxXkAGGL8mVMSAdamZZI4f1O2r8HA/edit?pli=1#gid=682505800>,
> we would like to do the same for Fx62. In order to help with the process, 
> *please
> submit your pi-request
> <https://mana.mozilla.org/wiki/display/PI/PI+Request> by May 2nd. *This
> is needed to assure QA will be involved in your feature development work
> for the next Nightly 62 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

[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

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

[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 <tgrabow...@mozilla.com>
wrote:

>
> Hi,
>
> Similar to what QA did for Fx59 feature testing prioritization
> <https://docs.google.com/spreadsheets/d/1Rn-F3Kg_1_VznIxxXkAGGL8mVMSAdamZZI4f1O2r8HA/edit?pli=1#gid=4930337>,
> we would like to do the same for Fx60. In order to help with the process, 
> *please
> submit your pi-request
> <https://mana.mozilla.org/wiki/display/PI/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

[IMPORTANT] QA Firefox 64 feature testing pi-requests deadline is August 29

[Tom Grabowski]

Hi,

Similar to what QA did for previous Firefox feature testing prioritization
,
we would like to do the same for Fx64. In order to help with the
process, *please
submit your pi-request
 by August 29. *This
is needed to assure QA will be involved in your feature development work
for the Nightly 64 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

Re: [IMPORTANT] QA Firefox 64 feature testing pi-requests deadline is August 29

[Tom Grabowski]

Hi,

Just a reminder that the deadline to send Fx64 PI Requests is *tomorrow*.
Please send your PI Requests as soon as possible. See details below.

Regards,
Tom


On Tue, Aug 21, 2018 at 3:39 PM Tom Grabowski 
wrote:

> Hi,
>
> Similar to what QA did for previous Firefox feature testing prioritization
> <https://docs.google.com/spreadsheets/d/1Rn-F3Kg_1_VznIxxXkAGGL8mVMSAdamZZI4f1O2r8HA/edit?pli=1#gid=826438053>,
> we would like to do the same for Fx64. In order to help with the process, 
> *please
> submit your pi-request
> <https://mana.mozilla.org/wiki/display/PI/PI+Request> by August 29. *This
> is needed to assure QA will be involved in your feature development work
> for the Nightly 64 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 61 feature testing pi-requests deadline is March 13

[Tom Grabowski]

Hi,

Similar to what QA did for previous Firefox feature testing prioritization
,
we would like to do the same for Fx61. In order to help with the
process, *please
submit your pi-request
 by March 13. *This is
needed to assure QA will be involved in your feature development work for
the next Nightly 61 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 62 feature testing pi-requests deadline is May 2

[Tom Grabowski]

Hi,

Similar to what QA did for previous Firefox feature testing prioritization
,
we would like to do the same for Fx62. In order to help with the
process, *please
submit your pi-request
 by May 2nd. *This is
needed to assure QA will be involved in your feature development work for
the next Nightly 62 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

Re: [IMPORTANT] QA Firefox 65 feature testing pi-requests deadline is October 17

[Tom Grabowski]

Hi,

Just a reminder to send your PI Requests as soon as possible. The deadline
is this Wednesday - October 17.

Thank you,
Tom



On Tue, Oct 9, 2018 at 7:08 PM Tom Grabowski  wrote:

> Hi,
>
> Similar to what QA did for previous Firefox feature testing prioritization
> <https://docs.google.com/spreadsheets/d/1Rn-F3Kg_1_VznIxxXkAGGL8mVMSAdamZZI4f1O2r8HA/edit?pli=1#gid=1158099166>,
> we would like to do the same for Fx65. In order to help with the process, 
> *please
> submit your pi-request
> <https://mana.mozilla.org/wiki/display/PI/PI+Request> by October 17. *This
> is needed to assure QA will be involved in your feature development work
> for the Nightly 65 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

Re: [IMPORTANT] QA Firefox 65 feature testing pi-requests deadline is October 17

[Tom Grabowski]

Hi,

Today is the last day to file your PI Requests for Fx65.
Thanks to everybody who logged their PI Requests in the last couple of
days!   For those who have not done it yet, please do it today.

Thank you,
Tom


On Mon, Oct 15, 2018 at 10:04 PM Tom Grabowski 
wrote:

> Hi,
>
> Just a reminder to send your PI Requests as soon as possible. The deadline
> is this Wednesday - October 17.
>
> Thank you,
> Tom
>
>
>
> On Tue, Oct 9, 2018 at 7:08 PM Tom Grabowski 
> wrote:
>
>> Hi,
>>
>> Similar to what QA did for previous Firefox feature testing
>> prioritization
>> <https://docs.google.com/spreadsheets/d/1Rn-F3Kg_1_VznIxxXkAGGL8mVMSAdamZZI4f1O2r8HA/edit?pli=1#gid=1158099166>,
>> we would like to do the same for Fx65. In order to help with the process, 
>> *please
>> submit your pi-request
>> <https://mana.mozilla.org/wiki/display/PI/PI+Request> by October 17. *This
>> is needed to assure QA will be involved in your feature development work
>> for the Nightly 65 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

[IMPORTANT] QA Firefox 65 feature testing pi-requests deadline is October 17

[Tom Grabowski]

 Hi,

Similar to what QA did for previous Firefox feature testing prioritization
,
we would like to do the same for Fx65. In order to help with the
process, *please
submit your pi-request
 by October 17. *This
is needed to assure QA will be involved in your feature development work
for the Nightly 65 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

[IMPORTANT] QA Firefox 67 feature testing pi-requests deadline is January 23

[Tom Grabowski]

Hi,

Similar to what QA did for previous Firefox feature testing prioritization
,
we would like to do the same for Fx67. In order to help with the
process, *please
submit your pi-request
 by January 23. *This
is needed to assure QA will be involved in your feature development work
for the Nightly 67 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

Re: [IMPORTANT] QA Firefox 67 feature testing pi-requests deadline is January 23

[Tom Grabowski]

Hi,

Just a reminder that the deadline for Fx67 PI Requests is tomorrow, January
23.
If you have not done it yet, please send your requests now.

Regards,
Tom


On Thu, Jan 17, 2019 at 1:15 PM Tom Grabowski 
wrote:

> Hi,
>
> Similar to what QA did for previous Firefox feature testing prioritization
> <https://docs.google.com/spreadsheets/d/1Rn-F3Kg_1_VznIxxXkAGGL8mVMSAdamZZI4f1O2r8HA/edit?pli=1#gid=243633991>,
> we would like to do the same for Fx67. In order to help with the process, 
> *please
> submit your pi-request
> <https://mana.mozilla.org/wiki/display/PI/PI+Request> by January 23. *This
> is needed to assure QA will be involved in your feature development work
> for the Nightly 67 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

[IMPORTANT] QA Firefox 66 feature testing pi-requests deadline is December 5

[Tom Grabowski]

Hi,

Similar to what QA did for previous Firefox feature testing prioritization
,
we would like to do the same for Fx66. In order to help with the
process, *please
submit your pi-request
 by December 5. *This
is needed to assure QA will be involved in your feature development work
for the Nightly 66 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

Re: [IMPORTANT] QA Firefox 66 feature testing pi-requests deadline is December 5

[Tom Grabowski]

Just a reminder that the deadline for Fx66 PI Requests is *today* December
5th!  Please submit your requests as soon as possible.

Thank you,
Tom


On Wed, Nov 28, 2018 at 11:09 PM Tom Grabowski 
wrote:

> Hi,
>
> Similar to what QA did for previous Firefox feature testing prioritization
> <https://docs.google.com/spreadsheets/d/1Rn-F3Kg_1_VznIxxXkAGGL8mVMSAdamZZI4f1O2r8HA/edit?pli=1#gid=1592190850>,
> we would like to do the same for Fx66. In order to help with the process, 
> *please
> submit your pi-request
> <https://mana.mozilla.org/wiki/display/PI/PI+Request> by December 5. *This
> is needed to assure QA will be involved in your feature development work
> for the Nightly 66 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

Re: [IMPORTANT] Submit your PI Requests for Firefox 68 QA feature testing by March 29

[Tom Grabowski]

Hi,

Just a reminder that the deadline for Fx68 PI Requests is today. If you
have not done it yet, please log your PI request as soon as possible.

- Tom


On Fri, Mar 22, 2019 at 11:40 PM Tom Grabowski 
wrote:

> Similar to what QA did for previous Firefox feature testing prioritization
> <https://docs.google.com/spreadsheets/d/1Rn-F3Kg_1_VznIxxXkAGGL8mVMSAdamZZI4f1O2r8HA/edit?pli=1#gid=682799809>,
> we would like to do the same for Fx68. In order to help with the process, 
> *please
> submit your pi-request
> <https://mana.mozilla.org/wiki/display/PI/PI+Request> by March 29. *This
> is needed to assure QA will be involved in your feature development work
> for the 68 cycle.
>
> As you are probably aware, starting with Fx68, the release process and
> schedule are changing. Full description of changes can be found here
> <https://docs.google.com/document/d/129IEYhx8wdBltgn3ErBEPSBrzsWyHobZsjruwlHhxfw/edit>.
> By default, all PI requests are to be considered for testing in Beta cycle
> only. Project teams can request if they need Nightly testing, which is now
> optional.
>
> Please note that the *feature technical documentation needs to be ready
> before April 12*, so that QA has enough time to design the test plan.
> Please make sure your documentation follows these guidelines: Feature
> Technical Documentation Guidelines
> <https://docs.google.com/document/d/1h6F5A_PW4X-20zBmrftDtZwp0jdsl9oIyjaqGNFm8YQ/edit>.
> 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
> 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

[IMPORTANT] Submit your PI Requests for Firefox 68 QA feature testing by March 29

[Tom Grabowski]

 Similar to what QA did for previous Firefox feature testing prioritization
,
we would like to do the same for Fx68. In order to help with the
process, *please
submit your pi-request
 by March 29. *This is
needed to assure QA will be involved in your feature development work for
the 68 cycle.

As you are probably aware, starting with Fx68, the release process and
schedule are changing. Full description of changes can be found here
.
By default, all PI requests are to be considered for testing in Beta cycle
only. Project teams can request if they need Nightly testing, which is now
optional.

Please note that the *feature technical documentation needs to be ready
before April 12*, so that QA has enough time to design the test plan.
Please make sure your documentation follows these guidelines: Feature
Technical Documentation Guidelines
.
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
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

[IMPORTANT] Submit your PI Requests for Firefox 69 QA feature testing by May 31

[Tom Grabowski]

Similar to what QA did for previous Firefox feature testing prioritization
,
we would like to do the same for Fx69. In order to help with the process,
please *submit your pi-request
*
by *May 31*. This is
needed to assure QA will be involved in your feature development work for
the 69 cycle. Kindly ensure to update the *Priority of the PI request *(High,
Medium, Low) 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* needs to be ready
before *June 14*, so that QA has enough time to design the test plan.
Please fill out the Feature Technical Documentation Guidelines Template

and share with the QA owner 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
Add-ons?*
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

Re: [IMPORTANT] Submit your PI Requests for Firefox 69 QA feature testing by May 31

[Tom Grabowski]

Hi,

This is a reminder that the deadline for submitting PI Requests for Fx69 is
today.
Please submit your requests now.

Thank you,
Tom


On Tue, May 28, 2019 at 11:10 PM Tom Grabowski 
wrote:

>
> Similar to what QA did for previous Firefox feature testing prioritization
> <https://docs.google.com/spreadsheets/d/1zzd0384V9FZ0bWyU4QDofvU04vChEdKKak-1Dtro3Gs/edit#gid=259668819>,
> we would like to do the same for Fx69. In order to help with the process,
> please *submit your pi-request
> <https://mana.mozilla.org/wiki/display/PI/PI+Request>*
> <https://mana.mozilla.org/wiki/display/PI/PI+Request>by *May 31*. This is
> needed to assure QA will be involved in your feature development work for
> the 69 cycle. Kindly ensure to update the *Priority of the PI request *(High,
> Medium, Low) 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* needs to be ready
> before *June 14*, so that QA has enough time to design the test plan.
> Please fill out the Feature Technical Documentation Guidelines Template
> <https://docs.google.com/document/d/1h6F5A_PW4X-20zBmrftDtZwp0jdsl9oIyjaqGNFm8YQ/edit>
> and share with the QA owner 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
> <https://docs.google.com/document/d/1jOTngDV_WWJGelTz4205ux4i5sAWfYNILHYmLLmHYeQ/edit>
>
> * 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. Such requests need to follow the Exception
> approval process
> <https://docs.google.com/document/d/1jOTngDV_WWJGelTz4205ux4i5sAWfYNILHYmLLmHYeQ/edit>
>
> *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

We have migrated JIRA ServiceDesk to local JIRA Server instance

[Tom Grabowski]

Hi,

If you log, or work with, PI Requests, please read this email.

Today, we have migrated our cloud instance of JIRA ServiceDesk into our
local JIRA Software. This resulted in some important changes that I will
outline below.

*Why did we do it?*
- We won't have problems with licenses anymore (we kept running out of
licenses on ServiceDesk)
- We can now use Mozilla LDAP SSO to log in to JIRA
- Easier maintenance and compatibility with other teams who use JIRA at
Mozilla
- More features, allowing future improvements and integrations

*Is the URL to the service the same?*
No. The new URL is https://jira.mozilla.com   (the old URL was
moz-pi-test.atlassian.net)

*Is the UI the same as before?*
No. JIRA Software is not the same product as JIRA ServiceDesk. The UI will
look a bit different, but all the fields, states and other concepts are the
same, so the transition should be quite painless for most.

*Where are my existing PI Requests?*
In order to figure out correct URL to access your existing PI Requests, you
need to know the request number. For example, if your PI Request number was
PI-123, the new URL will be this: https://jira.mozilla.com/browse/PI-123
If you don't know your PI Request number, you can either try to find it
here: https://jira.mozilla.com/secure/RapidBoard.jspa?rapidView=263 or
contact me for help.

*How do I log new PI Requests?*
New URLs are documented on our PI Request mana page:
https://mana.mozilla.org/wiki/display/PI/PI+Request

*I have other question or issue that wasn't answered above.*
Please contact me and I will be able to help.


I would encourage everybody to try to log in to the new system in order to
make sure you have the correct permissions. You can use the example URL I
showed above to make sure you can see the ticket correctly:
https://jira.mozilla.com/browse/PI-123

I would like to take this opportunity to thank Marek Platta and Majken
Longlade for their hard work on this migration, and for working during the
weekend to keep the disruptions to minimum. Great job guys!

Don't hesitate to contact me if you have any questions or comments.

Regards,
Tom
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

[IMPORTANT] Submit your PI Requests for Skyline/Firefox 70 QA feature testing by July 19

[Tom Grabowski]

Similar to what QA did for previous Firefox feature testing prioritization
,
we would like to do the same for Fx70/Skyline. In order to help with the
process, please *submit your pi-request
*
by *July 19*. This is
needed to assure QA will be involved in your feature development work for
the 70 cycle. Please ensure to update the *Priority of the PI request
*(Highest,
High, Medium, Low, Lowest) since during feature prioritization process,
this will be factored in to ensure critical features have sufficient
resources assigned. For Skyline related requests, please mention "*Skyline*"
in description or summary.

Please note that the *Feature technical documentation* for *features that
require Nightly testing* needs to be ready before *July 26*. For features
requiring just *Beta testing*, the *due date *is* August 2nd*. 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. 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
Add-ons?*
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! 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

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

[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

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

[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
> <https://docs.google.com/spreadsheets/d/1zzd0384V9FZ0bWyU4QDofvU04vChEdKKak-1Dtro3Gs/edit#gid=126088562>,
> we would like to do the same for Fx71. In order to help with the process,
> please *submit your pi-request
> <https://mana.mozilla.org/wiki/pages/viewpage.action?spaceKey=PI=PI+Request>*
> <https://mana.mozilla.org/wiki/display/PI/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
> <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. If the work is critical
> please follow the Exception approval process
> <https://docs.google.com/document/d/1jOTngDV_WWJGelTz4205ux4i5sAWfYNILHYmLLmHYeQ/edit>
>
> * 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
> <https://docs.google.com/document/d/1jOTngDV_WWJGelTz4205ux4i5sAWfYNILHYmLLmHYeQ/edit>
>
> *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

Re: [IMPORTANT] Submit your PI Requests for Skyline/Firefox 70 QA feature testing by July 19

[Tom Grabowski]

Hi,

This is a reminder that the deadline for PI Requests for Fx70 is *tomorrow*.
Please submit your requests ASAP.

Thank you,
Tom


On Thu, Jul 11, 2019 at 2:20 PM Tom Grabowski 
wrote:

> Similar to what QA did for previous Firefox feature testing prioritization
> <https://docs.google.com/spreadsheets/d/1zzd0384V9FZ0bWyU4QDofvU04vChEdKKak-1Dtro3Gs/edit#gid=1982612750>,
> we would like to do the same for Fx70/Skyline. In order to help with the
> process, please *submit your pi-request
> <https://mana.mozilla.org/wiki/pages/viewpage.action?spaceKey=PI=PI+Request>*
> <https://mana.mozilla.org/wiki/display/PI/PI+Request>by *July 19*. This
> is needed to assure QA will be involved in your feature development work
> for the 70 cycle. Please ensure to update the *Priority of the PI request
> *(Highest, High, Medium, Low, Lowest) since during feature prioritization
> process, this will be factored in to ensure critical features have
> sufficient resources assigned. For Skyline related requests, please mention
> "*Skyline*" in description or summary.
>
> Please note that the *Feature technical documentation* for *features that
> require Nightly testing* needs to be ready before *July 26*. For features
> requiring just *Beta testing*, the *due date *is* August 2nd*. 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. 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
> <https://docs.google.com/document/d/1jOTngDV_WWJGelTz4205ux4i5sAWfYNILHYmLLmHYeQ/edit>
>
> * 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. Such requests need to follow the Exception
> approval process
> <https://docs.google.com/document/d/1jOTngDV_WWJGelTz4205ux4i5sAWfYNILHYmLLmHYeQ/edit>
>
> *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

Re: [IMPORTANT] Submit your PI Requests for Firefox 72 QA feature testing by Nov 1

[Tom Grabowski]

Just a quick reminder that the deadline for Fx72 Pi Requests is *today*.
Please submit your requests as soon as possible.


On Tue, Oct 29, 2019 at 11:20 PM Tom Grabowski 
wrote:

> 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 
> 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=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

Re: [IMPORTANT] Submit your PI Requests and technical documentation for Firefox 73 QA feature testing by Dec 13

[Tom Grabowski]

Hi,

This is a reminder that the deadline for PI Requests and technical
documentation for Firefox 73 is this Friday, December 13th. Please log your
PI Request tickets as soon as possible, and provide the required technical
docs.

Thank you,
Tom


On Wed, Dec 4, 2019 at 6:59 PM Tom Grabowski  wrote:

> Similar to what QA did for previous Firefox feature testing prioritization
> <https://docs.google.com/spreadsheets/d/1zzd0384V9FZ0bWyU4QDofvU04vChEdKKak-1Dtro3Gs/edit#gid=259668819>,
> we would like to do the same for Fx73. In order to help with the process,
> please *submit your PI-Request
> <https://mana.mozilla.org/wiki/pages/viewpage.action?spaceKey=PI=PI+Request>*
> <https://mana.mozilla.org/wiki/display/PI/PI+Request>and* Feature
> Technical Documentation
> <https://docs.google.com/document/d/1h6F5A_PW4X-20zBmrftDtZwp0jdsl9oIyjaqGNFm8YQ/edit>
> *by *Friday, December 13*. This is needed to assure QA will be involved
> in your feature development work for the 73 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 Dec 13th.
>
> 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.
>
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Re: [IMPORTANT] Submit your PI Requests for Firefox 72 QA feature testing by Nov 1

[Tom Grabowski]

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 
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=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

[IMPORTANT] Submit your PI Requests for Firefox 72 QA feature testing by Nov 1

[Tom Grabowski]

Similar to what QA did for previous Firefox feature testing prioritization
,
we would like to do the same for Fx72. In order to help with the process,
please *submit your 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

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