Versioning and organization of this project #634

Open
opened 2026-02-17 12:15:48 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @yochem on GitHub (Jul 17, 2024).

Issues with different versions / releases

It seems that there are quite some questions about the versioning, releases, and release notes of the different versions of the spec:

I think this can be restructured, to have clear releases of new versions, that are automatically reflected on the website.

Versioning Proposal

Organization Proposal

If the spec -> website sync workflow will be revised, I would also suggest to split the content of both repo's more clearly:

  • semver.org: Only contain website files, used to convert the markdown spec's to a website (e.g. css, js, jekyll files, etc.).
  • semver: Contain all specification content. This means including the translations, as this should also be part of the spec.

It is of course also possible to combine both repo's. The advantage would be that no cross-repo action is needed. The disadvantage would be that the 'main' repo would get more convoluted.

Let me know what you think! I'm just gonna ping @alexandrtovmach here, as they had big plans for reviving the project in #573. Hope that's okay 😇.

Originally created by @yochem on GitHub (Jul 17, 2024). ## Issues with different versions / releases It seems that there are quite some questions about the versioning, releases, and release notes of the different versions of the spec: - Versions should have a date: - #1026 - Versions should have release notes: - #993 - Versions should follow semver: - #976 - #799 - The spec versions in [semver/semver.org/spec](https://github.com/semver/semver.org/tree/gh-pages/spec) are a different list then the tags in this repo - #783 - #868 I think this can be restructured, to have clear releases of new versions, that are automatically reflected on the website. ## Versioning Proposal - More extensively tag the different versions in this repository with semantic versions - Automatically sync those tags to the website - Can be easily done with a small script ([gist](https://gist.github.com/yochem/fa8a955f11da7d4983795f36f538d9cd)) - Website: link index page to latest version - https://github.com/semver/semver.org/issues/175 - https://github.com/semver/semver.org/pull/448 ## Organization Proposal If the spec -> website sync workflow will be revised, I would also suggest to split the content of both repo's more clearly: - `semver.org`: **Only** contain _website_ files, used to convert the markdown spec's to a website (e.g. css, js, jekyll files, etc.). - `semver`: Contain **all** specification content. This means _including_ the translations, as this should also be part of the spec. It is of course also possible to _combine_ both repo's. The advantage would be that no cross-repo action is needed. The disadvantage would be that the 'main' repo would get more convoluted. Let me know what you think! I'm just gonna ping @alexandrtovmach here, as they had big plans for reviving the project in #573. Hope that's okay 😇.
Author
Owner

@Neustradamus commented on GitHub (Jun 3, 2025):

Any progress?

@Neustradamus commented on GitHub (Jun 3, 2025): Any progress?
Author
Owner

@yochem commented on GitHub (Jun 3, 2025):

I haven't heard a thing since I opened this issue.

@yochem commented on GitHub (Jun 3, 2025): I haven't heard a thing since I opened this issue.
Author
Owner

@steveklabnik commented on GitHub (Jun 4, 2025):

I intend to do better here but have no timeline for shipping a fix.

@steveklabnik commented on GitHub (Jun 4, 2025): I intend to do better here but have no timeline for shipping a fix.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#634