Jean-Baptiste Faure wrote:
Am I wrong if I guess you want to see RC1 or RC2 in the name of the
version ?
I think it is not a good idea because the stable version is bit-for-bit
identical to RC2. So having RC2 in the version name would be confusing
for the stable version.
I'm aware of that. That is why I suggested to modify the name of the
installer instead to include the build number e.g.
LibO_3.4.4rc1_Build401_Win_x86_install_multi.exe
Also renaming the installation folder using the same logic to
LibreOffice 3.4 (Build 402) Installation Files
instead of the current
LibreOffice 3.4 (4eb10e5c) Installation Files
would help a lot, inclusively to know which old installation folders to
delete and to keep. E.g. I might want to keep build 400 which worked for me
(in case I need to go back) but not 401 which had a bad bug...
Can this be put to consideration? It's not such an odd request and it
doesn't involve any code changes...
--
View this message in context:
http://nabble.documentfoundation.org/Which-RC-version-tp3497781p3499408.html
Sent from the Users mailing list archive at Nabble.com.
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
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.