Gioele Barabucci píše v St 17. 08. 2011 v 12:27 +0200:
Hello,
I was wondering why the git tags are named `3.3.4.2` 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 3.3.4.2 as the second bugfix release for 3.3.4, or, in
more mathematical terms, 3.3.4.2 > 3.3.4 = 3.3.4.0. 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 tag version is used for the source tarballs. They are used by distro
packagers. They do not like letters in the version. The letters work
well for alpha/beta/rc because the alphabetical order is correct. But
how to name the final build? 3.4.0 is considered as an older version
than 3.4.0rc1 by rpm. We do not want to keep rc in the final build
because it confuses users.
From my point of view. Only developers and packagers take care of the
tag name. The current naming scheme is pretty clear for developers and
useful for packagers, so I vote to keep it ;-)
Best Regards,
Petr
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.