Hi,
please note that the commit deadline for 3.6.0-beta2 is today (Monday),
June 19, 2012.
NOTE: We are starting to use new version scheme:
+ 3.6.0.0.alphaX for Xth alpha release
+ 3.6.0.0.betaX for Xth beta release
+ 3.6.0.X for Xth release candidate
Advantages:
+ easy to understand for normal users, alpha, beta flags are known
from other projects, so they set reasonable expectations
+ correct alphabetical sorting in RPM, bugzilla
+ "easy" to parse (alpha/beta strings delimited by dot)
The result is that we could have the same version everywhere: git tags,
source tarballs, about dialog, bugzilla, ...
IMPORTANT: This is final decision. Please, do not start another tread.
There already was long discussion until we got into these conclusion. See
http://lists.freedesktop.org/archives/libreoffice-qa/2012-June/001822.html
See also
http://wiki.documentfoundation.org/ReleasePlan#3.5_release
http://wiki.documentfoundation.org/Release_Criteria
http://wiki.documentfoundation.org/Development/Branches
Best Regards,
Petr
--
Unsubscribe instructions: E-mail to l10n+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/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-l10n] REMINDER: Release 3.6.0-beta2 from libreoffice-3-6 branch · Petr Mladek
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.