On 06.10.2012 07:52, Olemis Lang wrote: > On 10/5/12, Joachim Dreimann <[email protected]> wrote: >> Hi all, >> > :) > >> I've started preparing Release 0.2 today, having volunteered to be Release >> Manager. > In spite of being able to trace tickets to the corresponding release > where associated changes have been included (... considering the fact > that no meaningful version's been defined at the moment ...) it'd be > nice if we could split current Release 2 milestone into two e.g. > «Release 2 beta» containing all tickets with patches that will be > distributed with 0.2.0 , plus «Release 2 final» containing tickets > scheduled for current «Release 2» with pending patches . > > Besides IMO we should take some time to start writing tests and setup > CI . This is mainly considering the fact that the number of > contributors has increased recently and more concurrent changes > against a more complex implementation means a higher probability to > e.g. introduce regressions . > > '''PS:''' Feel free to use any other milestone name .
Indeed. Version numbers are cheap, 0.x numbers doubly so. I wouldn't worry about a beta; just release whatever's ready and stable. If the next release comes in two weeks, I don't see that as a problem. -- Brane -- Certified & Supported Apache Subversion Downloads: http://www.wandisco.com/subversion/download
