Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

[tdf-discuss] Re: RC2 - no 3.4.0.x tag in help -> about libreoffice


Think harder. The point is that if a Release Candidate build is determined
to be
good *enough* to be released, the *exact* *same* *bits* will become the
release
then instead. Just the names of the download directories, downloadable
file, etc
are changed as necessary. So if the Help:About would say RC2, and RC2 would
be
turned into a release, then the release would also say RC2. Which would be
confusing, wouldn't it?


It's not a matter of thinking harder. The program I'm used to that uses
Release Candidates simply changes the version number (even if no changes are
made to the code). So RC2 is build 7599 and the OEM is 7600. But for the
user what matters is that one shows in the About box as RC2 and the other as
Final.

I know that makes no sense for developers but the About box is for the
users... so it should be user friendly ;)


--
View this message in context: 
http://nabble.documentfoundation.org/RC2-no-3-4-0-x-tag-in-help-about-libreoffice-tp2994857p3000082.html
Sent from the Discuss mailing list archive at Nabble.com.
-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
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.