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/mesos-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new ec1b5b8 Updated the website built from mesos SHA: af6922288.
ec1b5b8 is described below
commit ec1b5b863db09a95089e192e9dcc5d9b4a088df4
Author: jenkins <bui...@apache.org>
AuthorDate: Mon Aug 30 18:19:03 2021 +0000
Updated the website built from mesos SHA: af6922288.
---
content/documentation/beginner-contribution/index.html | 4 ++--
content/documentation/committing/index.html | 4 +++-
content/documentation/latest/beginner-contribution/index.html | 4 ++--
content/documentation/latest/committing/index.html | 4 +++-
4 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/content/documentation/beginner-contribution/index.html
b/content/documentation/beginner-contribution/index.html
index 0aa2f79..7404f0f 100644
--- a/content/documentation/beginner-contribution/index.html
+++ b/content/documentation/beginner-contribution/index.html
@@ -147,9 +147,9 @@
<p>If you are changing any code in Mesos, then you should build and run the
tests before opening a PR. You should run <code>make check</code> and ensure
that all tests pass before opening a PR.</p>
-<h2>Open a PR</h2>
+<h2>Open a Pull Request</h2>
-<p>Once changes are completed and tested, it’s time to open a PR so that
they can be reviewed. When your local branch is clean and ready to submit, push
it to your Mesos fork. You can then open a PR against the Apache Mesos GitHub
repository. Once your PR is open, you can notify the community on <a
href="/community">Mesos Slack</a> or on the developer mailing list.</p>
+<p>Once changes are completed and tested, it’s time to open a Pull
Request (PR) so that they can be reviewed. When your local branch is clean and
ready to submit, push it to your Mesos fork. You can then open a PR against the
Apache Mesos GitHub repository. Once your PR is open, you can notify the
community on <a href="/community">Mesos Slack</a> or on the developer mailing
list.</p>
<h1>Getting Started Guidance</h1>
diff --git a/content/documentation/committing/index.html
b/content/documentation/committing/index.html
index 726fe23..e8c4553 100644
--- a/content/documentation/committing/index.html
+++ b/content/documentation/committing/index.html
@@ -134,7 +134,9 @@ people to write poorly.</li>
this for you, but be careful when rebasing or ammending.</li>
<li><strong>Never ever commit a merge</strong>: always rebase instead, as
appropriate.
Likewise, never ‘force push’.</li>
-<li><strong>Don’t break the build</strong>: we support Linux, Mac OS X,
and Windows. However,
+<li><strong>Don’t break the build</strong>: we support <a
href="https://ci-builds.apache.org/job/Mesos/job/Mesos-Buildbot/";>Linux
x86_64</a>,
+<a href="https://ci-builds.apache.org/job/Mesos/job/Mesos-Buildbot-ARM/";>Linux
aarch64</a>,
+Mac OS X and <a
href="https://ci-builds.apache.org/job/Mesos/job/Mesos-Buildbot-Windows/";>Windows</a>.
However,
not all configurations are being tested in Jenkins, so be aware of that.
Also, pay attention to the Jenkins review bot if it flags a review as
breaking the build. Note that if you do break the build, the fixes are
diff --git a/content/documentation/latest/beginner-contribution/index.html
b/content/documentation/latest/beginner-contribution/index.html
index dfeddf5..6d432e9 100644
--- a/content/documentation/latest/beginner-contribution/index.html
+++ b/content/documentation/latest/beginner-contribution/index.html
@@ -147,9 +147,9 @@
<p>If you are changing any code in Mesos, then you should build and run the
tests before opening a PR. You should run <code>make check</code> and ensure
that all tests pass before opening a PR.</p>
-<h2>Open a PR</h2>
+<h2>Open a Pull Request</h2>
-<p>Once changes are completed and tested, it’s time to open a PR so that
they can be reviewed. When your local branch is clean and ready to submit, push
it to your Mesos fork. You can then open a PR against the Apache Mesos GitHub
repository. Once your PR is open, you can notify the community on <a
href="/community">Mesos Slack</a> or on the developer mailing list.</p>
+<p>Once changes are completed and tested, it’s time to open a Pull
Request (PR) so that they can be reviewed. When your local branch is clean and
ready to submit, push it to your Mesos fork. You can then open a PR against the
Apache Mesos GitHub repository. Once your PR is open, you can notify the
community on <a href="/community">Mesos Slack</a> or on the developer mailing
list.</p>
<h1>Getting Started Guidance</h1>
diff --git a/content/documentation/latest/committing/index.html
b/content/documentation/latest/committing/index.html
index 685fbbb..f6200f4 100644
--- a/content/documentation/latest/committing/index.html
+++ b/content/documentation/latest/committing/index.html
@@ -134,7 +134,9 @@ people to write poorly.</li>
this for you, but be careful when rebasing or ammending.</li>
<li><strong>Never ever commit a merge</strong>: always rebase instead, as
appropriate.
Likewise, never ‘force push’.</li>
-<li><strong>Don’t break the build</strong>: we support Linux, Mac OS X,
and Windows. However,
+<li><strong>Don’t break the build</strong>: we support <a
href="https://ci-builds.apache.org/job/Mesos/job/Mesos-Buildbot/";>Linux
x86_64</a>,
+<a href="https://ci-builds.apache.org/job/Mesos/job/Mesos-Buildbot-ARM/";>Linux
aarch64</a>,
+Mac OS X and <a
href="https://ci-builds.apache.org/job/Mesos/job/Mesos-Buildbot-Windows/";>Windows</a>.
However,
not all configurations are being tested in Jenkins, so be aware of that.
Also, pay attention to the Jenkins review bot if it flags a review as
breaking the build. Note that if you do break the build, the fixes are
