Skip to content

chore: Update release runbook#2674

Open
dannycjones wants to merge 2 commits into
apache:mainfrom
dannycjones:update-release-runbook
Open

chore: Update release runbook#2674
dannycjones wants to merge 2 commits into
apache:mainfrom
dannycjones:update-release-runbook

Conversation

@dannycjones

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

There is no open issue for this PR.

What changes are included in this PR?

This change updates the release process to try and simplify some steps,
and clarify what can be owned by non-committers.

I've purposely left the updates of dependency files out of the updates as I wish to tackle that in a separate PR.

Are these changes tested?

I have tested the instructions using a GitHub repository I own however I cannot test properly with Iceberg Rust.

I am coordinating with @CTTY for this release and we will review the release process and test it.

I have tested building the site to check there's no rendering issues.

@dannycjones

Copy link
Copy Markdown
Contributor Author

I'll probably rebase on #2676 once merged.

Comment thread website/src/release.md Outdated
Comment thread website/src/release.md

- [ ] Bump version in project
- [ ] Update docs
- [ ] Draft GitHub release

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Could you help me understand what is this?

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 was already in the instructions to generate the release notes but not properly documented. When creating it, you tell it the final tag name that it'll create and press generate to provide a set of release notes. These would be copied into CHANGELOG.md.

That being said, it sounds like not everyone had been using this for generating release notes. I'm happy to make it otherwise clearer and focus on the GitHub release only at the end if that makes sense (i.e. skip the draft).

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