Become a Beta Tester - Revision history

Tigersharke at 08:30, 26 April 2013

2013-04-26T08:30:14Z

Tigersharke at 20:48, 22 April 2013

2013-04-22T20:48:06Z

Drulavigne at 16:14, 16 April 2013

2013-04-16T16:14:10Z

Drulavigne: Marked this version for translation

2013-04-12T20:03:48Z

Marked this version for translation

Drulavigne at 20:03, 12 April 2013

2013-04-12T20:03:35Z

Drulavigne at 14:34, 6 November 2012

2012-11-06T14:34:26Z

Purgatori at 11:43, 5 November 2012

2012-11-05T11:43:14Z

Vater at 21:43, 3 September 2012

2012-09-03T21:43:23Z

Drulavigne at 14:04, 23 August 2012

2012-08-23T14:04:30Z

Drulavigne at 16:08, 16 August 2012

2012-08-16T16:08:51Z

@@ Line 1: / Line 1: @@
-<translate>
+<noinclude><translate>
 <!--T:1-->
-<noinclude>{{NavHeader|back=Supporting PC-BSD®|forward=Become a Translator}}</noinclude>
+{{NavHeader|back=Supporting PC-BSD®|forward=Become a Translator}}</noinclude>
 <!--T:2-->
@@ Line 34: / Line 34: @@
 <!--T:11-->
 <noinclude>
-[[category:handbook]]
+{{refheading}}
-[[category:Supporting PC-BSD®]]
 [[category:Become a Beta Tester]]
 <languages/>
 </noinclude>

@@ Line 39: / Line 39: @@
 [[category:Supporting PC-BSD®]]
 [[category:Become a Beta Tester]]
 </noinclude>
 </translate>

← Older revision		Revision as of 16:14, 16 April 2013
Line 1:		Line 1:
−	<translate><!--T:1-->	+	<translate>
		+
		+	<!--T:1-->
	<noinclude>{{NavHeader\|back=Supporting PC-BSD®\|forward=Become a Translator}}</noinclude>		<noinclude>{{NavHeader\|back=Supporting PC-BSD®\|forward=Become a Translator}}</noinclude>

