On Tuesday 03 May 2016 21:27:47 Richard W.M. Jones wrote: > > For historical reasons that don't really matter now, we currently > tag all releases with just the version number, eg: > > commit 6b48977cb7100e4f214b189052d4f0bf61523d11 (HEAD -> master, tag: > 1.33.26, origin/master, origin/HEAD) > Author: Richard W.M. Jones <[email protected]> > Date: Tue May 3 14:49:59 2016 +0100 > > Version 1.33.26. > > Of course this isn't the way that git versions are normally tagged. > The normal convention is to use "v<VERSION>" (eg. "v1.33.26"). > > I propose that I start tagging new releases this way (see the patch > below). This shouldn't be controversial. > > The question is should I tag new releases with the "old style" tags? > I'd prefer not to. Should I go back and add "v<VERSION>" tags to all > the old releases? Again, I'd prefer not to, but could do that if > anyone thinks it's necessary.
I've seen both ways used IMHO equally, so I don't have a strong preference. Just wondering whether the right moment for changing tag naming would be when tagging the .0 of a new series. -- Pino Toscano
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Libguestfs mailing list [email protected] https://www.redhat.com/mailman/listinfo/libguestfs
