Skip to content

docs: Add instruction to merge release branch back to main in release guide - #3085

Draft
dannycjones wants to merge 1 commit into
apache:mainfrom
dannycjones:update-release-guide-merge-back-into-main
Draft

docs: Add instruction to merge release branch back to main in release guide#3085
dannycjones wants to merge 1 commit into
apache:mainfrom
dannycjones:update-release-guide-merge-back-into-main

Conversation

@dannycjones

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

Addresses action item in #2864.

What changes are included in this PR?

Add note to release guide to instruct release manager to merge release branch back into main following each release.

Are these changes tested?

N/A

AI Disclosure

No AI was used in this change.

Comment thread website/src/release.md
Comment on lines +610 to +616
Create a pull request that pulls back the changes from the release branch.
To prepare the pull request,
create a merge commit from the release branch into main,
run `make generate-public-api` and `./dev/release/dependencies.sh generate`,
and open the pull request with both changes.

Once merged into `main`, `main` is then ready for future release branches being cut from it.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This documents what I've done for 0.10.1, however I think this falls apart if we're doing a patch release for an older minor version.

Ultimately, I'm wondering if we need a set of rules to say: if a change needs making to a release branch, it must first be made on main (where applicable) and a second PR must cherry-pick (or effectively cherry-pick) that change on to the release branch. Presumably we would need to do that for changelog? OR maybe changelog is one where we reverse backport it...

Open to thoughts here.

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