assignUser commented on code in PR #13308:
URL: https://github.com/apache/arrow/pull/13308#discussion_r888862981
##########
docs/source/developers/release.rst:
##########
@@ -87,12 +87,49 @@ These are the different steps that are required to create a
release candidate.
# Curate the release
# The end of the generated report shows the jira tickets with wrong
version number assigned.
archery release curate <version>
-
+
+
+Creating a Release Candidate
+============================
+
+These are the different steps that are required to create a release candidate.
+
+The initial Release Candidate branch is merged from master. Follow up Release
+Candidates will be created from a maintenance branch.
+
+We have implemented a Feature Freeze policy between Release Candidates.
+This means that, in general, we will only add fixes between Release Candidates.
+Only specific features, if there is community consensus, will be merged to
further Release Candidates.
Review Comment:
I think this needs rephrasing to make clear that this will only happen in
special circumstances so as not to leave an "opening" for noncritical feature
additions. Maybe:
```suggestion
In rare cases, critical features can be added between release candidates, if
there is community consensus.
```
##########
docs/source/developers/release.rst:
##########
@@ -87,12 +87,49 @@ These are the different steps that are required to create a
release candidate.
# Curate the release
# The end of the generated report shows the jira tickets with wrong
version number assigned.
archery release curate <version>
-
+
+
+Creating a Release Candidate
+============================
+
+These are the different steps that are required to create a release candidate.
+
+The initial Release Candidate branch is merged from master. Follow up Release
Review Comment:
```suggestion
The initial Release Candidate branch is created from master. Follow up
Release
```
##########
docs/source/developers/release.rst:
##########
@@ -87,12 +87,49 @@ These are the different steps that are required to create a
release candidate.
# Curate the release
# The end of the generated report shows the jira tickets with wrong
version number assigned.
archery release curate <version>
-
+
+
+Creating a Release Candidate
+============================
+
+These are the different steps that are required to create a release candidate.
+
+The initial Release Candidate branch is merged from master. Follow up Release
+Candidates will be created from a maintenance branch.
+
+We have implemented a Feature Freeze policy between Release Candidates.
+This means that, in general, we will only add fixes between Release Candidates.
+Only specific features, if there is community consensus, will be merged to
further Release Candidates.
+
+Create or update the corresponding maintenance branches:
+
+.. tab-set::
+
+ .. tab-item:: Initial Release Candidate
+
+ .. code-block::
+
+ # From an up to date master branch execute
+ archery release --jira-cache /tmp/jiracache cherry-pick X.Y.Z
--execute
+
+ .. tab-item:: Follow up Release Candidates
+
+ .. code-block::
+
+ # First run on dry-mode to see what are the commits that will be
cherry-pick.
+ # If there are commits that we don't want to get applied ensure
the version on
+ # JIRA is set to the following release.
+ archery release --jira-cache /tmp/jiracache cherry-pick X.Y.Z
--continue
+ # Update the maintenance branch with the previous commits
+ archery release --jira-cache /tmp/jiracache cherry-pick X.Y.Z
--continue --execute
+
+Create the rest of the Release branches.
+
+.. code-block::
+
# Checkout release branch
# Use master for major releases
- git checkout -b release-4.0.0 master
Review Comment:
I don't quite understand this change?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
