"Bert Huijben" <b...@qqmail.nl> writes: > ***** > But I would also like to recommend/ask that we start bundling Sqlite with > Subversion, to allow optimizing for the specific version we use for a > release without risking future breakage. > *****
Are we able to get advance notice of SQLite security releases or do we have to react to public releases? Take 3.7 for example, how many of the releases fixed security issues and would have triggered a new Subversion release? Do we allow developers to make changes to our copy of SQLite or do we insist that the Subversion copy is pristine? I identified umask as an SQLite problem in January and SQLite released in March. Suppose we had wanted to release Subversion in February, would we have released with the umask bug, or patched our copy of SQLite or delayed the release? -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
