[Subject changed to mark it as a proposal] On 20/05/10 14:29, Andrea Aime wrote: > I'd prefer to just keep the poms in the branch unmodified as > well, using 2.0-SNAPSHOT. > One less moving part in the release process, and I fail to see the > advantage of using something like 2.0.3-SNAPSHOT.
We are stuck on this convention for 2.0.x because 2.0.3-SNAPSHOT is a later version than 2.0-SNAPSHOT. Our next opportunity stop making work for ourselves is when we release 2.1.0 and make 2.1.x as the new stable branch. I propose that, when 2.1.x is branched, we keep the pom version as 2.1-SNAPSHOT, and similarly for subsequent branches. To clarify, I propose that for 2.1.x and later: (1) Only tags should get their pom versions updated when a tag is made. (2) The parent branch is not changed when a tag is made. (3) Trunk pom versions are still updated when a new stable branch is made, with the new branch inheriting the old pom version (this is what we do now, so this does not change). -- Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
