This is an automated email from the ASF dual-hosted git repository.
fjy pushed a commit to branch 0.16.0-incubating
in repository https://gitbox.apache.org/repos/asf/incubator-druid.git
The following commit(s) were added to refs/heads/0.16.0-incubating by this push:
new 29e6b4f add missing step in release process (#8422) (#8424)
29e6b4f is described below
commit 29e6b4f2bd7da7f3afe4d76d4442bd1aff091fe9
Author: Clint Wylie <[email protected]>
AuthorDate: Wed Aug 28 12:44:38 2019 -0700
add missing step in release process (#8422) (#8424)
---
distribution/asf-release-process-guide.md | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/distribution/asf-release-process-guide.md
b/distribution/asf-release-process-guide.md
index ecad0f5..7c161d1 100644
--- a/distribution/asf-release-process-guide.md
+++ b/distribution/asf-release-process-guide.md
@@ -39,6 +39,14 @@ $ git checkout origin/master
$ git checkout -b 0.16.0-incubating
```
+Then push the branch to `origin`. If doing a quarterly release, it will also
be necessary to bump the version in master to the next release snapshot:
+
+```
+$ mvn versions:set -DnewVersion=0.17.0-incubating-SNAPSHOT
+```
+
+and open a PR to the master branch. Bug fix releases should already have the
correct snapshot version from the previous releases on the branch, so this step
is not necessary.
+
The only additions to the release branch after this branch should be bug
fixes, which should be back-ported from the master branch, via a second PR, not
with a direct PR to the release branch. Bug fix release branches may be
initially populated via cherry-picking, but it is recommended to leave at least
1 commit to do as a backport PR in order to run through CI. (Note that CI is
sometimes flaky for older branches).
Once all issues and PRs that are still tagged with the release milestone have
been merged, closed, or removed from the milestone, the next step is to put
together a release candidate.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
