Bug Tracking Process - Revision history

Cmb: Several markup changes.

2022-09-26T19:46:10Z

Several markup changes.

Topazgb: Testing is always done on the staging version so that other merged patches are included in the test.

2019-04-12T09:10:47Z

Testing is always done on the staging version so that other merged patches are included in the test.

← Older revision		Revision as of 09:10, 12 April 2019
Line 17:		Line 17:
	<!--T:36-->		<!--T:36-->
	Before a stable release of Joomla is released the update needs testing. This is a simple process:		Before a stable release of Joomla is released the update needs testing. This is a simple process:
	# Install the ~~current stable~~ release of Joomla in a subfolder or on localhost (you can use a copy of a production site but '''never test on a live production site''').		# Install the Staging release of Joomla https://github.com/joomla/joomla-cms in a subfolder or on localhost (you can use a copy of a production site but '''never test on a live production site''').
	# Navigate to the Options of the Joomla! Update component and set the 'Update server' to 'Test'. [[S:MyLanguage/Help38:Components Joomla Update\|Components Joomla Update]]		# Navigate to the Options of the Joomla! Update component and set the 'Update server' to 'Test'. [[S:MyLanguage/Help38:Components Joomla Update\|Components Joomla Update]]
	# When a Joomla pre release is ready for testing, log into your test site and install the Update. Then test the site works as expected. Please report any errors/bugs on the [https://issues.joomla.org/ Joomla! Issue Tracker]		# When a Joomla pre release is ready for testing, log into your test site and install the Update. Then test the site works as expected. Please report any errors/bugs on the [https://issues.joomla.org/ Joomla! Issue Tracker]
Line 31:		Line 31:

	<translate>		<translate>

	=== Issues reported on the forum === <!--T:9-->		=== Issues reported on the forum === <!--T:9-->
	</translate>		</translate>

Franz.wohlkoenig at 12:03, 22 November 2018

2018-11-22T12:03:39Z

← Older revision		Revision as of 12:03, 22 November 2018
Line 22:		Line 22:
	</translate>		</translate>
	<translate>		<translate>

	==Reporting Issues== <!--T:7--></translate>		==Reporting Issues== <!--T:7--></translate>
			[[Image:ReportingIssues.png\|ReportingIssues.png]]

	~~[[Image:ReportingIssues.png\|ReportingIssues.png]]~~
	<translate>		<translate>
	<!--T:8-->		<!--T:8-->

Sandra97: Marked this version for translation

2018-10-24T12:15:03Z

Marked this version for translation

← Older revision		Revision as of 12:15, 24 October 2018
Line 15:		Line 15:
	</translate>		</translate>
	<translate>		<translate>
			<!--T:36-->
	Before a stable release of Joomla is released the update needs testing. This is a simple process:		Before a stable release of Joomla is released the update needs testing. This is a simple process:
	# Install the current stable release of Joomla in a subfolder or on localhost (you can use a copy of a production site but '''never test on a live production site''').		# Install the current stable release of Joomla in a subfolder or on localhost (you can use a copy of a production site but '''never test on a live production site''').

Franz.wohlkoenig at 11:13, 24 October 2018

2018-10-24T11:13:21Z

← Older revision		Revision as of 11:13, 24 October 2018
Line 88:		Line 88:
	* <translate><!--T:29--> '''Information Required''' is used if we need more information ''from the person who reported the issue'' to decide about the issue. For example, there are questions about how to reproduce the problem or other questions about the issue. If we get the information we need, then we can continue processing the issue. If we don't get the information within two weeks, then we can change the status to Unable to confirm (or another of the closed status codes if that is more applicable).</translate>		* <translate><!--T:29--> '''Information Required''' is used if we need more information ''from the person who reported the issue'' to decide about the issue. For example, there are questions about how to reproduce the problem or other questions about the issue. If we get the information we need, then we can continue processing the issue. If we don't get the information within two weeks, then we can change the status to Unable to confirm (or another of the closed status codes if that is more applicable).</translate>
	* <translate><!--T:30--> '''Needs Review''' is used if we need a PLT Member or CMS Maintainer for a review / decision. This is different from Information Required, which means that we need more information from the person who reported the issue.</translate>		* <translate><!--T:30--> '''Needs Review''' is used if we need a PLT Member or CMS Maintainer for a review / decision. This is different from Information Required, which means that we need more information from the person who reported the issue.</translate>
	* <translate><!--T:31--> '''Confirmed''' means that JBS has confirmed that this issue is a bug in Joomla! that should be fixed. That's when the JBS tries to solve it or consults with the development team about a solution. ''At this point there should be clear step-by-step test instructions that indicate how to reproduce the problem~~. For version 1.6, use the Test Instructions field for this information~~.''</translate>		* <translate><!--T:31--> '''Confirmed''' means that JBS has confirmed that this issue is a bug in Joomla! that should be fixed. That's when the JBS tries to solve it or consults with the development team about a solution. ''At this point there should be clear step-by-step test instructions that indicate how to reproduce the problem.''</translate>
	* <translate><!--T:32--> '''Pending''' means that a patch has been submitted. Every Pending issue should have instructions that tell the tester how to reproduce the problem and make sure the patch fixes the problem.</translate>		* <translate><!--T:32--> '''Pending''' means that a patch has been submitted. Every Pending issue should have instructions that tell the tester how to reproduce the problem and make sure the patch fixes the problem.</translate>
	* <translate><!--T:33--> '''Ready to commit''' means that (in general) two separate people have successfully tested the same patch file, and it works correctly with the patch. Note that, for some issues that are more complex or higher impact, we may need more than two people to test or may need to test on multiple platforms. For simple issues, such as fixing typos in language strings or comments, one tester is enough.</translate>		* <translate><!--T:33--> '''Ready to commit''' means that (in general) two separate people have successfully tested the same patch file, and it works correctly with the patch. Note that, for some issues that are more complex or higher impact, we may need more than two people to test or may need to test on multiple platforms. For simple issues, such as fixing typos in language strings or comments, one tester is enough.</translate>

Franz.wohlkoenig at 10:44, 24 October 2018

2018-10-24T10:44:20Z

← Older revision		Revision as of 10:44, 24 October 2018
Line 75:		Line 75:
	</translate>		</translate>

	<translate><!--T:21--> The bug squad takes care of the Joomla releases. For example, that means getting the 3.4, 3.5, 3.~~6, 3~~.7 etc releases ready by fixing problems that come up. The idea is to make the release increasingly stable and take care of issues that come up. At the same time, it is vitally important not to break anything that is working. That's called software regression and it's not something you want at this stage.</translate>		<translate><!--T:21--> The bug squad takes care of the Joomla releases. For example, that means getting the 3.4, 3.5, ... etc releases ready by fixing problems that come up. The idea is to make the release increasingly stable and take care of issues that come up. At the same time, it is vitally important not to break anything that is working. That's called software regression and it's not something you want at this stage.</translate>
	<translate>		<translate>
	<!--T:22-->		<!--T:22-->

Franz.wohlkoenig at 10:28, 24 October 2018

2018-10-24T10:28:50Z

← Older revision		Revision as of 10:28, 24 October 2018
Line 56:		Line 56:
	<translate><!--T:16-->		<translate><!--T:16-->
	'''Urgent (2):'''		'''Urgent (2):'''
	Parts of the source are obstructing operation in a serious way or causing a major loss in advertised function. Examples would includes PHP notices and warnings and reported javascript errors. Major issues will also typically prevent the release cycle from moving from Beta to Release Candidate (RC), or Release Candidate to General Availability (GA).</translate>		Parts of the source are obstructing operation in a serious way or causing a major loss in advertised function. Examples would includes PHP notices and warnings and reported javascript errors. Major issues will also typically prevent the release cycle from moving from Beta to Release Candidate (RC), or Release Candidate to General Availability (GA).</translate>

	<translate><!--T:17-->		<translate><!--T:17-->
	'''Medium (3):'''		'''Medium (3):'''
	Issues that are hindering advertised behavior but the application is still workable. Examples would include parameters not working as advertised, language files not loading as expected, etc.</translate>		Issues that are hindering advertised behavior but the application is still workable. Examples would include parameters not working as advertised, language files not loading as expected, etc.</translate>

	<translate><!--T:18-->		<translate><!--T:18-->
	'''Low (4):'''		'''Low (4):'''
	Minor loss of function and generally annoying behavior. May include less common platform or browser specific problems that while they may be technically major in those environments, they represent a minority. Also include missing translation strings.</translate>		Minor loss of function and generally annoying behavior. May include less common platform or browser specific problems that while they may be technically major in those environments, they represent a minority. Also include missing translation strings.</translate>

	<translate>		<translate>

Franz.wohlkoenig at 10:22, 24 October 2018

2018-10-24T10:22:26Z

← Older revision		Revision as of 10:22, 24 October 2018
Line 52:		Line 52:
	<translate><!--T:15-->		<translate><!--T:15-->
	'''Critical (1):'''		'''Critical (1):'''
	The trunk is not working at all. Significant parts of the source are broken preventing key operations. Examples would be login, installation, extension installers, javascript errors that prevent you from moving a save or similar action, etc. Also includes the generation of Fatal PHP errors and major security issues in a prerelease (Security issues for a stable release should NOT be reported in the tracker but instead reported to the security team security@joomla.org).</translate>		The trunk is not working at all. Significant parts of the source are broken preventing key operations. Examples would be login, installation, extension installers, javascript errors that prevent you from moving a save or similar action, etc. Also includes the generation of Fatal PHP errors and major security issues in a prerelease (Security issues for a stable release should NOT be reported in the tracker but instead reported to the security team security@joomla.org).</translate>

	<translate><!--T:16-->		<translate><!--T:16-->

Franz.wohlkoenig at 10:19, 24 October 2018

2018-10-24T10:19:17Z

← Older revision		Revision as of 10:19, 24 October 2018
Line 48:		Line 48:
	</translate>		</translate>

	<translate><!--T:14--> [[S:MyLanguage/Bug and Issue Tracker Priority\|Why most issues are priority 3]], or ~~Normal~~. The artifacts are prioritized according to the following characteristics:</translate>		<translate><!--T:14--> [[S:MyLanguage/Bug and Issue Tracker Priority\|Why most issues are priority 3]], or Medium. The artifacts are prioritized according to the following characteristics:</translate>

	<translate><!--T:15-->		<translate><!--T:15-->

Franz.wohlkoenig at 09:49, 24 October 2018

2018-10-24T09:49:25Z

← Older revision		Revision as of 09:49, 24 October 2018
Line 14:		Line 14:
	===Testing Pre releases=== <!--T:6-->		===Testing Pre releases=== <!--T:6-->
	</translate>		</translate>
			<translate>
	Before a stable release of Joomla is released the update needs testing. This is a simple process:		Before a stable release of Joomla is released the update needs testing. This is a simple process:
	# Install the current stable release of Joomla in a subfolder or on localhost (you can use a copy of a production site but '''never test on a live production site''').		# Install the current stable release of Joomla in a subfolder or on localhost (you can use a copy of a production site but '''never test on a live production site''').
	# Navigate to the Options of the Joomla! Update component and set the 'Update server' to 'Test'. [[S:MyLanguage/Help38:Components Joomla Update\|Components Joomla Update]]		# Navigate to the Options of the Joomla! Update component and set the 'Update server' to 'Test'. [[S:MyLanguage/Help38:Components Joomla Update\|Components Joomla Update]]
	# When a Joomla pre release is ready for testing, log into your test site and install the Update. Then test the site works as expected. Please report any errors/bugs on the [https://issues.joomla.org/ Joomla! Issue Tracker]		# When a Joomla pre release is ready for testing, log into your test site and install the Update. Then test the site works as expected. Please report any errors/bugs on the [https://issues.joomla.org/ Joomla! Issue Tracker]
			</translate>
	<translate>		<translate>
	==Reporting Issues== <!--T:7--></translate>		==Reporting Issues== <!--T:7--></translate>