IMO there is value in having verion-SNAPHOT when we're developing on a branch as e.g. the Sandesha2 1.1 branch was made dependant on the Axis2 1.1-SNAPSHOT so it didn't decome dependant on the trunk.
I'm ambivant about using a version number on the trunk. It's easy enough to solve when we next branch (just bump the number on the trunk) but it's probably clearer to users that we don't endorse the SNAPSHOTs if there isn't an associated version number. David On 22/11/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
Hi Jochen and all, SNAPSHOT is a SNAPSHOT and it has no version in it, IMO. What do you gain by putting a number with a SNAPSHOT. Snapshots are mostly unstable versions of a project and we don't wanna know after which version it was created. Let me ask this question also, who will use a SNAPSHOT of a project, say a snapshot of Axis2? I think projects like Sandesha will use it. They will depend on trunk and not on any of the branches. Maintaining branch versions is an internal version, IMO. So I always prefer to have snapshot without a version number in it. So +1 for just snapshot. My 2 cents. -- Chinthaka Jochen Wiedmann wrote: > Chamikara Jayalath wrote: > >> Could u please explain a bit more. What do u think the version of the >> 'trunk' should be ? >> (until we move to maven 2) > > What's wrong with "1.2-SNAPSHOT" (Maven convention) or "1.2-dev", > which Jakarta used to have? I believe we agree, that subsequent 1.1.x > versions won't come out of the trunk, and we can change that to > 2.0-SNAPSHOT or whatever at any time, should that be desirable. > > Jochen > >
-- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
