klaus-jürgen weghorn ol píše v So 21. 04. 2012 v 10:49 +0200:
Hi Fridrich, *,
this mail never reached the l10n@ and projects@ but only the LibO-QA. Is
there a problem with the mail-system or something else?
It is by purpose. We should probably update the subject to make it more
clear. What about the following?
[ANN] LibreOffice 3.5.3 RC1 builds available for pre-testing
Am 20.04.2012 12:44, schrieb Fridrich Strba:
Builds are now being uploaded to a public (but non-mirrored - so don't
spread news too widely!) place, as soon as they're available. Grab
them here:
The above paragraph explains why we do not spread the information too
much.
http://dev-builds.libreoffice.org/pre-releases/
This is provided by a single machine and it can't handle too many
people.
If you've a bit of time, please give them a try& report *critical*
bugs not yet in bugzilla here, so we can incorporate them into the
release notes. Please note that it takes approximately 24 hours to
populate the mirrors, so that's about the time we have to collect
feedback.
The above paragraph explains why we announce the pre-release at all :-)
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
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.