This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a change to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git.
discard 0c94192 This closes #506
discard a790241 Add instructions for local Flink cluster.
discard bd6b564 Add Flink instructions to portability contrib page.
new b704e5a Add a page for release cadence
new 0dfae18 updated the language
new 9e6da40 fix the space
new ebe224b This closes #502
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (0c94192)
\
N -- N -- N refs/heads/mergebot (ebe224b)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
src/_includes/section-menu/community.html | 1 +
.../javadoc/index.md => community/policies.md} | 16 ++++++++----
src/contribute/portability.md | 29 ++++------------------
3 files changed, 17 insertions(+), 29 deletions(-)
copy src/{documentation/sdks/javadoc/index.md => community/policies.md} (52%)
