2017-07-01 21:50 GMT+02:00 Richard Hipp: > However, I know it > does seem to upset some people when Fossil ships with a non-release > version of SQLite.
I wouldn't be upset, it just wouldn't spread out fossil 2.3 as much as desired. I'm afraid various maintainers will skip fossil 2.3, and just wait for 2.4. Or they simply hack fossil, eliminating the need for the SQLITE_PREPARE_PERSISTENT flag. > I suggest we go "pencils down" 2017-07-14. Only bug fixes are > allowed on trunk after that point, until the release. This can be solved by using a "release branch", but I'm sure I don't need to explain that ;-) My suggestion: <http://www.fossil-scm.org/index.html/info/1eab060a84f24fa5> So: - just continue developing on trunk, as usual. - around 2017-07-14, merge everything from trunk to branch-2.3. - development can just continue on trunk, no need for 'pencils down' - bug-fixes appearing on trunk can be cherry-picked to branch-2.3, as far as desired. - on 2017-07-21, release fossil 2.3 from the release branch. Advantage: Fossil-2.3 will ship with SQLite 2.19.3, while trunk development can continue normally. The self-hosting fossil service can continue to use SQLite 2.20 beta. Regards, Jan Nijtmans _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
