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


On 02/23/2012 08:25 AM, Tanstaafl wrote:
On 2012-02-22 1:12 PM, Chris Morgan <chris@lynxinfo.co.uk> wrote:
I am very sceptical about the so-called benefits of
releasing on a strict time-schedule.
The process seems to favour new features over bug fixes.
I thought the old way was better - release it when it's ready.

The problem with this method is - it is *never* ready (meaning, bug-free)...

I like the new release schedule... it ensures that new features are introduced faster, and get better testing... everything simply speeds up.

Yes, it does create some potential for breakage, but as long as you are prepared (can roll back if you get bit by a show-stopper), it shouldn't be a real problem. Also, what may be a show-stopper bug for one person is irrelevant to another (not everyone uses the same features).
Good point about show stoppers. Also, what is a minor annoyance for one may be disastrous for another because of the relative importance of the feature to each.


--
Jay Lozier
jslozier@gmail.com


--
For unsubscribe instructions e-mail to: users+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/users/
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.