[Geoprisma-dev] Ticket and fix informations
Alexandre Dube
adube at mapgears.com
Fri Dec 2 11:41:19 EST 2011
Hi devs,
GeoPrisma 1.0.0 is out, with it comes the first official branch 1.0.
So, from now on, patches and commits will be handled a little
differently. Here's some details on the matter. It will include more
than just new infos for documentation purpose.
The properties of a ticket should be set as follow :
=== Version ===
Set to the version (branch name) where the bug was found (if a bug).
If it's a new feature, it should always be set to "trunk".
=== Milestone ===
In which release the bug/feature should be fixed/added.
(defect, stable widget or anything else) If the ticket is a bug
featuring a widget, if the widget is "stable" the Milestone should be
set to the next release of the current official branch only (for
example, the current one is 1.0.1). If it's a serious bug (security),
then it should be set to current current next release of current branch
and all previous "still maintained" branches as well.
(defect, unstable and deprecated widgets) If the widget is "unstable"
or "deprecated", it should be set to the future branch release (for
example, the current one is 1.2.0)
(enhancement, task) If the ticket is an enhancement or a task, the
Milestone should be set to the future branch release
Regards,
--
Alexandre Dubé
Mapgears
www.mapgears.com
More information about the Geoprisma-dev
mailing list