On Feb 17, 2007, at 10:54 AM, Andrus Adamchik wrote:
On Feb 17, 2007, at 11:59 AM, Kevin Menard wrote:
Fair enough. What I was hoping to achieve was some idea of when
to cut
a release. Right now we sorta just wing it. When enough issues are
closed someone proposes the vote and we go from there. What might be
nice is knowing what open issues need to be fixed before we release
2.0.3 and what can wait until a 2.0.4.
From experience I am skeptical about that. We sort of tried this
before, and it never really worked because of the volunteer nature
of the project. The most honest thing to do would be to leave "Fix
Version" blank, until the fix is actually ready to be committed.
That's been my experience as well with open source projects. Winging
it might not be the best for users but seems to work in practice. And
anyone who really really really wants a bug fixed can volunteer to
fix it.
Craig
Currently we may set it to "3.0", which is vague enough to give us
breathing space. Presetting it to 3.0M1 or anything as specific
will be too optimistic and in most cases - misleading.
Andrus
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
