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


Hi Rainer,

Rainer Bielefeld wrote (03-08-11 16:37)

that's a 3.4 branch build - also interesting for particular research,
but not the best for my needs. Because of the new proceeding that in
future all branch fixes should be cherry picked from Master, Master
should be in a much better shape than the last one I saw is. And that
means: more testing with Master!

Though I think it will not be a general rule for all future versions that fixes will be picked from master .... of course I agree with you that more testing on the master and more regular available builds, are important. Sorry that I did not pick from the issue that you pointed to the master build in particular.

My hope was that Website team might find a way to make sure that no
Master will be deleted before a new one has been uploaded.

Tomorrow I will ask again for more WIN Master builds.

From IIRC the dev-list I understand that it does have the attention of people. But you may have seen that yourself.

Regards,

--
 - Cor
 - http://nl.libreoffice.org


--
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


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.