GH-629: Add post-release tasks to dev/release/README.md#630
GH-629: Add post-release tasks to dev/release/README.md#630lidavidm merged 1 commit intoapache:mainfrom
Conversation
This comment has been minimized.
This comment has been minimized.
|
|
||
| ### Close the GitHub milestone | ||
|
|
||
| Close the milestone here, then open a new milestone for the next release: |
There was a problem hiding this comment.
What is the general rule for setting the target date of the next milestone?
There was a problem hiding this comment.
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.
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.
I'm happy to volunteer for arrow-Java release every 6-8 weeks.
There was a problem hiding this comment.
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.
Sure. I think it makes sense to discuss on the ml. Let me start a thread. Thanks !
There was a problem hiding this comment.
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.
Yes, let's start with quarter releases. We can always do intermediate release if needed.
4 participants
What's Changed
Add instructions for undocumented post-release tasks.
Closes #629.