296
edits
Changes
→3. Submit new bug: this pearl must be preserved for posterity. Would you submit a bug with "forgot what happened" being the only meaningful info in it?!
#The '''Feature Requests''' project is a place for recording requests for new features. #The projects with names that look like "'''Gramps x.x.X" is ''' 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 '''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
== Submitting Issues == How to proceed ====
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 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 23.2.10 6 should be filed under the "'''Gramps 23.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. == Resolving bugs ==This information is for the developers following up on the submitted issues.
In general, when resolving an issue, it is always a good idea to add a note with the SVN revision number of the commit that fixed the problem.
When resolving issues in a maintenance branch, one should always set the "Fixed in version" field to the version of the next release that will be made from that branch. This is done so that the issue properly appears in the ChangeLog page for that project (http://bugs.gramps-project.org/changelog_page.php).
Bugs in maintenance branch projects should not be marked as closed until the developer has committed the change into the corresponding maintenance branch. Additionally, it is the developer's developers responsibility to make sure the change has been merged into trunk. ==Bug triage== Help the Gramps project [[Bug triage]]. ==Syntax== [http://www.mantisbt.org/ Mantis bug tracker] uses its own syntax code :* ''#'' before a bug number writes a link to the bug.* ''~'' before a comment number writes a link to the comment, same as : ''{url}#c{comment number}''.* we can try to use some HTML tags into text field, like : <code> < pre >< /pre > < i > < / i > < b > < / b></code> [[Category:Developers/General]][[Category:Developers/Quality Assurance]]