You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by dl...@apache.org on 2015/02/02 09:18:22 UTC
svn commit: r1656402 [1/3] - in /mesos/site: publish/
publish/documentation/configuration/
publish/documentation/latest/configuration/
publish/documentation/latest/mesos-developers-guide/
publish/documentation/latest/powered-by-mesos/ publish/documenta...
Author: dlester
Date: Mon Feb 2 08:18:22 2015
New Revision: 1656402
URL: http://svn.apache.org/r1656402
Log:
Updates website documentation.
Modified:
mesos/site/publish/documentation/configuration/index.html
mesos/site/publish/documentation/latest/configuration/index.html
mesos/site/publish/documentation/latest/mesos-developers-guide/index.html
mesos/site/publish/documentation/latest/powered-by-mesos/index.html
mesos/site/publish/documentation/mesos-developers-guide/index.html
mesos/site/publish/documentation/powered-by-mesos/index.html
mesos/site/publish/sitemap.xml
mesos/site/source/documentation/latest/configuration.md
mesos/site/source/documentation/latest/mesos-developers-guide.md
mesos/site/source/documentation/latest/powered-by-mesos.md
Modified: mesos/site/publish/documentation/configuration/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/configuration/index.html?rev=1656402&r1=1656401&r2=1656402&view=diff
==============================================================================
--- mesos/site/publish/documentation/configuration/index.html (original)
+++ mesos/site/publish/documentation/configuration/index.html Mon Feb 2 08:18:22 2015
@@ -770,15 +770,6 @@ file://path/to/file (where file contains
</tr>
<tr>
<td>
- --cgroups_subsystems=VALUE
- </td>
- <td>
- This flag has been deprecated and is no longer used,
- please update your flags
- </td>
- </tr>
- <tr>
- <td>
--[no-]checkpoint
</td>
<td>
Modified: mesos/site/publish/documentation/latest/configuration/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/configuration/index.html?rev=1656402&r1=1656401&r2=1656402&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/configuration/index.html (original)
+++ mesos/site/publish/documentation/latest/configuration/index.html Mon Feb 2 08:18:22 2015
@@ -770,15 +770,6 @@ file://path/to/file (where file contains
</tr>
<tr>
<td>
- --cgroups_subsystems=VALUE
- </td>
- <td>
- This flag has been deprecated and is no longer used,
- please update your flags
- </td>
- </tr>
- <tr>
- <td>
--[no-]checkpoint
</td>
<td>
Modified: mesos/site/publish/documentation/latest/mesos-developers-guide/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/mesos-developers-guide/index.html?rev=1656402&r1=1656401&r2=1656402&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/mesos-developers-guide/index.html (original)
+++ mesos/site/publish/documentation/latest/mesos-developers-guide/index.html Mon Feb 2 08:18:22 2015
@@ -144,11 +144,15 @@
<li><code>make check</code></li>
</ol>
</li>
-<li><p>Make sure to pull in any changes that have been committed to master branch. Using Git, do this via something like:</p></li>
-<li> <code>git checkout master</code></li>
-<li> <code>git pull</code></li>
-<li> <code>git co my_branch</code></li>
-<li> Check the output of <code>git diff master</code> and make sure it lists only your changes. If other changes you did not make are listed, try a rebase to bring your branch up to date with master.</li>
+<li><p>Make sure to pull in any changes that have been committed to master branch. Using Git, do this via something like:</p>
+
+<ol>
+<li><code>git checkout master</code></li>
+<li><code>git pull</code></li>
+<li><code>git co my_branch</code></li>
+<li>Check the output of <code>git diff master</code> and make sure it lists only your changes. If other changes you did not make are listed, try a rebase to bring your branch up to date with master.</li>
+</ol>
+</li>
</ol>
@@ -161,6 +165,7 @@
<li>Log in or create an account at <a href="http://reviews.apache.org">Apache Review Board</a></li>
<li>The easiest (and recommended) way to submit reviews is through <code>post-reviews.py</code> a wrapper around post-review.</li>
<li>First, install post-review. <a href="http://www.reviewboard.org/docs/manual/dev/users/tools/post-review/">See Instructions</a></li>
+<li>Configure post-review. The easiest method is to symlink to the sample config: ln -s support/reviewboardrc .reviewboardrc</li>
<li>From your local branch run <code>support/post-reviews.py</code>.</li>
<li>Note that <code>post-reviews.py</code> creates a new review for every commit on your branch that is different from the <code>master</code>.</li>
<li>Be sure to add your JIRA issue id (e.g. MESOS-01) to the field labeled “Bugs” (this will automatically link)</li>
@@ -170,6 +175,7 @@
<li><p>Wait for a code review from another Mesos developer via Review Board, address their feedback and upload updated patches until you receive a “Ship It” from a Mesos committer.</p>
<ol>
+<li>When addressing feedback, adjust your existing commit(s) instead of creating new commits, otherwise <code>post-reviews.py</code> will create a new review (<code>git rebase -i</code> is your friend).</li>
<li>Review Board comments should be used for code-specific discussions, and JIRA comments for bigger-picture design discussions.</li>
<li>Always respond to each RB comment that you address directly (i.e. each comment can be responded to directly) with either “Done.” or a comment explaining how you addressed it.</li>
<li>If an issue has been raised in the review, please resolve the issue as “Fixed” or “Dropped”. If “Dropped” please add a comment explaining the reason. Also, if your fix warrants a comment (e.g., fixed differently than suggested by the reviewer) please add a comment.</li>
Modified: mesos/site/publish/documentation/latest/powered-by-mesos/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/latest/powered-by-mesos/index.html?rev=1656402&r1=1656401&r2=1656402&view=diff
==============================================================================
--- mesos/site/publish/documentation/latest/powered-by-mesos/index.html (original)
+++ mesos/site/publish/documentation/latest/powered-by-mesos/index.html Mon Feb 2 08:18:22 2015
@@ -90,6 +90,7 @@
<li><a href="http://www.artirix.com">Artirix</a></li>
<li><a href="http://www.atigeo.com">Atigeo</a></li>
<li><a href="http://www.atlassian.com">Atlassian</a></li>
+<li><a href="http://www.bol.com">Bol.com</a></li>
<li><a href="http://www.brandingbrand.com">Branding Brand</a></li>
<li><a href="http://categorize.co">Categorize</a></li>
<li><a href="http://cloudphysics.com">CloudPhysics</a></li>
@@ -132,10 +133,11 @@
<li><a href="http://www.twitter.com">Twitter</a></li>
<li><a href="http://www.ucsf.edu">UCSF</a></li>
<li><a href="http://www.berkeley.edu">UC Berkeley</a></li>
+<li><a href="http://www.uninett.no">Uninett AS</a></li>
<li><a href="http://www.urx.com">URX</a></li>
<li><a href="http://www.viadeo.com">Viadeo</a></li>
-<li><a href="http://www.vimeo.com">Vimeo</a></li>
<li><a href="http://www.virdata.com">Virdata</a></li>
+<li><a href="http://www.whisk.com">Whisk</a></li>
<li><a href="http://www.wizcorp.jp">Wizcorp</a></li>
<li><a href="http://www.woorank.com">WooRank</a></li>
<li><a href="http://www.yieldbot.com">Yieldbot</a></li>
Modified: mesos/site/publish/documentation/mesos-developers-guide/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/mesos-developers-guide/index.html?rev=1656402&r1=1656401&r2=1656402&view=diff
==============================================================================
--- mesos/site/publish/documentation/mesos-developers-guide/index.html (original)
+++ mesos/site/publish/documentation/mesos-developers-guide/index.html Mon Feb 2 08:18:22 2015
@@ -144,11 +144,15 @@
<li><code>make check</code></li>
</ol>
</li>
-<li><p>Make sure to pull in any changes that have been committed to master branch. Using Git, do this via something like:</p></li>
-<li> <code>git checkout master</code></li>
-<li> <code>git pull</code></li>
-<li> <code>git co my_branch</code></li>
-<li> Check the output of <code>git diff master</code> and make sure it lists only your changes. If other changes you did not make are listed, try a rebase to bring your branch up to date with master.</li>
+<li><p>Make sure to pull in any changes that have been committed to master branch. Using Git, do this via something like:</p>
+
+<ol>
+<li><code>git checkout master</code></li>
+<li><code>git pull</code></li>
+<li><code>git co my_branch</code></li>
+<li>Check the output of <code>git diff master</code> and make sure it lists only your changes. If other changes you did not make are listed, try a rebase to bring your branch up to date with master.</li>
+</ol>
+</li>
</ol>
@@ -161,6 +165,7 @@
<li>Log in or create an account at <a href="http://reviews.apache.org">Apache Review Board</a></li>
<li>The easiest (and recommended) way to submit reviews is through <code>post-reviews.py</code> a wrapper around post-review.</li>
<li>First, install post-review. <a href="http://www.reviewboard.org/docs/manual/dev/users/tools/post-review/">See Instructions</a></li>
+<li>Configure post-review. The easiest method is to symlink to the sample config: ln -s support/reviewboardrc .reviewboardrc</li>
<li>From your local branch run <code>support/post-reviews.py</code>.</li>
<li>Note that <code>post-reviews.py</code> creates a new review for every commit on your branch that is different from the <code>master</code>.</li>
<li>Be sure to add your JIRA issue id (e.g. MESOS-01) to the field labeled “Bugs” (this will automatically link)</li>
@@ -170,6 +175,7 @@
<li><p>Wait for a code review from another Mesos developer via Review Board, address their feedback and upload updated patches until you receive a “Ship It” from a Mesos committer.</p>
<ol>
+<li>When addressing feedback, adjust your existing commit(s) instead of creating new commits, otherwise <code>post-reviews.py</code> will create a new review (<code>git rebase -i</code> is your friend).</li>
<li>Review Board comments should be used for code-specific discussions, and JIRA comments for bigger-picture design discussions.</li>
<li>Always respond to each RB comment that you address directly (i.e. each comment can be responded to directly) with either “Done.” or a comment explaining how you addressed it.</li>
<li>If an issue has been raised in the review, please resolve the issue as “Fixed” or “Dropped”. If “Dropped” please add a comment explaining the reason. Also, if your fix warrants a comment (e.g., fixed differently than suggested by the reviewer) please add a comment.</li>
Modified: mesos/site/publish/documentation/powered-by-mesos/index.html
URL: http://svn.apache.org/viewvc/mesos/site/publish/documentation/powered-by-mesos/index.html?rev=1656402&r1=1656401&r2=1656402&view=diff
==============================================================================
--- mesos/site/publish/documentation/powered-by-mesos/index.html (original)
+++ mesos/site/publish/documentation/powered-by-mesos/index.html Mon Feb 2 08:18:22 2015
@@ -90,6 +90,7 @@
<li><a href="http://www.artirix.com">Artirix</a></li>
<li><a href="http://www.atigeo.com">Atigeo</a></li>
<li><a href="http://www.atlassian.com">Atlassian</a></li>
+<li><a href="http://www.bol.com">Bol.com</a></li>
<li><a href="http://www.brandingbrand.com">Branding Brand</a></li>
<li><a href="http://categorize.co">Categorize</a></li>
<li><a href="http://cloudphysics.com">CloudPhysics</a></li>
@@ -132,10 +133,11 @@
<li><a href="http://www.twitter.com">Twitter</a></li>
<li><a href="http://www.ucsf.edu">UCSF</a></li>
<li><a href="http://www.berkeley.edu">UC Berkeley</a></li>
+<li><a href="http://www.uninett.no">Uninett AS</a></li>
<li><a href="http://www.urx.com">URX</a></li>
<li><a href="http://www.viadeo.com">Viadeo</a></li>
-<li><a href="http://www.vimeo.com">Vimeo</a></li>
<li><a href="http://www.virdata.com">Virdata</a></li>
+<li><a href="http://www.whisk.com">Whisk</a></li>
<li><a href="http://www.wizcorp.jp">Wizcorp</a></li>
<li><a href="http://www.woorank.com">WooRank</a></li>
<li><a href="http://www.yieldbot.com">Yieldbot</a></li>