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. > +1 I really don't object to a more "Semantic Versioning" release, but I think those who really want it are fooling themselves into thinking it will require less mental effort. Still, it doesn't hurt me or help me to stick with one or change to the other. > "However, the current tarball naming conventions only reserve two digits > for the Y and so the naming format for downloads will need to be revised in > about 2030." > > If we're still actively using SQLite3 for new projects in 2030 (i.e. we > haven't moved on to SQLite4 or something else entirely), they'd better > award the dev team a solid platinum prize of some sort. > If this change is being made at this time, why not just go ahead and make a tarball naming convention change now too. Symlinks could easily accommodate the current convention for as long as is needed / desired. Given the fact that the last two digits of the current tarball naming convention will forever after be 00: filename-3XXYYZZ.ext means filename-3YYZZ00.ext Go ahead and either start using: filename-3YYYZZZ.ext (note below) Or alternatively: filename-3-Y-Z.ext (or some variation thereof) The 3YYYZZZ format has two potential flaws. One is the relative sort order, in that field widths are different in length and quantity. Any future change will have this problem, so I ignore it. The other is potential collisions with previous releases. They should be relatively rare. They can be completely avoided with something more like filename-3YYYZZZb.ext (or any other character in place of b to indicate it is part of a different sequence; it can be prefixed or suffixed to the version number string depending on preferences). -- Scott Robison
