Re: [mantisbt-dev] To count or not to count?

[Gianluca S. <gi...@gm...>]

On 7/26/07, Jeferson Oliveira <jef...@gm...> wrote:
> Thinking about it I have noticed that ChangeLog shows all resolved bugs,
> even when not yet closed, as resolved in version X.x.x. In my scenario,
> "Resolved" means that some developer have fixed some code, and the test
> team is working on a test version. When the test is ok, the issue is
> closed. So "Closed" means that the fix is able to be part of the next
> release.
>
> Considering that between the "Resolved" and "Closed" status some version
> could be released, and the code wasn't committed yet, shouldn't the
> ChangeLog consider only the closed issues? Is there some ChangeLog's
> option to indicate which status should be considered part of a version?
> Maybe a solution could be a "Released in version" field distinguishing
> the fixed version from the released one(?).
>

I think an option is to mark the version as "Not released" which is
doable in the "Manage project" page. IIRC, versions not marked as
released are not shown in the Changelog page so your workflow would
be:

* Create new version as "not released"
* Mark bugs as fixed in that release
* test bugs until all are closed
* mark the version as released
* release