QA/qawanted proposal - Revision history

Mschifer: /* Transition Issues */

2013-06-25T20:35:24Z

Transition Issues

← Older revision		Revision as of 20:35, 25 June 2013
Line 70:		Line 70:
	* Legacy bugs with request keywords will continue to show up in queries, as is appropriate.		* Legacy bugs with request keywords will continue to show up in queries, as is appropriate.

	* Existing ''qawanted'' keyword bugs can remain as is without being impacted by the new ''~~qa-urgent~~'' keyword		* Existing ''qawanted'' keyword bugs can remain as is without being impacted by the new ''qaurgent'' keyword

	* Initially, we will likely have to re-keyword new bugs as we educate external parties on how to use the new ''~~qa-urgent~~'' keyword as well as the use specific requests. Faster turnaround can be promoted as an incentive for them learning the scheme.		* Initially, we will likely have to re-keyword new bugs as we educate external parties on how to use the new ''qaurgent'' keyword as well as the use specific requests. Faster turnaround can be promoted as an incentive for them learning the scheme.

	* Firefox OS can continue to honor the current commitment that a blocking flag + a request keyword is an implicit ''~~qa-urgent~~'' request, while in transition. An appropriate time between releases would be chosen to fully transition.		* Firefox OS can continue to honor the current commitment that a blocking flag + a request keyword is an implicit ''qaurgent'' request, while in transition. An appropriate time between releases would be chosen to fully transition.

Mschifer: /* Proposed Changes */

2013-06-25T20:35:00Z

Proposed Changes

← Older revision		Revision as of 20:35, 25 June 2013
Line 46:		Line 46:
	* Any outstanding testing request will be expected to have at least one request keyword on it so that it can be queried.		* Any outstanding testing request will be expected to have at least one request keyword on it so that it can be queried.

	* ''~~qa-urgent~~'' will be introduced as a new keyword to request direct involvement by the Mozilla QA staff and will be used in conjunction with one of the other existing keywords.		* ''qaurgent'' will be introduced as a new keyword to request direct involvement by the Mozilla QA staff and will be used in conjunction with one of the other existing keywords.

	* ''qawanted'' will be defined as an miscellaneous request for the QA involvement not covered by any of the other existing keywords.		* ''qawanted'' will be defined as an miscellaneous request for the QA involvement not covered by any of the other existing keywords.
Line 52:		Line 52:
	* Bugzilla's keyword definitions will be updated to reflect this proposal.		* Bugzilla's keyword definitions will be updated to reflect this proposal.

	* All Product QA teams will adopt these semantics, though the specific commitment to ''~~qa-urgent~~'' response time will vary contextually between team, product, and even release, as negotiated with other stakeholders. ''qawanted'' will no longer be used to indicate an urgent response is required and should not be used in conjunction with other QA related keywords.		* All Product QA teams will adopt these semantics, though the specific commitment to ''qaurgent'' response time will vary contextually between team, product, and even release, as negotiated with other stakeholders. ''qawanted'' will no longer be used to indicate an urgent response is required and should not be used in conjunction with other QA related keywords.

	== How Proposed Changes Address Issues ==		== How Proposed Changes Address Issues ==

Gmealer: /* Transition Issues */

2013-06-13T18:23:32Z

Transition Issues

← Older revision		Revision as of 18:23, 13 June 2013
Line 74:		Line 74:
	* Initially, we will likely have to re-keyword new bugs as we educate external parties on how to use the new ''qa-urgent'' keyword as well as the use specific requests. Faster turnaround can be promoted as an incentive for them learning the scheme.		* Initially, we will likely have to re-keyword new bugs as we educate external parties on how to use the new ''qa-urgent'' keyword as well as the use specific requests. Faster turnaround can be promoted as an incentive for them learning the scheme.

	* Firefox OS can continue to honor the current commitment that a blocking flag + a request keyword is an implicit ''~~qawanted~~'' request, while in transition. An appropriate time between releases would be chosen to fully transition.		* Firefox OS can continue to honor the current commitment that a blocking flag + a request keyword is an implicit ''qa-urgent'' request, while in transition. An appropriate time between releases would be chosen to fully transition.

