[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Using Sqlite in libsvn_wc towards Subversion 1.9++

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Mon, 18 Nov 2013 10:41:14 +0000

"Bert Huijben" <bert_at_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*
Received on 2013-11-18 11:41:54 CET

This is an archived mail posted to the Subversion Dev mailing list.