On 10/10/2013 12:24 AM, Torsten Curdt wrote:
Every now and then I keep getting requests via private mail asking to
release javaflow as it seems to be working for people. Yet I know there is
still so much essential stuff to fix for a 1.0 release.
Crossing over to the other thread: I know on github I would made a 0.x
release already ages ago but knowing I won't have time to work on it
anymore I keep pushing this out at commons.
Wouldn't this be a case to allow and use intermediate milestone releases?
Using a 1.0-Mxx version would make still clear to the users things haven't
settled yet (API wise), so should not limit or restrict making API changes
before a final 1.0 release, but would help both the community and the project
moving. More likely to incite further involvement and contributions, etc.
Being 'stuck' on getting a (final) 1.0 release out because everything should be
settled and 'frozen' (API wise) first doesn't make sense to me at all.
"Release early and often" really is what keeps open source projects moving
forward, *any* policy which blocks that is plain wrong and should be fixed.
Note: I'm not saying I'm against the strict versioning rules, but those should
NOT block getting to a 1.0 release easily.
And I don't think they do. Isn't this where Milestone releases are meant for?
Ate
Release and put into dormant?
It's a strange situation.
cheers,
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
