+1 alpha and beta tags are better handled as 0.x.y version numbers in any case. once you hit 1.0.0 there should be no need for an alpha or beta tag unless you have the commitment to run the real release within a month or two
-Stephen On 15 September 2010 18:28, Dennis Lundberg <denn...@apache.org> wrote: > Hi > > I saw that John added http://jira.codehaus.org/browse/MASSEMBLY-502 with > a wish for Java 1.5. This is fine, but I think we need to discuss the > contents of the coming versions. > > Over the last year or so I've tried to get rid of as many alpha and beta > plugins as possible. We are now down to only 4 remaining, and the > Assembly plugin is one of them. In my opinion alpha and beta versions of > plugins only adds to the version confusion for our users. > > Now to the Assembly plugin. Here's what we have in JIRA: > > 2.2-beta-6: 4 out of 23 issues fixed > 2.2: 0 out of 14 issues fixed > 2.3-beta-1: 0 out of 14 issues fixed > > I propose that we shuffle these around: > > - Skip 2.2-beta-6, the next version will be 2.2 > - 2.2 will contain the 4 issues already solved for 2.2-beta-6, and > anything else (small) that we can cram in there without disturbing too > much. Remember that it won't be beta any more :-) > - The version after that will be 2.3 (not a beta), which will require > Java 1.5 > - If necessary 2.2.x releases can be branched off, while trunk continues > towards 2.3 > > > Comments? > > -- > Dennis Lundberg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