@@ Line 1: / Line 1: @@
-<translate><noinclude>{{NavHeader|back=Supporting PC-BSD®|forward=Become a Translator}}</noinclude>
+<translate><!--T:1-->
 If you like playing around with operating systems and have a bit of spare time, one of the most effective ways you can assist the PC-BSD® community is by reporting problems you encounter while using PC-BSD®.
 If you have a spare system, or virtual machine, you can also download and try out the latest alpha, beta or release candidate snapshots. These versions are still in testing and have not been officially released yet. Having as many people as possible using PC-BSD® on many different hardware configurations assists the project in finding and fixing bugs. This makes using PC-BSD® better for everyone. Subscribing to the {{citelink|url=http://blog.pcbsd.org/|txt=PC-BSD® blog}} is a good way to keep up-to-date on the availability of testing snapshots and any major bugs that are found within a snapshot.
 If becoming a tester interests you, subscribe to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/testing|txt=testing mailing list}}. As new testing versions become available they will be announced on this list. You will also be able to see what problems other testers are finding and can check to see if the problem exists on your hardware as well. You can also subscribe to {{citelink|url=http://dir.gmane.org/gmane.os.pcbsd.testing|txt=Gmane's RSS feeds}} if you want a quick way to keep up with the subjects being discussed on the testing mailing list.
 Anyone can become a beta tester. Follow these tips so that you can accurately describe your findings so they can be fixed as soon as possible:
 * before sending an email, search the testing mailing list to see if anyone else has reported a similar problem.
 * when reporting a new issue, use a descriptive subject in your email that includes the error and the version of PC-BSD®. Ideally, the subject should be short (8 words or less), and contains key words about the error. An example would be "Warden on 9.1-BETA1 fails to export jail".
 * ensure that the body of your email includes the PC-BSD® version and architecture (e.g. 9.1-BETA1, 64-bit USB version).
 * give a short (2-3 sentences) description of how to recreate the error (e.g. when I right click a jail in warden and select Export jail to a .wdn file, it lets me select a file name, but then it freezes). If there is an error message, include its text.
 * include any other info that may be useful (e.g. this seems to work on my 32 bit system or this used to work on 9.0).
 * if the problem appears to be hardware related, include a copy of ''/var/run/dmesg.boot'' as this file shows the hardware that was probed the last time the PC-BSD® system booted.
 <noinclude>{{refheading}}</noinclude>
 <noinclude>

@@ Line 1: / Line 1: @@
-<noinclude>{{NavHeader|back=Supporting PC-BSD®|forward=Become a Translator}}</noinclude>
+<translate><noinclude>{{NavHeader|back=Supporting PC-BSD®|forward=Become a Translator}}</noinclude>
 If you like playing around with operating systems and have a bit of spare time, one of the most effective ways you can assist the PC-BSD® community is by reporting problems you encounter while using PC-BSD®.
@@ Line 27: / Line 27: @@
 [[category:Become a Beta Tester]]
 </noinclude>

@@ Line 3: / Line 3: @@
 If you like playing around with operating systems and have a bit of spare time, one of the most effective ways you can assist the PC-BSD community is by reporting problems you encounter using PC-BSD.
-If you have a spare system or virtual machine, you can also download and try out the latest alpha, beta or release candidate snapshots. These versions are still in testing and haven't been officially released yet. Having as many people as possible using PC-BSD on many different hardware configurations assists the project in finding and fixing bugs. This makes using PC-BSD better for everyone. PC-BSD releases always occur shortly after the FreeBSD release to allow for some extra testing. Subscribing to the {{citelink|url=http://blog.pcbsd.org/|PC-BSD blog}} is a good way to keep up-to-date on the availability of testing snapshots and any major bugs that are found within a snapshot.
+If you have a spare system or virtual machine, you can also download and try out the latest alpha, beta or release candidate snapshots. These versions are still in testing and have not been officially released yet. Having as many people as possible using PC-BSD on many different hardware configurations assists the project in finding and fixing bugs. This makes using PC-BSD better for everyone. Subscribing to the {{citelink|url=http://blog.pcbsd.org/|PC-BSD blog}} is a good way to keep up-to-date on the availability of testing snapshots and any major bugs that are found within a snapshot.
 If becoming a tester interests you, subscribe to the {{citelink|url=http://lists.pcbsd.org/mailman/listinfo/testing|testing mailing list}}. As new testing versions become available they will be announced on this list. You will also be able to see what problems other testers are finding and can check to see if the problem exists on your hardware as well. You can also subscribe to {{citelink|url=http://dir.gmane.org/gmane.os.pcbsd.testing|Gmane's RSS feeds}} if you want a quick way to keep up with the subjects being discussed on the testing mailing list.
@@ Line 11: / Line 11: @@
 * before sending an email, search the testing mailing list to see if anyone else has reported a similar problem.
-* when reporting a new issue, use a descriptive subject in your email that includes the error and the version of PC-BSD. Ideally, the subject is short (8 words or less) and contains key words about the error. An example would be "Warden on 9.0-RC3 fails to export jail".
+* when reporting a new issue, use a descriptive subject in your email that includes the error and the version of PC-BSD. Ideally, the subject is short (8 words or less) and contains key words about the error. An example would be "Warden on 9.1-BETA1 fails to export jail".
-* ensure that the body of your email includes the PC-BSD version and architecture (e.g. 9.0BETA1.5, 64-bit version).
+* ensure that the body of your email includes the PC-BSD version and architecture (e.g. 9.1-BETA1, 64-bit USB version).
 * give a short (2-3 sentences) description of how to recreate the error (e.g. when I right click a jail in warden and select Export jail to a .wdn file, it lets me select a file name, but then it freezes). If there is an error message, include its text.
-* include any other info that may be useful (e.g. this seems to work on my 32 bit system or this used to work on 8.2).
+* include any other info that may be useful (e.g. this seems to work on my 32 bit system or this used to work on 9.0).
 * if the problem appears to be hardware related, include a copy of ''/var/run/dmesg.boot'' as this file shows the hardware that was probed the last time the PC-BSD system booted.