aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFredrik Gustafsson <[email protected]>2013-06-26 15:27:42 +0200
committerFredrik Gustafsson <[email protected]>2013-06-26 15:27:42 +0200
commitf4394d1b8a170010887597c013be556284e86766 (patch)
tree6f7056dab4e3394946bc2b26cbd55459a06c1ef4
parent4c3b306184d886678d08949bcbe0186af8f984b1 (diff)
downloadotp-f4394d1b8a170010887597c013be556284e86766.tar.gz
otp-f4394d1b8a170010887597c013be556284e86766.tar.bz2
otp-f4394d1b8a170010887597c013be556284e86766.zip
readme: changed information about pull requests
-rw-r--r--README.md11
1 files changed, 7 insertions, 4 deletions
diff --git a/README.md b/README.md
index 1bcf14e760..a6a4f11be8 100644
--- a/README.md
+++ b/README.md
@@ -28,10 +28,13 @@ Here are the [instructions for submitting patches] [2].
In short:
* We prefer to receive proposed updates via email on the
- [`erlang-patches`] [3] mailing list rather than through a pull request.
- Pull requests are not practical because we have a strict policy never to
- merge any untested changes to the development branch (the only exception
- being **obviously** correct changes, such as corrections of typos).
+ [`erlang-patches`] [3] mailing list or through a pull request.
+
+* Pull requests will be handled once everyday and there will be
+ essential testing before we will take a decision on the outcome
+ of the request. If the essential testings fails, the pull request
+ will be closed and you will have to fix the problem and submit another
+ pull request when this is done.
* We merge all proposed updates to the `pu` (*proposed updates*) branch,
typically within one working day.