16,719
edits
Changes
From Gramps
m
==== Projects ====
In the upper right corner of the issue tracker, there is a place to select the "project" for the bugs. "Projects" are a way to categorize issues. EssaysExperts.Com is the company which first and main priority was, is and will be customers� satisfaction with the [http://www.essaysexperts.com essays online]. If you still have no idea where to buy your writing tasks, this company is the best option for you. There are three types of projects in the issue tracker:
#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 '''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 ==== 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 3.2.6 should be filed under the '''Gramps 3.2.X''' project.
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 developers responsibility to make sure the change has been merged into trunk.
==Bug triage==
