Skip to content

Document the release process - #268

Merged
mauroservienti merged 3 commits into
masterfrom
document-release-process
Nov 1, 2026
Merged

mauroservienti merged 3 commits into
masterfrom
document-release-process

Conversation

@mauroservienti

@mauroservienti mauroservienti commented Nov 1, 2026 •

Copy link
Copy Markdown
Member

Adds a RELEASING.md, aligned with the Radical one: master builds the next major, and every release is tagged on a release-X.Y branch.

It differs from Radical in three ways:

  • how to patch versions already tagged on master, which is every recent version here, and how to start a new minor;
  • running CI again before tagging, and --latest=false for older majors;
  • the repositories release independently, because neither package depends on the other.

It also links the file from the README.

The guide describes the state after these pull requests:

Describe the branching model, where changes go and how they are backported, how release branches and new majors start, how releases are tagged and published, and how the ServiceComposer repositories relate.
@mauroservienti
mauroservienti force-pushed the document-release-process branch from 7cd6677 to 34f4350 Compare November 1, 2026 16:44
@mauroservienti
mauroservienti merged commit 7e919b7 into master Nov 1, 2026
4 checks passed
@mauroservienti
mauroservienti deleted the document-release-process branch November 1, 2026 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant