--- [EMAIL PROTECTED] wrote: > In some since, all changes to SQLite are released immediately. Anybody > can download the latest changes from CVS or look at the timeline > (http://www.sqlite.org/cvstrac/timeline) see the changes and download > patches. So source code is released continuously. All an official > release does is increment the version number and provide binaries for > people who don't are can't compile for themselves. So "release" in > the SQLite and open-source world means something very different than > "release" for commercial software. In the commerical world, the changes > are unavailable until released. For SQLite, a release merely means that > the changes are available in a more convenient packaging. > > How do these varying definitions of "release" effect this argument, > do you suppose?
Keep in mind that a lot of projects that bundle sqlite source with their programs or link statically will only support official SQLite releases. It is easier to quantify a specific SQLite release number from a support perspective (bug reports, documentation, etc). __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
