On 16/11/2006, at 3:25 AM, Richard van der Hoff wrote:
Just my opinion here, but it seems wrong to 'close' a bug when
there's no release on the horizon, because:
(a) it might be closed to you, but if the fix depends on maven 2.1
it's as good as useless to real-world users. I think that you're
not giving an accurate representation of the quality of the current
release version (and hence the urgency of a release) by closing
bugs as soon as the fix is committed to svn.
The dependency on maven 2.1 is a flaw, it should be possible to
release the plugin earlier than that.
(b) if I see a bug, I want to be able to search jira for it,
whether it's going to be fixed in the next release or not. You need
a distinction between bugs which were fixed before the current
release, and those which will only be fixed in the next release.
By default, jira searches closed bugs too, so you can use the plugin
version as your guide to availability.
Obviously, we need to improve on timely releases, especially for
plugins (and its a topic that has already been beaten to death here
recently - we are certainly working on it, and open to suggestions on
better tracking progress in general).
Given this, I don't see any need to change the way we use the closed
state or reintroduce the resolved workflow step.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
