-
Notifications
You must be signed in to change notification settings - Fork 108
GH-629: Add post-release tasks to dev/release/README.md #630
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -172,6 +172,74 @@ $ GH_TOKEN=${YOUR_GITHUB_TOKEN} dev/release/bump_version.sh 19.0.0-SNAPSHOT | |
| It creates a feature branch and adds a commit that bumps version. This | ||
| opens a pull request from the feature branch by `gh pr create`. | ||
|
|
||
| ### Close the GitHub milestone | ||
|
|
||
| Close the milestone here, then open a new milestone for the next release: | ||
|
|
||
| https://github.com/apache/arrow-java/milestones | ||
|
|
||
| The milestone should be named after the version (e.g. "18.4.0"). | ||
|
|
||
| ### Publish the release blog post | ||
|
|
||
| Open a pull request on | ||
| [apache/arrow-site](https://github.com/apache/arrow-site) announcing the new | ||
| release and summarizing the changes. Do not include the full changelog, just | ||
| important entries (breaking changes, new features, major bug fixes) and a link | ||
| to the full changelog. See an [example | ||
| PR](https://github.com/apache/arrow-site/pull/594). | ||
|
|
||
| ### Announce the new release on the mailing list | ||
|
|
||
| Send an email to "[email protected]" from your Apache email, CC'ing | ||
| [email protected]/[email protected]. See an [example | ||
| post](https://lists.apache.org/thread/bxpt0r8kw0ltgywnylqdroskkt6966z4). | ||
|
|
||
| ``` | ||
| To: [email protected] | ||
| CC: [email protected], [email protected] | ||
| Subject: [ANNOUNCE] Apache Arrow Java 18.2.0 released | ||
|
|
||
| The Apache Arrow community is pleased to announce the Arrow Java 18.2.0 release. | ||
|
|
||
| The release is available now from our website: | ||
| https://arrow.apache.org/install/ | ||
| and | ||
| https://www.apache.org/dyn/closer.cgi/arrow/apache-arrow-java-18.2.0/ | ||
|
|
||
| Read about what's new in the release at: | ||
| https://arrow.apache.org/blog/2025/02/19/arrow-java-18.2.0/ | ||
|
|
||
| Read the full changelog: | ||
| https://github.com/apache/arrow-java/commits/v18.2.0 | ||
|
|
||
| What is Apache Arrow? | ||
| ------------------------------- | ||
|
|
||
| Apache Arrow is a universal columnar format and multi-language toolbox | ||
| for fast data interchange and in-memory analytics. It houses a set of | ||
| canonical in-memory representations of flat and hierarchical data | ||
| along with multiple language-bindings for structure manipulation. It | ||
| also provides low-overhead streaming and batch messaging, zero-copy | ||
| interprocess communication (IPC), and vectorized in-memory analytics | ||
| libraries. | ||
|
|
||
| Please report any feedback to the mailing lists: | ||
| https://lists.apache.org/[email protected] | ||
|
|
||
| Regards, | ||
| The Apache Arrow community. | ||
| ``` | ||
|
|
||
| ### Announce the new release on social media | ||
|
|
||
| Make a post on our [BlueSky](https://bsky.app/profile/arrow.apache.org) and | ||
| [LinkedIn](https://www.linkedin.com/company/apache-arrow/) accounts. (Ask | ||
| your fellow PMC members for access if need be, or ask a PMC member to make the | ||
| post on your behalf.) The post should link to the blog post. See [example | ||
| BlueSky post](https://bsky.app/profile/arrow.apache.org/post/3lioi6ov5h22d) | ||
| and [example LinkedIn post](https://www.linkedin.com/posts/apache-arrow_apache-arrow-java-1820-release-activity-7298633716522758144-L71x). | ||
|
|
||
| ## Verify | ||
|
|
||
| We have a script to verify a RC. | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
What is the general rule for setting the target date of the next milestone?
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.
I don't think we really use target date. Maybe we can discuss a target release cadence? For instance, for ADBC I've been trying to hit ~6-8 weeks (it tends to slip though because I have limited time)
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.
I'm favor of predictable release pace but flexible.
For the community, it's great to know in advance when a release is planned. However, we should clearly state that what is in the release could change (depending of resources, priority, etc).
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.
I'm happy to volunteer for arrow-Java release every 6-8 weeks.
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.
Maybe we can trade off to reduce the burden/improve bus factor, but that sounds good to me.
Do you want to start a small discussion on the ML? Or if we're in agreement here then let's just go with it.
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.
Sure. I think it makes sense to discuss on the ml. Let me start a thread. Thanks !
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.
Releasing arrow-java every 6-8 weeks sounds a little bit frequent to me. Perhaps we can start with a three-month release cadence same to the mono repo in the past.
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.
Yes, let's start with quarter releases. We can always do intermediate release if needed.