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 getting. 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 results. Regards from Tom :) -- Unsubscribe instructions: E-mail to [email protected] Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/marketing/ All messages sent to this list will be publicly archived and cannot be deleted
