please note that the commit deadline for 188.8.131.52 (aka rc1) is on Monday, January 14,
The tag and branch libreoffice-3-6-5 is going to be created the day after.
Only commits with 3 reviewers will be allowed for that branch.
IMPORTANT: If there are not found serious regressions, we will release
rc1 as the final build. By other words, we will try to avoid rc2[*].
PS: Please, help with reviewing pending commits.
[*] This is a special case. QA suggested to have two weeks between 4.0.0
betas and rcs. I modified the schedule in October but it was too late to
change the feature freeze. We also could not shift the final release
date because it is synced some distro releases. The result is that 4.0.0
release is not ideal. There is only one week between rc2 and rc3 and
there is no time to do 184.108.40.206 in between. If we need 220.127.116.11 in the
end, it has to be done after 18.104.22.168 and thus 3 weeks after rc1. It is
pretty long delay and we would like to avoid it :-)
Note that the schedule for 4.1.0 and 4.2.0 release are better interlaced
with the other bugfix releases.
See https://wiki.documentfoundation.org/ReleasePlan for more details.
Unsubscribe instructions: E-mail to firstname.lastname@example.org
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
- [libreoffice-l10n] REMINDER: Release 22.214.171.124 from libreoffice-3-6 branch · Petr Mladek
Impressum (Legal Info)
: 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