Mschifer at 23:38, 12 June 2013

2013-06-12T23:38:33Z

← Older revision		Revision as of 23:38, 12 June 2013
Line 46:		Line 46:
	* Any outstanding testing request will be expected to have at least one request keyword on it so that it can be queried.		* Any outstanding testing request will be expected to have at least one request keyword on it so that it can be queried.

	* ''~~qaUrgent~~'' will be introduced as a new keyword to request direct involvement by the Mozilla QA staff and will be used in conjunction with one of the other existing keywords.		* ''qa-urgent'' will be introduced as a new keyword to request direct involvement by the Mozilla QA staff and will be used in conjunction with one of the other existing keywords.

	* ''qawanted'' will be defined as an miscellaneous request for the QA involvement not covered by any of the other existing keywords. ~~This will be the basic catch all for~~		* ''qawanted'' will be defined as an miscellaneous request for the QA involvement not covered by any of the other existing keywords.

	* Bugzilla's keyword definitions will be updated to reflect this proposal.		* Bugzilla's keyword definitions will be updated to reflect this proposal.

	* All Product QA teams will adopt these semantics, though the specific commitment to ''~~qaUrgent~~'' response time will vary contextually between team, product, and even release, as negotiated with other stakeholders. ''qawanted'' will no longer be used to indicate an urgent response is required and should not be used in conjunction with other QA related keywords.		* All Product QA teams will adopt these semantics, though the specific commitment to ''qa-urgent'' response time will vary contextually between team, product, and even release, as negotiated with other stakeholders. ''qawanted'' will no longer be used to indicate an urgent response is required and should not be used in conjunction with other QA related keywords.

	== How Proposed Changes Address Issues ==		== How Proposed Changes Address Issues ==
Line 70:		Line 70:
	* Legacy bugs with request keywords will continue to show up in queries, as is appropriate.		* Legacy bugs with request keywords will continue to show up in queries, as is appropriate.

	* Existing ''qawanted'' keyword bugs can remain as is without being impacted by the new ''~~qaUrgent~~'' keyword		* Existing ''qawanted'' keyword bugs can remain as is without being impacted by the new ''qa-urgent'' keyword

	* Initially, we will likely have to re-keyword new bugs as we educate external parties on how to use the new ''~~qaUrgent~~'' keyword as well as the use specific requests. Faster turnaround can be promoted as an incentive for them learning the scheme.		* Initially, we will likely have to re-keyword new bugs as we educate external parties on how to use the new ''qa-urgent'' keyword as well as the use specific requests. Faster turnaround can be promoted as an incentive for them learning the scheme.

	* Firefox OS can continue to honor the current commitment that a blocking flag + a request keyword is an implicit ''qawanted'' request, while in transition. An appropriate time between releases would be chosen to fully transition.		* Firefox OS can continue to honor the current commitment that a blocking flag + a request keyword is an implicit ''qawanted'' request, while in transition. An appropriate time between releases would be chosen to fully transition.

Mschifer at 23:33, 12 June 2013

2013-06-12T23:33:28Z

← Older revision		Revision as of 23:33, 12 June 2013
Line 46:		Line 46:
	* Any outstanding testing request will be expected to have at least one request keyword on it so that it can be queried.		* Any outstanding testing request will be expected to have at least one request keyword on it so that it can be queried.

	* ''~~testing-wanted~~'' will be introduced as a ~~non-overlapping miscellaneous~~ keyword to ~~mean any~~ request ~~not otherwise covered~~ by ~~a more specific keyword~~.		* ''qaUrgent'' will be introduced as a new keyword to request direct involvement by the Mozilla QA staff and will be used in conjunction with one of the other existing keywords.

	* ''qawanted'' will be defined as an ~~urgent~~ request for the ~~internal~~ QA ~~team, to~~ be ~~used in combination with another keyword that indicates~~ the ~~request type.~~		* ''qawanted'' will be defined as an miscellaneous request for the QA involvement not covered by any of the other existing keywords. This will be the basic catch all for

	* Bugzilla's keyword definitions will be updated to reflect this proposal.		* Bugzilla's keyword definitions will be updated to reflect this proposal.

	* All Product QA teams will adopt these semantics, though the specific commitment to ''~~qawanted~~'' response time will vary contextually between team, product, and even release, as negotiated with other stakeholders.		* All Product QA teams will adopt these semantics, though the specific commitment to ''qaUrgent'' response time will vary contextually between team, product, and even release, as negotiated with other stakeholders. ''qawanted'' will no longer be used to indicate an urgent response is required and should not be used in conjunction with other QA related keywords.

	== How Proposed Changes Address Issues ==		== How Proposed Changes Address Issues ==
