-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [EMAIL PROTECTED] wrote: > 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?
The other thing "release" means in both worlds is tested and supported. For example I wouldn't just take the CVS codebase at some random point in time and deploy that. I would only take a release version. In fact the only time I would ever take a non-release version is to test some functionality/bug fix to ensure that the "release" version is ok. Quite simply code is only going to be used once you release it. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFn62MmOOfHg372QQRAr0eAJ94hlKjoU/Tpx2tvNv0caatWk7khQCfeDqe liaeBVlXmt9kNvi9iRnq09w= =pxXh -----END PGP SIGNATURE----- ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
