I am not intimately involved in day to day coding and I am not attached to any of the branches or the names :) So, take this comment as a 3rd person's point of view.
1.x relays the message that 1.0 and incremental releases of 1.0 are spawned off of this version of the code. 2.x relays the message that 2.0 and incremental releases of 2.0 are spawned off of this version of the code. It is the reality that at some point in any software's life cycle, a new architecture and potentially incompatible SPIs/APIs, will come to life based on experiences learned from the existing software. Therefore, at some point there will be a 2.x version of Tuscany and it is better to not cause confusion. On 6/6/08, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > Luciano Resende 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 >>> >>> >> >> >> > I'd prefer the next logical number, 1.3 for example. > > -- > Jean-Sebastien >
