Hi all
This is my final request about this subject.
Can you please make some sense out of the version naming convention?
I was about to reinstall version 3.4.4 (after it was overwritten by
3.5.0 Beta0) and I already had an unpacked install folder on my
desktop. The only way I could verify that it was for 3.4.4 final, was
to run the installer and check what would be the name of the generated
folder. Since it had the same code (4eb10e5c) it was the same
version...
Another situation: I download a master build from a tinderbox. How do
I know the build included? How do I know if the source it was
generated from is newer or older than the one I already have? Easy.
Just install, open the About box and check if 4f11d0a-adcf6d5-c4bb9bd
is greater or smaller than 4f11d0a-adcf6d5-c4b29bd (just an example)
If the latest final version was named 3.4.4 and build was 402 couldn't
it simple be named 3.3.4.402?
And this new version can't it be simply named 3.5.0.xxx???
And keep this code constant in the installer, the about box, the
master builds, etc?
I think this is not an unreasonable request... Maybe the codes you use
are perfect for developers, but this is a community and not all users
(namely those in QA, l10n, etc, let alone common users) are version
experts.
Here is a proper bug request about this
https://bugs.freedesktop.org/show_bug.cgi?id=43031
Please help us to contribute to this project.
Regards,
Pedro
Context
- [Libreoffice] Naming builds. Please??? · Pedro Lino
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.