You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But it means every change needs to bump up the semver's version (NB: we currently don't though), even a change fixes just a small typo, otherwise, it makes a difference between the tagged version and the published version on the website. And it'd also be confusing to have specifications published under the same version but showing different content from day to day (related: #799).
Maybe it's better to have a working draft version of the website (e.g. draft.semver.org) and do versioning precisely?
(This issue talks about the website, but it's also related to the semver's versioning, so I'm going to open it here.)
Perennial complaint. The published spec does not adhere to SemVer versioning. I think the working draft was reflected in the readme.md file for a long time, while the official site content was being generated in the other repo, and that caused some consternation due to them both having the same version number and different content.
The version should not be bumped simply because some automation republishes the content, but it should get bumped for all content changes. Adding new translations, FAQ's, etc., should always be a minor bump. Changes to the spec that make it more clear, with modifying the versioning semantics should be patch level bumps.
Currently, every change here is published every day by GHA workflow: https://github.com/semver/semver.org/blob/gh-pages/.github/workflows/sync.yml
But it means every change needs to bump up the semver's version (NB: we currently don't though), even a change fixes just a small typo, otherwise, it makes a difference between the tagged version and the published version on the website. And it'd also be confusing to have specifications published under the same version but showing different content from day to day (related: #799).
Maybe it's better to have a working draft version of the website (e.g. draft.semver.org) and do versioning precisely?
(This issue talks about the website, but it's also related to the semver's versioning, so I'm going to open it here.)
/cc #604, #783
The text was updated successfully, but these errors were encountered: