beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bhule...@apache.org
Subject [beam] branch TheNeuralBit-patch-3 updated: Update release-guide.md
Date Wed, 23 Dec 2020 17:42:27 GMT
This is an automated email from the ASF dual-hosted git repository.

bhulette pushed a commit to branch TheNeuralBit-patch-3
in repository https://gitbox.apache.org/repos/asf/beam.git


The following commit(s) were added to refs/heads/TheNeuralBit-patch-3 by this push:
     new 6412426  Update release-guide.md
6412426 is described below

commit 64124267865c0dbd936ec1f56f4c8f067ed8df86
Author: Brian Hulette <bhulette@google.com>
AuthorDate: Wed Dec 23 09:41:59 2020 -0800

    Update release-guide.md
---
 website/www/site/content/en/contribute/release-guide.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/website/www/site/content/en/contribute/release-guide.md b/website/www/site/content/en/contribute/release-guide.md
index 9bde498..30688a0 100644
--- a/website/www/site/content/en/contribute/release-guide.md
+++ b/website/www/site/content/en/contribute/release-guide.md
@@ -237,6 +237,8 @@ Release candidates are built from a release branch. As a final step in
preparati
 
 There are 2 ways to cut a release branch: either running automation script(recommended),
or running all commands manually.
 
+After following one of these processes you should manually update `CHANGES.md` on `master`
by adding a new section for the next release.
+
 #### Use cut_release_branch.sh to cut a release branch
 * Script: [cut_release_branch.sh](https://github.com/apache/beam/blob/master/release/src/main/scripts/cut_release_branch.sh)
 
@@ -653,7 +655,6 @@ This pull request is against the `apache/beam` repo, on the `master` branch
([ex
 ### Blog post
 
 Write a blog post similar to [beam-2.23.0.md](https://github.com/apache/beam/commit/b976e7be0744a32e99c841ad790c54920c8737f5#diff-8b1c3fd0d4a6765c16dfd18509182f9d).

-- Update `CHANGES.md` by adding a new section for the next release.
 - Copy the changes for the current release from `CHANGES.md` to the blog post and edit as
necessary.
 - Be sure to add yourself to [authors.yml](https://github.com/apache/beam/blob/master/website/www/site/data/authors.yml)
if necessary.
 


Mime
View raw message