Skip to content

Questions about Clickhouse Version number #12573

@vkingnew

Description

@vkingnew

After read the clickhouse change log,I Find as following:

  1. 1.1.54245, 2017-07-04 ---- 1.1.54394, 2018-07-12
    This is a stage 1.1 version,the version number named rule maybe:Major.Minor.patch

2.18.1.0, 2018-07-23 --- 19.17.6.36, 2019-12-27
the version number rule changd as :Year.Major.Minor.patch

Changed the numbering scheme for release versions. Now the first part contains the year of release (A.D., Moscow timezone, minus 2000), the second part contains the number for major changes (increases for most releases), and the third part is the patch version. Releases are still backward compatible, unless otherwise stated in the changelog.

in this period:the second version number look increase random,but end with year's end date. the new feaure appears in random version. And hard to distinguish the stable and testing version.

3.v20.1.2.4, 2020-01-22 -- now
the version number maybe: v+Year.Month.Minor.patch
vYear.Month.1.x always testing version,the v.Year.month.2.x always to introduce new feature

The period is devide by me.Could You help to introduce the history of Clickhouse Relase Number and why change the named rule. Also can introduce the release interval in every period. Wish the explain from Official,above just guess.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions