Using the bug tracker - Revision history

Patsyblefebre: /* Projects */[Brief_introduction_to_SVN#Types_of_branches|Types of Branches

2013-02-04T21:44:55Z

‎Projects: [Brief_introduction_to_SVN#Types_of_branches|Types of Branches

Patsyblefebre: Category:Developers/Quality Assurance

2013-01-22T04:08:25Z

Category:Developers/Quality Assurance

Patsyblefebre: Gramps

2013-01-22T04:05:46Z

Gramps

Alexander Fomichev at 05:37, 5 December 2012

2012-12-05T05:37:02Z

Alexander Fomichev at 05:34, 5 December 2012

2012-12-05T05:34:30Z

Romjerome: Undo revision 34591 by GeorginaFrancis (talk)

2012-02-23T14:17:04Z

Undo revision 34591 by GeorginaFrancis (talk)

GeorginaFrancis at 09:08, 23 February 2012

2012-02-23T09:08:21Z

Lcc: Undo revision 33470 by NannieZamora (talk)

2012-01-13T14:06:40Z

Undo revision 33470 by NannieZamora (talk)

NannieZamora at 12:22, 13 January 2012

2012-01-13T12:22:45Z

Romjerome: Protected "Using the bug tracker" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2011-12-27T13:20:36Z

Protected "Using the bug tracker" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

@@ Line 19: / Line 19: @@
 #The '''Feature Requests''' project is a place for recording requests for new features.
-#The projects with names that look like '''Gramps x.x.X''' are where issues are reported that apply specifically to a maintenance branch (see [http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN#Types_of_branches Types of Branches]). A separate project exists for each maintenance branch.
+#The projects with names that look like '''Gramps x.x.X''' are where issues are reported that apply specifically to a maintenance branch (see [[Brief_introduction_to_SVN#Types_of_branches|Types of Branches]]). A separate project exists for each maintenance branch.
-#The '''Gramps Trunk''' project should only be used by developers and testers of the latest code. It is a place for recording issues that only apply to the trunk in Subversion (see [http://www.gramps-project.org/wiki/index.php?title=Brief_introduction_to_SVN#Types_of_branches Types of Branches]). There is only one "Gramps Trunk" project because there is only one trunk in the Subversion repository
+#The '''Gramps Trunk''' project should only be used by developers and testers of the latest code. It is a place for recording issues that only apply to the trunk in Subversion (see [[Brief_introduction_to_SVN#Types_of_branches|Types of Branches]]). There is only one "Gramps Trunk" project because there is only one trunk in the Subversion repository
 ==== How to proceed ====

← Older revision		Revision as of 04:08, 22 January 2013
Line 52:		Line 52:

	[[Category:Developers/General]]		[[Category:Developers/General]]
		+	[[Category:Developers/Quality Assurance]]

@@ Line 1: / Line 1: @@
 {{languages|How to report bugs}}
-The bug/issue tracker for GRAMPS is located at the following URL: http://bugs.gramps-project.org
+The bug/issue tracker for Gramps is located at the following URL: http://bugs.gramps-project.org
 This bug/issue tracker allows users and developers to log new issues and track them as they progress. Please take some time to read the issue tracker instructions below and read '''[[How to create a good bug report|how to create a good bug report]]'''. Also, have a look at '''[[Known_issues|known issues]]''' and '''[[Common_problems|common problems]]'''.
 ==Report a bug==
 ===1. Login===
-To report a bug, you must have a login account on http://bugs.gramps-project.org, which is the GRAMPS bug tracker. When you create a user account, remember that it can take up to 12 hours before a notification email is send to you. Only after clicking on the link in the email can you submit bugs. Your email address will be handled confidentially.
+To report a bug, you must have a login account on http://bugs.gramps-project.org, which is the Gramps bug tracker. When you create a user account, remember that it can take up to 12 hours before a notification email is send to you. Only after clicking on the link in the email can you submit bugs. Your email address will be handled confidentially.
 ===2. Search existing bugs===
@@ Line 13: / Line 13: @@
 ===3. Submit new bug===
-Click on Report Issue, and enter the required information, see below on how to select the project to which the bug belongs. Be verbose, the developers are bad at mind reading. Do not forget to list the GRAMPS version you are using. You can check this in GRAMPS by clicking in the GRAMPS program the Help menu, option About.
+Click on Report Issue, and enter the required information, see below on how to select the project to which the bug belongs. Be verbose, the developers are bad at mind reading. Do not forget to list the Gramps version you are using. You can check this in Gramps by clicking in the Gramps program the Help menu, option About.
 ==== Projects ====
@@ Line 25: / Line 25: @@
 The first step in submitting an issue on the tracker is to determine which project it belongs to.
-*If the issue represents functionality that does not currently exist in GRAMPS, then the issue should be filed under the '''Feature Requests''' project.
+*If the issue represents functionality that does not currently exist in Gramps, then the issue should be filed under the '''Feature Requests''' project.
-*If the issue represents a problem with functionality that has been released in a stable release of code, then the issue should be filed under the project that corresponds to the maintenance branch for that release. For example, a bug found in GRAMPS 3.2.6 should be filed under the '''Gramps 3.2.X''' project.
+*If the issue represents a problem with functionality that has been released in a stable release of code, then the issue should be filed under the project that corresponds to the maintenance branch for that release. For example, a bug found in Gramps 3.2.6 should be filed under the '''Gramps 3.2.X''' project.
 *If the issue represents a problem with functionality that only exists in trunk, or the problem exists in trunk, but not any stable releases, then the issue should be filed under the '''Gramps Trunk''' project.
@@ Line 42: / Line 42: @@
 ==Bug triage==
-Help the GRAMPS project [[Bug triage]].
+Help the Gramps project [[Bug triage]].
 ==Syntax==

@@ Line 1: / Line 1: @@
-{{languages|Using the bug tracker}}
+{{languages|How to report bugs}}
 The bug/issue tracker for GRAMPS is located at the following URL: http://bugs.gramps-project.org
 This bug/issue tracker allows users and developers to log new issues and track them as they progress. Please take some time to read the issue tracker instructions below and read '''[[How to create a good bug report|how to create a good bug report]]'''. Also, have a look at '''[[Known_issues|known issues]]''' and '''[[Common_problems|common problems]]'''.

@@ Line 1: / Line 1: @@
-{{languages}}
+{{languages|Using the bug tracker}}
 The bug/issue tracker for GRAMPS is located at the following URL: http://bugs.gramps-project.org
 This bug/issue tracker allows users and developers to log new issues and track them as they progress. Please take some time to read the issue tracker instructions below and read '''[[How to create a good bug report|how to create a good bug report]]'''. Also, have a look at '''[[Known_issues|known issues]]''' and '''[[Common_problems|common problems]]'''.