Browse files

readme: changed information about pull requests

  • Loading branch information...
1 parent 4c3b306 commit f4394d1b8a170010887597c013be556284e86766 @gustehn gustehn committed Jun 26, 2013
Showing with 7 additions and 4 deletions.
  1. +7 −4
@@ -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.

0 comments on commit f4394d1

Please sign in to comment.