aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBjörn Gustavsson <[email protected]>2016-06-15 12:29:32 +0200
committerBjörn Gustavsson <[email protected]>2016-06-15 12:33:10 +0200
commit2ce17d44eba8993985f49abafc78d6c0f99bef27 (patch)
tree5e6ed19bbb7264c2c77bd504c1bd935cc9270191
parentdb21a04892e7cfd8d4ebad668a666b789604fcfb (diff)
downloadotp-2ce17d44eba8993985f49abafc78d6c0f99bef27.tar.gz
otp-2ce17d44eba8993985f49abafc78d6c0f99bef27.tar.bz2
otp-2ce17d44eba8993985f49abafc78d6c0f99bef27.zip
Simplify the rules for submitting patches
We don't want patches via the mailing lists anymore. All the other information about how we handle patches is better put in the Wiki.
-rw-r--r--README.md26
1 files changed, 4 insertions, 22 deletions
diff --git a/README.md b/README.md
index 9986d6bc18..127ac9cad7 100644
--- a/README.md
+++ b/README.md
@@ -36,29 +36,11 @@ Here are the [instructions for submitting patches] [2].
In short:
-* Go to the JIRA issue tracker at [bugs.erlang.org] [7] to see reported issues which you can contribute to. Search for issues with the status *Contribution Needed*.
+* Submit your patch by opening a new Pull Request.
-* We prefer to receive proposed updates via email on the
- [`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.
-
-* At least once a day, the contents of the `pu` branch will be built on
- several platforms (Linux, Solaris, Mac OS X, Windows, and so on) and
- automatic test suites will be run. We will email you if any problems are
- found.
-
-* If a proposed change builds and passes the tests, it will be reviewed
- by one or more members of the Erlang/OTP team at Ericsson. The reviewer
- may suggest improvements that are needed before the change can be accepted
- and merged.
+* Go to the JIRA issue tracker at [bugs.erlang.org] [7] to
+ see reported issues which you can contribute to.
+ Search for issues with the status *Contribution Needed*.
Bug Reports