Extras-testing - Revision history

joerg_rw: /* Demotion */ clearing ambiguities

joerg_rw — Fri, 12 Apr 2013 21:00:29 GMT

Demotion: clearing ambiguities

← Older revision		Revision as of 21:00, 12 April 2013
Line 83:		Line 83:
	== Demotion ==		== Demotion ==
	An application is demoted from Extras-testing to Extras-devel when these criteria are fulfilled:		An application is demoted from Extras-testing to Extras-devel when these criteria are fulfilled:
-	* At least 10 days of quarantine	+	* At least 10 days of quarantine have expired and at least one of the following conditions is true
	* Karma < -5 (1 vote up = 1 karma point / 1 vote down = -1 karma points)		* Karma < -5 (1 vote up = 1 karma point / 1 vote down = -1 karma points)
	* When the maintainer votes down the application		* When the maintainer votes down the application

andre: Protected "Extras-testing" [edit=autoconfirmed:move=autoconfirmed]

andre — Thu, 25 Oct 2012 17:12:52 GMT

Protected "Extras-testing" [edit=autoconfirmed:move=autoconfirmed]

← Older revision

Revision as of 17:12, 25 October 2012

joerg_rw: Undo revision 50419 by 198.57.51.127 (Talk) vandalism-alike comment, moved to talk

joerg_rw — Thu, 25 Oct 2012 10:19:58 GMT

Undo revision 50419 by 198.57.51.127 (Talk) vandalism-alike comment, moved to talk

← Older revision		Revision as of 10:19, 25 October 2012
Line 19:		Line 19:
	If you want to be informed when new packages enter the Extras-Testing repository, you might want to follow [http://twitter.com/maemoextras maemoextras on Twitter].		If you want to be informed when new packages enter the Extras-Testing repository, you might want to follow [http://twitter.com/maemoextras maemoextras on Twitter].

-	~~l find it unbelievable that~~ you ~~would knlignwoy fragment the installed base~~ by ~~not providing~~ an ~~update to 770~~. ~~Not only~~ are you ~~letting~~ the ~~owners~~, ~~your early adopters down~~, ~~which~~ is ~~bad~~ in ~~itself~~, ~~but screwing third party developers by doubling build-~~, ~~test~~- and ~~distribution workload~~ is no ~~way~~ to ~~build trust for~~ the ~~platform~~. ~~Frankly,~~ it ~~shows Nokia has~~ a ~~few things~~ to ~~learn about the difference between closed~~ and ~~open systems~~.	+	== The extras-testing QA queue & you ==
		+	The list of applications waiting to be evaluated in Extras-testing can be found at
		+	http://maemo.org/packages/repository/qa/fremantle_extras-testing/
		+
		+	They are sorted by age: the first application is the oldest in the extras-testing queue and the last is the youngest. When a developer sends a new version of an application the old version disappears from the list and the new one is located at the end of the list.
		+
		+	There are three basic types of beta testers:
		+	* The ones that concentrate on the applications on top of the list (the apps that have been longest in the queue). Do this unless you have a better agenda. It is important to give feedback to developers soon. Either they get their software approved to Extras or they get bad reports so work on a new version in extras-devel.
		+	* The ones that concentrate on the applications they regularly use. By following this path you become an expert in specific applications, able to evaluate new releases quickly and get involved in the project as a regular.
		+	* The ones that concentrate on a type of testing. Some prefer to check that the features work and there are no crashes. Others might prefer to look at performance or power management metrics. Testing is a complex activity and nobody is expected to be an expert in all fields.
		+
		+	=== Report soon, report often ===
		+	Testing a specific version of an application thoroughly takes time, and most of us are busy. This is why you are encouraged to handle testing in chunks, testing a specific aspect of one application and reporting back to the page where the evaluations are made. If you report that the content of ExampleApp is correct (something that took you only ten minutes to check), then someone else after you can concentrate on something else. Ten people can look at one thing each, instead of ten people each having to go through the ten things.
		+
		+	=== Try to find the blockers first ===
		+	The [[Extras-testing/QA Checklist\|QA Checklist]] contains several points that block an app from promotion to Extras. If there is a flagrant and evident blocker (e.g. wrong use of the Maemo trademark) then there is no immediate need to go further on testing more complex and subtle aspects like power management or system reliability. Just file the blocker bug and raise the flag asking the developer to prepare a fixed version in Extras-devel.
		+
		+	=== One after another ===
		+	If you are testing aspects like power management and system stability it is recommended that you install and try out applications one by one (this is a good idea for all users anyway). If you install many applications at once then it will be difficult to find out which one is causing trouble.
		+
		+	Below you have a modular checklist to help you evaluate apps soon and often.

	== How to activate Extras-testing ==		== How to activate Extras-testing ==

198.57.51.127: /* The extras-testing QA queue & you */

198.57.51.127 — Wed, 24 Oct 2012 22:36:43 GMT

The extras-testing QA queue & you

← Older revision		Revision as of 22:36, 24 October 2012
Line 19:		Line 19:
	If you want to be informed when new packages enter the Extras-Testing repository, you might want to follow [http://twitter.com/maemoextras maemoextras on Twitter].		If you want to be informed when new packages enter the Extras-Testing repository, you might want to follow [http://twitter.com/maemoextras maemoextras on Twitter].

-	~~== The extras-testing QA queue &~~ you ==	+	l find it unbelievable that you would knlignwoy fragment the installed base by not providing an update to 770. Not only are you letting the owners, your early adopters down, which is bad in itself, but screwing third party developers by doubling build-, test- and distribution workload is no way to build trust for the platform. Frankly, it shows Nokia has a few things to learn about the difference between closed and open systems.
-	~~The list of applications waiting to be evaluated in Extras-testing can be found at~~	+
-	~~http://maemo.org/packages/repository/qa/fremantle_extras-testing/~~	+
-		+
-	~~They are sorted~~ by ~~age: the first application is the oldest in the extras-testing queue and the last is the youngest. When a developer sends a new version of~~ an ~~application the old version disappears from the list and the new one is located at the end of the list~~.	+
-		+
-	~~There~~ are ~~three basic types of beta testers:~~	+
-	* The ones that concentrate on the applications on top of the list (the apps that have been longest in the queue). Do this unless you ~~have a better agenda. It is important to give feedback to developers soon. Either they get their software approved to Extras or they get bad reports so work on a new version in extras-devel.~~	+
-	* The ones that concentrate on the ~~applications they regularly use. By following this path you become an expert in specific applications~~, ~~able to evaluate new releases quickly and get involved in the project as a regular.~~	+
-	* The ones that concentrate on a type of testing. Some prefer to check that the features work and there are no crashes. Others might prefer to look at performance or power management metrics. Testing is a complex activity and nobody is expected to be an expert in all fields.	+
-		+
-	~~=== Report soon~~, ~~report often ===~~	+
-	~~Testing a specific version of an application thoroughly takes time, and most of us are busy. This~~ is ~~why you are encouraged to handle testing~~ in ~~chunks~~, testing a specific aspect of one application and reporting back to the page where the evaluations are made. If you report that the content of ExampleApp is correct (something that took you only ten minutes to check), ~~then someone else after you can concentrate on something else. Ten people can look at one thing each, instead of ten people each having to go through the ten things.~~	+
-		+
-	~~=== Try to find the blockers first ===~~	+
-	~~The [[Extras~~-~~testing/QA Checklist\|QA Checklist]] contains several points that block an app from promotion to Extras. If there is a flagrant~~ and ~~evident blocker (e.g. wrong use of the Maemo trademark) then there~~ is no ~~immediate need~~ to ~~go further on testing more complex and subtle aspects like power management or system reliability. Just file~~ the ~~blocker bug and raise the flag asking the developer to prepare a fixed version in Extras-devel~~.	+
-		+
-	~~=== One after another ===~~	+
-	~~If you are testing aspects like power management and system stability~~ it ~~is recommended that you install and try out applications one by one (this is~~ a ~~good idea for all users anyway). If you install many applications at once then it will be difficult~~ to ~~find out which one is causing trouble.~~	+
-		+
-	~~Below you have a modular checklist to help you evaluate apps soon~~ and ~~often~~.	+

	== How to activate Extras-testing ==		== How to activate Extras-testing ==

81.82.192.49: /* Command line applications */ Fix typo

81.82.192.49 — Sat, 20 Oct 2012 16:39:42 GMT

Command line applications: Fix typo

← Older revision		Revision as of 16:39, 20 October 2012
Line 73:		Line 73:
	== Command line applications ==		== Command line applications ==

-	[[/Command line applications \| Command line apps]] are a special-case in apps and app ~~texting~~. They have their own special icon, and should have detailed descriptions and documentation describing their function.	+	[[/Command line applications \| Command line apps]] are a special-case in apps and app testing. They have their own special icon, and should have detailed descriptions and documentation describing their function.

	== Promotion ==		== Promotion ==

billmania: clarified the number of letter e-s in fremantle

billmania — Tue, 12 Apr 2011 14:49:27 GMT

clarified the number of letter e-s in fremantle

← Older revision		Revision as of 14:49, 12 April 2011
Line 43:		Line 43:
	== How to activate Extras-testing ==		== How to activate Extras-testing ==

-	Users willing to give a hand testing and evaluating community applications must start activating the extras-testing repository in the Application Manager of their Maemo 5 compatible device. Note 'fremantle' only ~~has one~~ 'e'. Note the trailing slash in the URL	+	Users willing to give a hand testing and evaluating community applications must start activating the extras-testing repository in the Application Manager of their Maemo 5 compatible device. Note, the word 'fremantle' contains only two letter 'e'. Note the trailing slash in the URL

	Application manager, menu, Application catalogs, New		Application manager, menu, Application catalogs, New

88.114.144.25: /* How to activate Extras-testing */ trailing slash

88.114.144.25 — Tue, 05 Apr 2011 18:18:22 GMT

How to activate Extras-testing: trailing slash

← Older revision		Revision as of 18:18, 5 April 2011
Line 43:		Line 43:
	== How to activate Extras-testing ==		== How to activate Extras-testing ==

-	Users willing to give a hand testing and evaluating community applications must start activating the extras-testing repository in the Application Manager of their Maemo 5 compatible device. Note 'fremantle' only has one 'e'.	+	Users willing to give a hand testing and evaluating community applications must start activating the extras-testing repository in the Application Manager of their Maemo 5 compatible device. Note 'fremantle' only has one 'e'. Note the trailing slash in the URL

	Application manager, menu, Application catalogs, New		Application manager, menu, Application catalogs, New
	Catalog name: maemo.org extras-testing		Catalog name: maemo.org extras-testing
-	Web address: http://repository.maemo.org/extras-testing	+	Web address: http://repository.maemo.org/extras-testing/
	Distribution: fremantle		Distribution: fremantle
	Components: free non-free		Components: free non-free

rotoflex: /* Try to find the blockers first */

rotoflex — Tue, 14 Dec 2010 11:51:34 GMT

Try to find the blockers first

← Older revision		Revision as of 11:51, 14 December 2010
Line 34:		Line 34:

	=== Try to find the blockers first ===		=== Try to find the blockers first ===
-	The [[Extras-testing/QA Checklist\|QA Checklist]] contains several points that ~~are blockers for~~ an app ~~to get promoted~~ to Extras. If there is a flagrant and evident blocker (e.g. wrong use of the Maemo trademark) then there is no immediate need to go further on testing more complex and subtle aspects like power management or system reliability. Just file the blocker bug and raise the flag asking the developer to prepare a fixed version in Extras-devel.	+	The [[Extras-testing/QA Checklist\|QA Checklist]] contains several points that block an app from promotion to Extras. If there is a flagrant and evident blocker (e.g. wrong use of the Maemo trademark) then there is no immediate need to go further on testing more complex and subtle aspects like power management or system reliability. Just file the blocker bug and raise the flag asking the developer to prepare a fixed version in Extras-devel.

	=== One after another ===		=== One after another ===

dneary: /* Try to hint the blockers first */

dneary — Tue, 14 Dec 2010 10:59:14 GMT

Try to hint the blockers first

← Older revision		Revision as of 10:59, 14 December 2010
Line 33:		Line 33:
	Testing a specific version of an application thoroughly takes time, and most of us are busy. This is why you are encouraged to handle testing in chunks, testing a specific aspect of one application and reporting back to the page where the evaluations are made. If you report that the content of ExampleApp is correct (something that took you only ten minutes to check), then someone else after you can concentrate on something else. Ten people can look at one thing each, instead of ten people each having to go through the ten things.		Testing a specific version of an application thoroughly takes time, and most of us are busy. This is why you are encouraged to handle testing in chunks, testing a specific aspect of one application and reporting back to the page where the evaluations are made. If you report that the content of ExampleApp is correct (something that took you only ten minutes to check), then someone else after you can concentrate on something else. Ten people can look at one thing each, instead of ten people each having to go through the ten things.

-	=== Try to ~~hint~~ the blockers first ===	+	=== Try to find the blockers first ===
	The [[Extras-testing/QA Checklist\|QA Checklist]] contains several points that are blockers for an app to get promoted to Extras. If there is a flagrant and evident blocker (e.g. wrong use of the Maemo trademark) then there is no immediate need to go further on testing more complex and subtle aspects like power management or system reliability. Just file the blocker bug and raise the flag asking the developer to prepare a fixed version in Extras-devel.		The [[Extras-testing/QA Checklist\|QA Checklist]] contains several points that are blockers for an app to get promoted to Extras. If there is a flagrant and evident blocker (e.g. wrong use of the Maemo trademark) then there is no immediate need to go further on testing more complex and subtle aspects like power management or system reliability. Just file the blocker bug and raise the flag asking the developer to prepare a fixed version in Extras-devel.

achipa: /* Thumbs Down */

achipa — Wed, 08 Sep 2010 17:39:32 GMT

Thumbs Down

← Older revision		Revision as of 17:39, 8 September 2010
Line 67:		Line 67:
	=== Thumbs Down ===		=== Thumbs Down ===

-	Whenever you decide to vote an application '''down''', please leave a comment describing the issues you found. The best feedback is a bug report from the bug-tracking system of the application because it allows the developers and testers to track and discuss the problems effectively. Voting thumbs down without any explanation doesn't help the developer in providing better software for you and the end users.	+	Whenever you decide to vote an application '''down''', please leave a comment describing the issues you found. The best feedback is a bug report from the bug-tracking system of the application because it allows the developers and testers to track and discuss the problems effectively. Voting thumbs down without any explanation doesn't help the developer in providing better software for you and the end users. Remember, this is not about "like" nearly as much as it is about "doesn't break things".

	There is also a mailing [https://garage.maemo.org/mailman/listinfo/testingsquad-comments comments list] that contains all the traffic from the comments on QA pages - it is a good reference to see how testing communication works, what the common issues are, etc.		There is also a mailing [https://garage.maemo.org/mailman/listinfo/testingsquad-comments comments list] that contains all the traffic from the comments on QA pages - it is a good reference to see how testing communication works, what the common issues are, etc.