This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 5c6e7eb Publishing website 2020/02/04 21:12:59 at commit 8f177b5
5c6e7eb is described below
commit 5c6e7eb2fb7f9f699c767d8f58378087730001ac
Author: jenkins <bui...@apache.org>
AuthorDate: Tue Feb 4 21:12:59 2020 +0000
Publishing website 2020/02/04 21:12:59 at commit 8f177b5
---
website/generated-content/contribute/committer-guide/index.html | 2 ++
website/generated-content/contribute/release-guide/index.html | 7 ++++++-
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/website/generated-content/contribute/committer-guide/index.html
b/website/generated-content/contribute/committer-guide/index.html
index d5e6e8f..85ba76c 100644
--- a/website/generated-content/contribute/committer-guide/index.html
+++ b/website/generated-content/contribute/committer-guide/index.html
@@ -344,6 +344,8 @@ rollback; it is easy to roll back many commits, or a whole
pull request, but
harder to roll back part of a commit.</li>
<li>Commit messages should tag JIRAs and be otherwise descriptive.
It should later not be necessary to find a merge or first PR commit to find
out what caused a change.</li>
+ <li><code class="highlighter-rouge">CHANGES.md</code> file should be updated
with noteworthy changes (e.g. new features, backward
+incompatible changes, dependency changes, etc.).</li>
<li>Squash the “Fixup!”, “Address comments” type of commits that resulted
from review iterations.</li>
</ul>
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index 37e2d65..977700a 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -1371,6 +1371,11 @@ to point to the new release. See file history for
examples.</li>
<p>Write a blog post similar to
https://beam.apache.org/blog/2019/08/22/beam-2.15.0.html</p>
+<ul>
+ <li>Update <code class="highlighter-rouge">CHANGES.md</code> by adding a new
section for the next release.</li>
+ <li>Copy the changes for the current release from <code
class="highlighter-rouge">CHANGES.md</code> to the blog post and edit as
necessary.</li>
+</ul>
+
<p><strong>Tip</strong>: Use git log to find contributors to the releases.
(e.g: <code class="highlighter-rouge">git log --pretty='%aN' ^v2.10.0 v2.11.0 |
sort | uniq</code>).
Make sure to clean it up, as there may be duplicate or incorrect user
names.</p>
@@ -1402,7 +1407,7 @@ all major features and bug fixes, and all known
issues.</p>
### Breaking Changes
* X behavior was changed
([BEAM-X](https://issues.apache.org/jira/browse/BEAM-X)).
- * Y behavior was changed
([BEAM-Y](https://issues.apache.org/jira/browse/BEAM-X)).
+ * Y behavior was changed
([BEAM-Y](https://issues.apache.org/jira/browse/BEAM-Y)).
### Deprecations
