On Wed, 30 Jan 2013 08:36:26 +0100 Fred Cooke <[email protected]> wrote:
> I'm not annoyed, its not my place to be annoyed here. > > I just consider a tag as sacred, and skipping a version as something not to > be ashamed of. Arch ok, but here there is nothing deployed anywhere for anybody until I press the Release button on staging stuff on nexus. Why then to create a new tag, if it is just for pleasure I don't see any value to do this. Moreover I will have two tag with same version ? bit confusing to me :( > Version 2 of http://semver.org/ is pretty good. Version 1 had issues, but > rather than fix those and still call it 1, he called it 2 :-) > > See point 4. I guess what it comes down to is how you define "released". To > me a tag and a binary are synonymous. until vote is ok, it is not a release, it exists only on a temporary place to test it. > > And yes, I understand the staged thing, but it's still evil to redistribute > a new one, even if not to central, with the same version IMO. I do not agree, otherwise what is the meaning of the staging ? Moreover tagging something which will never be on central has no point to me, no? I do not see any value to keep stuff for nothing, I like rules but still I am not a sheep :D IMHO you can't apply same rules for a application versionning, public api versionning and a parent-pom with no api at all! Here we don't use a simple versionning rule, just an increment a number so why should we pass directly to version 32, as the version 31 will never be in central ? > > Apologies for the hijack. I won't vote, I've said too much already :-) Arch please vote then, My vote is not about how to remove a bad tag but on release of a new mojo-parent ;) tony. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
