On Thu, Oct 8, 2015 at 8:36 AM, Simon Slavin <slavins at bigfraud.org> wrote:
> > On 8 Oct 2015, at 2:38pm, Richard Hipp <drh at sqlite.org> wrote: > > > If accepted, the new policy will cause the next release to be 3.9.0 > > instead of 3.8.12. And the second number in the version will be > > increased much more aggressively in future releases. > > I approve of this particular release changing the Y value (i.e. being > 3.9.0) since it allows SQLite to create and change databases to a format > which can't be opened with previous versions. > I don't care a rat's behind what number changes next in the naming convention 3vvuupp <bb...> where vv = 'version', uu = 'update' ; pp = patch <optional bb = build (usually a timestamp, date or hash I guess)> As someone else noted what is the criterion to call a revision major/minor version and is one of them applicable in the transition 3081101 to 3090000 respectively 3081200. If the incompatibilities are as great as feared I'd go to for a new vv, if as small as hoped, let's feel free and modest call it "just an" update. My ?0.02 Kind regards |?Cordiali saluti | Vriendelijke groeten | Freundliche Gr?sse, Klaas `Z4us` V ?- LinkedIn 437429414
