This is an automated email from the ASF dual-hosted git repository.
dgrove pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openwhisk-release.git
The following commit(s) were added to refs/heads/master by this push:
new 3eac048 add note that core repo releases need to come from a release
branch (#313)
3eac048 is described below
commit 3eac048a4072074b99b9224c81c99985a526821d
Author: David Grove <[email protected]>
AuthorDate: Wed Jan 15 14:39:09 2020 -0500
add note that core repo releases need to come from a release branch (#313)
---
docs/release_instructions.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/docs/release_instructions.md b/docs/release_instructions.md
index 35cb28f..427e4d3 100644
--- a/docs/release_instructions.md
+++ b/docs/release_instructions.md
@@ -71,6 +71,7 @@ Before creating release artifacts, the Release Manager should
initiate a communi
1. Start a [DISCUSS] thread on the dev list proposing the release. Allow at
least 24 hours for feedback.
2. Make sure all unit and integration tests are passing in the repositories
that are being released. Check the [project status
list](../README.md#project-status).
3. If a component being released includes a changelog or release notes file,
make sure they are up-to-date.
+ 4. If you are releasing either the `openwhisk` or `openwhisk-deploy-kube`
repositories create a release branch in the Apache git repo. Then submit a PR
to that release branch to change all uses of the `nightly` tag to fixed tags
(eg `1.14.0` or `8eb922f`).
### Defining the Release Contents
@@ -111,7 +112,7 @@ provide historical documentation of project releases.
- name: User level name of the component
- hash: git commit hash being released
- repository: URL of the repository
- - branch: git branch being released
+ - branch: git branch being released (`master` or a release branch name)
### Create Release Candidates
