FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

GH-629: Add post-release tasks to dev/release/README.md by lidavidm · Pull Request #630 · apache/arrow-java · GitHub

GH-629: Add post-release tasks to dev/release/README.md - #630

Merged
lidavidm merged 1 commit into
apache:mainfrom
lidavidm:gh-629
Feb 25, 2025
Merged

GH-629: Add post-release tasks to dev/release/README.md#630
lidavidm merged 1 commit into
apache:mainfrom
lidavidm:gh-629

Conversation

Copy link
Copy Markdown
Member

What's Changed

Add instructions for undocumented post-release tasks.

Closes #629.

This comment has been minimized.

lidavidm requested a review from jbonofre February 24, 2025 04:59
lidavidm added the documentation PRs that improve documentation. label Feb 24, 2025
lidavidm marked this pull request as ready for review February 24, 2025 05:00
Comment thread dev/release/README.md

### Close the GitHub milestone

Close the milestone here, then open a new milestone for the next release:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

What is the general rule for setting the target date of the next milestone?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

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)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

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).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

I'm happy to volunteer for arrow-Java release every 6-8 weeks.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Sure. I think it makes sense to discuss on the ml. Let me start a thread. Thanks !

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Yes, let's start with quarter releases. We can always do intermediate release if needed.

kou left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

+1

Thanks!

lidavidm merged commit f8660a8 into apache:main Feb 25, 2025
lidavidm added this to the 18.3.0 milestone Feb 25, 2025
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation PRs that improve documentation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Release] Add missing post release tasks to dev/release/README.md

4 participants


Back | FazBrowse Home | New Git URL