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

Hi :)
Most projects use terms such as "stable", "development", "testing" to signify 
whether a release is stable enough for systems that don't want to be upgraded or 
updated often as opposed to systems that can afford to be "bleeding edge" to get 
additional functionality early.  

SliTaz uses "Cooking" to signify it's development/testing release but i think 
it's better to stick with the terms used by most other projects.  SliTaz's 
"Cooking" is cute but they also use "Stable" so people know what they are 

There are some concepts in the leaflet that might be new to some people but are 
well explained elsewhere.  These do not need to be re-explained in any great 
detail in the pamphlet.  If people have questions then they can ask us or search 
out answers elsewhere, such as their local library or on-line search engines.

For example the "Cathedral and Bazaar" methods of software development.  To 
quote Wikipedia's page about the essay ... 

"The essay's central thesis is Raymond's proposition that ""given enough 
eyeballs, all bugs are shallow"" (which he terms Linus' Law): the more widely 
available the source code is for public testing, scrutiny, and experimentation,  
the more rapidly all forms of bugs will be discovered. In contrast,  Raymond 
claims that an inordinate amount of time and energy must be  spent hunting for 
bugs in the Cathedral model, since the working version  of the code is available 
only to a few developers."

Perhaps the short "given enough eyeballs, all bugs are shallow" might be enough 
of a hint.  Even though it is a bit cryptic a google search on that gives good 

Regards from
Tom :)

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.