3.18, 3.19 branches

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

3.18, 3.19 branches

Jean Chevalier
Why are commits being done atop the 3.18 branch instead of 3.19? Is it
because a breaking change in 3.19? Will 3.18 eventually turn into 3.20? Or
is 3.18 only of interest for selected developments?
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: 3.18, 3.19 branches

Richard Hipp-3
On 6/18/17, [hidden email] <[hidden email]> wrote:
> Why are commits being done atop the 3.18 branch instead of 3.19? Is it
> because a breaking change in 3.19? Will 3.18 eventually turn into 3.20? Or
> is 3.18 only of interest for selected developments?

Some project might consider 3.19.3 too high risk and prefer to
continue using a version of SQLite that has been in wide-spread
circulation for a while.  (I disagree, but it is not my place to
decide these things for other projects.)  Version 3.18.2 is just
3.18.0 with a couple of important bug fixes backported from 3.19.3.
Some release managers are more comfortable shipping with 3.18.2 than
with 3.19.3.
--
D. Richard Hipp
[hidden email]
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Loading...