Skip to content

doc: clarify backport policy, mention 32.x branch - #36

Merged
Sjors merged 2 commits into
2140-dev:masterfrom
Sjors:2026/09/release-policy-32
Sep 18, 2026
Merged

Sjors merged 2 commits into
2140-dev:masterfrom
Sjors:2026/09/release-policy-32

Conversation

@Sjors

@Sjors Sjors commented Sep 18, 2026 •

Copy link
Copy Markdown
Collaborator

This matches the approach Bitcoin Core uses for maintenance branches.

Because IPC is still considered experimental, things are rarely back-ported, but once they are, this process should ensure we match it correctly.

Document how maintenance branches are created and what they may receive:
only backports and branch specific fixes, never a fast-forward to
master. The latter happened to 31.x, which as a result picked up
submitBlock() (not part of Bitcoin Core 31.x) and lost its CI
configuration, see 2140-dev#35.
@Sjors

Sjors commented Sep 18, 2026

Copy link
Copy Markdown
Collaborator Author

@Sjors
Sjors merged commit b32b3ad into 2140-dev:master Sep 18, 2026
1 check passed
@Sjors
Sjors deleted the 2026/09/release-policy-32 branch September 18, 2026 08:48
bit-aloo pushed a commit that referenced this pull request Oct 23, 2026
Document how maintenance branches are created and what they may receive:
only backports and branch specific fixes, never a fast-forward to
master. The latter happened to 31.x, which as a result picked up
submitBlock() (not part of Bitcoin Core 31.x) and lost its CI
configuration, see #35.

Github-Pull: #36
Rebased-From: 94b2b73
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.

2 participants