[Libreoffice] Git tags: why not "3.3.4-rc2" instead of ""

Miklos Vajna vmiklos at frugalware.org
Thu Aug 18 07:15:09 PDT 2011

On Wed, Aug 17, 2011 at 12:27:14PM +0200, Gioele Barabucci <gioele at svario.it> wrote:
> I was wondering why the git tags are named `` for 3.3.4-rc2 
> instead of the more natural `3.3.4-rc2` or the more common `v3.3.4-rc2`. 
> I am used to see as the second bugfix release for 3.3.4, or, in 
> more mathematical terms, > 3.3.4 = I hope 3.5-rc1 will 
> not be tagged as 3.5.1.
> Is this behaviour a leftover of the SVN workflow? Could it be changed?

The problem is that when 3.4.x.y is tagged in git, nobody knows if it
will be the last RC or not. The final 3.4.x release is always the same
as the last RC, and there is only one 3.4.x.y tag for them.

An alternative would be what KDE does (or something similar, Lubos may
know better): when the RC is supposed to be the last one, then tag it as
3.4.x, then release the tarballs in a private packager list, repack
tarballs without incrementing version number when critical issues found,
then release to the public.

IMHO not having private source tarballs and not having private repacks
worths having two (3.4.x-rcy and 3.4.x.y) versionings.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/libreoffice/attachments/20110818/3716d776/attachment.pgp>

More information about the LibreOffice mailing list