Line 70:		Line 70:
	* Legacy bugs with request keywords will continue to show up in queries, as is appropriate.		* Legacy bugs with request keywords will continue to show up in queries, as is appropriate.

	* ~~We will initially need to do a query for just~~ ''qawanted'' ~~to catch legacy~~ bugs ~~with~~ the ~~"catchall"~~ keyword~~. These can be quickly re-keyworded as appropriate.~~		* Existing ''qawanted'' keyword bugs can remain as is without being impacted by the new ''qaUrgent'' keyword

	* ~~While in transition~~, we will likely have to re-keyword new bugs as we educate external parties on how to use the specific requests. Faster turnaround can be promoted as an incentive for them learning the scheme.		* Initially, we will likely have to re-keyword new bugs as we educate external parties on how to use the new ''qaUrgent'' keyword as well as the use specific requests. Faster turnaround can be promoted as an incentive for them learning the scheme.

	* Firefox OS can continue to honor the current commitment that a blocking flag + a request keyword is an implicit ''qawanted'' request, while in transition. An appropriate time between releases would be chosen to fully transition.		* Firefox OS can continue to honor the current commitment that a blocking flag + a request keyword is an implicit ''qawanted'' request, while in transition. An appropriate time between releases would be chosen to fully transition.

Gmealer: /* Current Situation */

2013-05-14T17:58:46Z

Current Situation

← Older revision		Revision as of 17:58, 14 May 2013
Line 24:		Line 24:
	In the Bugzilla definitions, ''qawanted'' is a catchall for any testing-related work and overlaps with the other keywords. Any given request might use a specific keyword or just ''qawanted''. There is no differentiation between an urgent request for the internal QA team and a request to be left open for the larger community.		In the Bugzilla definitions, ''qawanted'' is a catchall for any testing-related work and overlaps with the other keywords. Any given request might use a specific keyword or just ''qawanted''. There is no differentiation between an urgent request for the internal QA team and a request to be left open for the larger community.

	For the Desktop and Mobile teams, ''qawanted'' is used in combination along with another testing request keyword to mean that it's an urgent request for the internal QA team. All others are left open for the community. A ~~miscellaneous~~ request that isn't urgent might have no keyword at all.		For the Desktop and Mobile teams, ''qawanted'' is used in combination along with another testing request keyword to mean that it's an urgent request for the internal QA team. All others are left open for the community. A request that isn't urgent and which isn't one of the other defined tasks might have no keyword at all.

	For Firefox OS team, ''qawanted'' means a miscellaneous testing request that no other keyword covers. Urgency is determined by blocking flags with an assumption that everything is handled internally, and there's no little to no concept of a request that's left available for the community.		For Firefox OS team, ''qawanted'' means a miscellaneous testing request that no other keyword covers. Urgency is determined by blocking flags with an assumption that everything is handled internally, and there's no little to no concept of a request that's left available for the community.

Gmealer: /* Current Situation */

2013-05-14T17:57:17Z

Current Situation

