I guess part of problem here is because a lot of people assume that the maven artifact version represents what is going to be our next release and then, if it's set as 2.0-SNAPSHOT, it means our next release would be 2.0. But I tend to take these two pieces as two different things, the maven pom version is a maven requirement, and the release version is discussed at some point by the community and would be set during branching for the release.
Now, let's get back to a scenario, and just use Tuscany SCA before 1.0 release. Although we had 1.0-SNAPSHOT in the maven pom, we were discussing the releases, and properly setting the right pom version when we were creating the branches (e.g 0.90, 0.91, etc) This is just to say why I think it would be ok to leave the pom version as 2.0-SNAPSHOT. But I don't have strong feelings, as long as there is some prefix to the pom version. So if people would like to move it as 1.x-SNAPSHOT or 1.some number-SNAPSHOT I'm +1. On Fri, Jun 6, 2008 at 12:44 AM, Mike Edwards <[EMAIL PROTECTED]> wrote: > Ant, > > +1 in general - by why not simply choose a number, rather than "x"? > - the problem with "x" is "what comes next?" > > Yours, Mike. > > ant elder wrote: >> >> Lots of different views so far on this thread, better than no one replying >> :) I'm tempted to go with "1.x-SNAPSHOT" as I think from whats been said >> most would be ok with that, please say if you would _not_ be unhappy with >> it. Note that all other projects I've looked at use either a specific >> numeric number followed by the "-SNAPSHOT" suffix, or else just the string >> "SNAPSHOT" for the trunk version, so having the letter "x" as part of our >> version number makes for an "unusual" version name. Don't see why it >> shouldn't work though. >> >> ...ant >> > > -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/
