Skip to content

Revise definition of patch version and modify release practice accordingly #973

Closed
@rjyounes

Description

@rjyounes

Our current definition of patch release:

"Correction of an error, even if not backward-compatible, does not require a major release. The expectation is that users will not have implemented against an obvious error. This would be a patch."

Semver definition of patch release:

"Given a version number MAJOR.MINOR.PATCH, increment the ... PATCH version when you make backward compatible bug fixes"

We are therefore not following semver in this regard. I think we should update our policy and our release practice accordingly. (Note: we have as yet never issued a non-backward-compatible patch release.)

Metadata

Metadata

Assignees

Labels

area: documentationstatus: fast trackA low impact change for which a PR can be submitted without group discussion

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions