On Fri, Jun 6, 2008 at 9:17 AM, Luciano Resende <[EMAIL PROTECTED]> wrote:
> How about 1.5-SNAPSHOT ? This would probably give us some room to have > couple releases without the necessity to keep updating the trunk pom > version. And this would probably make everybody happy :) > > On Fri, Jun 6, 2008 at 1:14 AM, ant elder <[EMAIL PROTECTED]> wrote: > > On Fri, Jun 6, 2008 at 9:05 AM, Luciano Resende <[EMAIL PROTECTED]> > > wrote: > > > >> 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. > > > > > > I agree, this is exactly the issue. But I'm not sure its that much of an > > unreasonable assumption, it does feel odd to me to have 2.0-SNAPSHOT as > the > > trunk version before there has been any decision to start working on a > 2.0 > > in trunk. > > > > ...ant > > > > > > -- > Luciano Resende > Apache Tuscany Committer > http://people.apache.org/~lresende <http://people.apache.org/%7Elresende> > http://lresende.blogspot.com/ > My feeling about this have been galvanized by our previous conversations about doing some development work at some point in the future to improve the APIs/SPIs in backwardly incompatible ways. We previously discussed this under the banner of a 2.0 code base which still sounds sensible. If we do that at some point in the future then we will have a 1.X code based which our existing users will rely on and a 2.X code base which our users may move to over time. I'd like it to be clear when working on a code base, making releases from a code base or just providing snapshots what flavour of Tuscany is involved. Releases take care of themselves but this is why I'd like to see some reference to version 1 in Trunk be maintained. We don't commit to a particular release number until the start discussing each release and cut the branch. Hence that's why I was happy with using 1.X. Regards Simon
