Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

Clarify the major version bumps in CHANGELOGs #83

Open
blamario opened this issue Nov 16, 2021 · 1 comment
Open

Clarify the major version bumps in CHANGELOGs #83

blamario opened this issue Nov 16, 2021 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@blamario
Copy link

I didn't look closely into the actual commit history, but y'all seem to be trigger-happy with the major version bumps. Looking at just the changelogs, there's stuff like

## 2.0 -- 2021-11-11

- Plutus upgraded
  - `plutus` pinned to `3f089ccf0ca746b399c99afe51e063b0640af547`
  - `plutus-apps` pinned to `404af7ac3e27ebcb218c05f79d9a70ca966407c9`

How does a Plutus upgrade justify a super-major version bump? Maybe there was another reason for it, but in that case please state what it was so your downstream users can figure out what they need to change. And if there was no reason for it, then please refrain from major version bumps. They impose real costs on your users.

@kozross
Copy link
Contributor

kozross commented Nov 16, 2021

This is a policy established by @Benjmhart: specifically, in addition to the PVP, a Plutus bump imposes a major version jump. I agree, this should be documented.

@kozross kozross self-assigned this Nov 16, 2021
@kozross kozross added the documentation Improvements or additions to documentation label Nov 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants