Changes

Jump to: navigation, search

Using the bug tracker

21 bytes added, 11:00, 7 November 2013
svn to git
#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 [[Brief_introduction_to_SVNBrief_introduction_to_Git#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 master branch in Subversion Git (see [[Brief_introduction_to_SVNBrief_introduction_to_Git#Types_of_branches|Types of Branches]]). There is only one "Gramps Trunk" project because there is only one trunk master branch in the Subversion Git repository.
==== How to proceed ====
*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 trunkthe master branch, or the problem exists in trunkthe master branch, 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 hash 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 developers responsibility to make sure the change has been merged into trunkthe master branch.
==Bug triage==

Navigation menu