Skip to content

Versioning convention for Bitcoin Core #9653

@kallewoof

Description

@kallewoof

In #8455 (comment) the versioning of Bitcoin Core was mentioned, but deemed off-topic, so I am creating this issue to address the fact that Bitcoin Core uses a non-traditional scheme for version releases.

To me, the first (traditionally "major") version number is 0 for as long as a product is considered non-production-ready, and >0 for production-ready, and bears significant meaning in this sense.

Possible mind-sets:

  1. It is agreed that Bitcoin Core is past beta stage, even if blockchains and crypto-currencies are new technologies. The initial 0. is dropped, meaning that the next version is 14.0 not 0.14.0.
  2. A set of milestones leading up to a 'production ready' version of Bitcoin Core are established, and this is referred to as the 1.0 release.
  3. This discussion is irrelevant.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions