Vincent Massol wrote:
<SNIP>
Thus I think that after we release B6 (possibly on
Wednesday) we should
move the remaining issues in RC1 and not do a new B7. Once we start RC
we shouldn't put any new feature but rather commit any new features on
the trunk only.
WDYT?
I'm using OSS regularly and I was even a member of some projects and
what I found out is that most of the time people are not sure when to
declare 1.0. Net is plagued with OSS project sticking to 0.9.x versions
for years. There is a lot of reason to do that:
* you are doing this for yourself, therefore it must be perfect
* you want to freeze external interfaces for good
* you are not sure what should be in version 1.0
Due to the dynamic nature of the software it is not really possible to
satisfy all this criteria. Software is changing all the time. That's why
we got agile methods and refactoring.
Reluctance to declare 1.0 turns away users because they think software
is not good until 1.0, and most of these projects are. So, forget about
dates, but rather decide what features should be present in 1.0, cut the
rest, fix major bugs and release it. I think you are on the good track.