[X] -1 No - Flume should adopt some other policy I would personally expect that soon after release 1.1.0-beta1 there will be stable release 1.1.0 that won't contain any new features but just bug fixes. But as far as I know, we're currently making releases just to provide snapshots for user testing and there is no goal to get branch 1.1.0 stable and eventually release 1.1.0, right? We will just relase 1.1.0(-beta) and then move on to version 1.2.0(-beta). I believe that it might lead to user confusion as they might expect something that won't happen.
I would personally suggest to adopt "Apache Commons" version policy after flume-ng will be consider production ready. Jarcec On Mon, Mar 19, 2012 at 04:47:26PM +0900, Juhani Connolly wrote: > [X] +1 Yes - Flume should adopt this policy > > Anything that makes it clear to users what state the software > they're working with is in > > On 03/19/2012 04:10 PM, Ralph Goers wrote: > >I would like to propose that Flume adopt the release numbering scheme > >followed by Apache Commons which can be found at > >http://commons.apache.org/releases/versioning.html#Release_Numbers. > > > >Please vote > > > >[X] +1 Yes - Flume should adopt this policy > >[] +0 Abstain - I don't have a preference > >[] -1 No - Flume should adopt some other policy > > > >Ralph >
signature.asc
Description: Digital signature
