Repository: mesos Updated Branches: refs/heads/master b78749d29 -> b979d03c5
Fixed a few small issues in the developer's guide. Review: https://reviews.apache.org/r/18891 Project: http://git-wip-us.apache.org/repos/asf/mesos/repo Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/b979d03c Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/b979d03c Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/b979d03c Branch: refs/heads/master Commit: b979d03c5b2a4a1217e14b7818ab256a1edae01f Parents: b78749d Author: Chengwei Yang <[email protected]> Authored: Thu Mar 6 21:52:39 2014 -0800 Committer: Jie Yu <[email protected]> Committed: Thu Mar 6 21:52:39 2014 -0800 ---------------------------------------------------------------------- docs/mesos-developers-guide.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/mesos/blob/b979d03c/docs/mesos-developers-guide.md ---------------------------------------------------------------------- diff --git a/docs/mesos-developers-guide.md b/docs/mesos-developers-guide.md index 60a6ac1..d195bde 100644 --- a/docs/mesos-developers-guide.md +++ b/docs/mesos-developers-guide.md @@ -16,11 +16,11 @@ layout: documentation * A code review request should be created for every JIRA that involves a change to the codebase. ### Before you submit -1. Check out the code from the Apache repository via Git or SVN. Instructions are on the [Getting Started](http://mesos.apache.org/gettingstarted/) page. +1. Check out the code from the Apache repository via Git. Instructions are on the [Getting Started](http://mesos.apache.org/gettingstarted/) page. 1. Join the [email protected] mailing list by sending an email to [email protected] -1. Find a JIRA that is currently unassigned that you want to work on at http://issues.apache.org/jira/browse/MESOS, or create your own (you'll need a JIRA account for this, see below)! +1. Find a JIRA that is currently unassigned that you want to work on at [JIRA issue tracker](https://issues.apache.org/jira/browse/MESOS), or create your own (you'll need a JIRA account for this, see below)! 2. This could be a JIRA representing a bug (possibly a bug that you encountered and reported, e.g. when trying to build) or a new feature 1. Assign the JIRA to yourself. To do this, you will need: @@ -51,7 +51,7 @@ layout: documentation ### Submit your patch 1. You're ready to submit your patch for review! - 2. Log in or create an account at ]Apache Review Board](http://reviews.apache.org) + 2. Log in or create an account at [Apache Review Board](http://reviews.apache.org) 2. The easiest (and recommended) way to submit reviews is through `post-reviews.py` a wrapper around post-review. 2. First, install post-review. [See Instructions](http://www.reviewboard.org/docs/manual/dev/users/tools/post-review/) 2. From your local branch run `support/post-reviews.py`. @@ -69,4 +69,4 @@ layout: documentation 1. The last step is to ensure that the necessary documentation gets created or updated so the whole world knows about your new feature or bug fix. ## Style Guides -* For patches to the core, we ask that you follow the [Mesos C++ Style Guide](mesos-c++-style-guide.md) \ No newline at end of file +* For patches to the core, we ask that you follow the [Mesos C++ Style Guide](mesos-c++-style-guide.md)
