Hi Friedrich,
On Fri, Mar 23, 2012 at 2:28 PM, Friedrich Strohmaier
<damokles4-listen@bits-fritz.de> wrote:
From my POV the community way for sucht thing, was to improve the
download infrastructure for testing and instead of threatening them,
This has nothing to do with the download infrastructure.
Uploading to the prerelease server was done to give testers a chance
to sanity check the releases, to prevent comments like
"How could you even push a version with such an obvious bug as RC"
We had such a problem in the very beginning, so this intermediate step
was introduced.
You could argue that this would only be necessary for betas / the .0
releases, but that's a different topic.
The prerelease one is explicitly meant to test (sanity-check) the
release before going public with it.
If it was meant to be public right from the start, then it would be
added to the mirror-network right away.
ciao
Christian
--
Unsubscribe instructions: E-mail to website+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/website/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [libreoffice-website] Re: Promoting RCs on Facebook (continued)
Re: [libreoffice-website] Re: Promoting RCs on Facebook · Friedrich Strohmaier
- Re: [libreoffice-website] Re: Promoting RCs on Facebook · Christian Lohmaier
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.