summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.rst
diff options
context:
space:
mode:
authorFrancesca Krihely <francesca@10gen.com>2013-11-27 15:14:35 -0500
committerMatt Kangas <matt.kangas@mongodb.com>2013-12-15 21:36:50 -0500
commit1e5bf026379f767171d5ebb8344217f534bdffc9 (patch)
treedadab6795129b619077caa704a5d887032f4a7a9 /CONTRIBUTING.rst
parent7c72e8b52934f2daedeee4f289c75246dc665487 (diff)
downloadmongo-1e5bf026379f767171d5ebb8344217f534bdffc9.tar.gz
Some suggestions for the Contributors page
Signed-off-by: Matt Kangas <matt.kangas@mongodb.com>
Diffstat (limited to 'CONTRIBUTING.rst')
-rw-r--r--CONTRIBUTING.rst18
1 files changed, 17 insertions, 1 deletions
diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
index b8bfdcae8f6..4772e9a94d0 100644
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -39,6 +39,22 @@ your solution will take.
.. _SERVER project: https://jira.mongodb.org/browse/SERVER
+The Life Cycle of a Pull Request
+--------------------------------
+
+When you submit a pull request, here is what happens:
+
+- The MongoDB engineering team will review your pull request to make sure you have included a
+ SERVER ticket in your request and signed the contributor agreement.
+- You should receive a response from one of our engineers with additional questions about your
+ contributions.
+- If your pull request matches a ticket and is aligned with the Server Roadmap, it will get
+ triaged and reviewed by the Kernel team.
+- Pull requests that have been reviewed and approved will be signed off and merged into a
+ development branch and the associated JIRA SERVER issue will be resolved with an expected
+ fixVersion.
+
+
Style Guide
-----------
@@ -74,4 +90,4 @@ Contributor Agreement
A patch will only be considered for merging into the upstream codebase after you have signed the
`contributor agreement`_.
-.. _contributor agreement: http://www.mongodb.com/contributor \ No newline at end of file
+.. _contributor agreement: http://www.mongodb.com/contributor