| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Added a new paragraph with instructions for what happens/should be done
_after_ submitting a PR.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit polishes a lot of the make system to be more
robust and hopefully user friendly. A new DEVELOPMENT howto
guide has been added with instructions on how to work with
the Erlang/OTP code and the `make test` functionality has
been fixed so that it should work for all applications.
In order to solve the problem of some applications relying
on being tested using a release, each application has been
instrumented in its Makefile so that it knows if a release
has to be done or not.
|
|
|
| |
Refer to erlang forums instead of the mailing list.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
We want it to be as easy as possible to review a pull request without
breaking the possibility to use bisect.
The need for improvement was discovered due to PR-1968 and a first
enhancement proposal made in PR-2652, but we discovered it needed to
be reworded to fulfill our whole requirement.
|
| |
|
| |
|
|
|
|
| |
Branch names and whitespaces.
|
| |
|
|
|
|
|
| |
When a branch named 'maint' or 'master' is merged, the commit
message for the merge will be confusing.
|
|
According to https://help.github.com/articles/setting-guidelines-for-repository-contributors, a link to a file named CONTRIBUTING.md will be shown when someone is about to create a pull request. That is more visible than our Wiki pages, which are easy to miss.
Create the CONTRIBUTING.md file, based on the existing Wiki page https://github.com/erlang/otp/wiki/Contribution-Guidelines.
|