Handling trackers: Difference between revisions

From FreeMind
Jump to navigationJump to search
No edit summary
Line 13: Line 13:
When an issue relating to ''unstable package'' is solved in CVS, it shall be closed only after the solution has been made available in another beta or RC release in instable package. As soon as the issue is solved in CVS, it should be assigned the group ''FreeMind 0.9.0 - Fixed in CVS'', given ''0.9.0'' is the unstable package.
When an issue relating to ''unstable package'' is solved in CVS, it shall be closed only after the solution has been made available in another beta or RC release in instable package. As soon as the issue is solved in CVS, it should be assigned the group ''FreeMind 0.9.0 - Fixed in CVS'', given ''0.9.0'' is the unstable package.


===Groups in Bugs tracker===
==Groups in Bugs tracker==
{| {{Table style}}
{| {{Table style}}
! Group
! Group

Revision as of 08:21, 29 January 2008

Closing feature requests and bugs

Stable package

When a developer solves in CVS a feature request or a bug (both an issue) relating to stable package,

she should assign the issue to the group FreeMind 0.8.0 - Fixed in CVS leaving the issue Open, given 0.8.0 is the stable package.

When a final release containing the solution is out,

the issue should be assigned to the groups FreeMind 0.8.0 and set to Closed.

Unstable package

When an issue relating to unstable package is solved in CVS, it shall be closed only after the solution has been made available in another beta or RC release in instable package. As soon as the issue is solved in CVS, it should be assigned the group FreeMind 0.9.0 - Fixed in CVS, given 0.9.0 is the unstable package.

Groups in Bugs tracker

Group Note
FreeMind 0.8.0
FreeMind 0.8.0 - Fixed in CVS
FreeMind 0.9.0
FreeMind 0.9.0 - Fixed in CVS

Links