-
Notifications
You must be signed in to change notification settings - Fork 331
docs: update "how to release" #1691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
cc @CTTY could you also take a look and see if this makes sense? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @kevinjqliu for updating this! Just some minor comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @kevinjqliu for this pr! It would be more convenient if we could have a release script as cpp does.
yea good idea, both cpp and go has the |
Which issue does this PR close?
What changes are included in this PR?
Based on notes from #1631 and past experience running the release process
A few things to know
v${release_version}
format as the tagapache-iceberg-rust-${release_version}/
format for ASF svn (for dev and release )Formatted the "How to verify a release" section:
Are these changes tested?