← Older revision		Revision as of 17:57, 14 May 2013
Line 22:		Line 22:
	''qawanted'', in particular, has been used inconsistently.		''qawanted'', in particular, has been used inconsistently.

	In the Bugzilla definitions, ''qawanted'' is a catchall for any testing-related work and overlaps with the other keywords. Any given request might use a specific keyword or just ''qawanted''. There is no differentiation between an urgent request for ~~paid staff~~ and a request to be left open for the community.		In the Bugzilla definitions, ''qawanted'' is a catchall for any testing-related work and overlaps with the other keywords. Any given request might use a specific keyword or just ''qawanted''. There is no differentiation between an urgent request for the internal QA team and a request to be left open for the larger community.

	For the Desktop and Mobile teams, ''qawanted'' is used in combination along with another testing request keyword to mean that it's an urgent request for the internal QA team. All others are left open for the ~~larger~~ community. A miscellaneous request that isn't urgent might have no keyword at all.		For the Desktop and Mobile teams, ''qawanted'' is used in combination along with another testing request keyword to mean that it's an urgent request for the internal QA team. All others are left open for the community. A miscellaneous request that isn't urgent might have no keyword at all.

	For Firefox OS team, ''qawanted'' means a miscellaneous testing request that no other keyword covers. Urgency is determined by blocking flags with an assumption that everything is handled internally, and there's no little to no concept of a request that's left available for the community.		For Firefox OS team, ''qawanted'' means a miscellaneous testing request that no other keyword covers. Urgency is determined by blocking flags with an assumption that everything is handled internally, and there's no little to no concept of a request that's left available for the community.

Gmealer: /* Transition Issues */

2013-05-13T21:50:18Z

Transition Issues

← Older revision		Revision as of 21:50, 13 May 2013
Line 70:		Line 70:
	* Legacy bugs with request keywords will continue to show up in queries, as is appropriate.		* Legacy bugs with request keywords will continue to show up in queries, as is appropriate.

	* We will initially need to do a query for just ''qawanted'' to catch bugs with the "catchall" keyword. These can be quickly re-keyworded as appropriate.		* We will initially need to do a query for just ''qawanted'' to catch legacy bugs with the "catchall" keyword. These can be quickly re-keyworded as appropriate.

			* While in transition, we will likely have to re-keyword new bugs as we educate external parties on how to use the specific requests. Faster turnaround can be promoted as an incentive for them learning the scheme.

	* Firefox OS can continue to honor the current commitment that a blocking flag + a request keyword is an implicit ''qawanted'' request, while in transition. An appropriate time between releases would be chosen to fully transition.		* Firefox OS can continue to honor the current commitment that a blocking flag + a request keyword is an implicit ''qawanted'' request, while in transition. An appropriate time between releases would be chosen to fully transition.

Gmealer: /* Proposed Changes */

2013-05-13T21:48:01Z

Proposed Changes

← Older revision		Revision as of 21:48, 13 May 2013
Line 46:		Line 46:
	* Any outstanding testing request will be expected to have at least one request keyword on it so that it can be queried.		* Any outstanding testing request will be expected to have at least one request keyword on it so that it can be queried.

	* ''testing-wanted'' will be introduced as a non-overlapping miscellaneous keyword to mean any request not otherwise covered by a specific keyword.		* ''testing-wanted'' will be introduced as a non-overlapping miscellaneous keyword to mean any request not otherwise covered by a more specific keyword.

	* ''qawanted'' will be defined as an urgent request for the internal QA team, to be used in combination with another keyword that indicates the request type.		* ''qawanted'' will be defined as an urgent request for the internal QA team, to be used in combination with another keyword that indicates the request type.

Gmealer: /* How This Addresses Issues */

2013-05-13T21:47:41Z

How This Addresses Issues

← Older revision		Revision as of 21:47, 13 May 2013
Line 54:		Line 54:
	* All Product QA teams will adopt these semantics, though the specific commitment to ''qawanted'' response time will vary contextually between team, product, and even release, as negotiated with other stakeholders.		* All Product QA teams will adopt these semantics, though the specific commitment to ''qawanted'' response time will vary contextually between team, product, and even release, as negotiated with other stakeholders.

	== How ~~This Addresses~~ Issues ==		== How Proposed Changes Address Issues ==

	* There will be no collision between keywords; semantics will be consistent no matter which team.		* There will be no collision between keywords; semantics will be consistent no matter which team.