<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello Erlang-patches!<br>
<br>
This is a summary email that will be sent out to the erlang-patches
list from time to time. In this email you will find information
regarding code-stops, release dates, and useful links to ease your
patching.<br>
<br>
I will also take this opportunity to describe our way of working and
testing.<br>
<br>
RELEASE DATES<br>
<br>
Below you can find the planned release dates, and code stop dates
for 17.0.<br>
Note: We will not accept any NEW feature patches for inclusion in
Erlang/OTP 17.0 after 2014-02-21.<br>
<br>
Preliminary dates for the upcoming release:<br>
Release: erts, emu,comp |Code stop |Documentation
stop |Release Date<br>
17.0-rc2 2014-02-21 2014-02-21 2014-02-21
2014-02-26<br>
17.0 2014-03-10 2014-03-17
2014-03-19 2014-03-26<br>
<br>
We will focus the time between 17.0-rc2 and 17.0 on bug fixes,
improvements, and testing. Therefore you are most welcome to submit
patches regarding such issues and we will try our best to include
them before 17.0 is released.<br>
Especially bugs introduced in 17.0-rcX.<br>
<br>
PATCHES:<br>
<br>
Make sure to look at our Github wiki page before submitting a patch
to Erlang/OTP<br>
<a class="moz-txt-link-freetext"
href="https://github.com/erlang/otp/wiki">https://github.com/erlang/otp/wiki</a><br>
<br>
We also have a page on Erlang.org concerning the status of submitted
patches<br>
<a class="moz-txt-link-freetext"
href="http://www.erlang.org/development/">http://www.erlang.org/development/</a><br>
<br>
There you can find information about patches that are
"awaiting_action", Waiting for the topic author to correct one thing
or another.<br>
Assigned to a team within Erlang/OTP, to be reviewed and
approved/dropped.<br>
Or scroll <span style="color: rgb(51, 51, 51); font-family:
'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 13px;
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: 18px; orphans: auto;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(240, 240,
240);"><span class="Apple-converted-space"></span></span>through
the list of graduated patches since R16B.<br>
<br>
We currently have ~25 patches that are "awaiting_action".<br>
There is a total of 27 patches that are assigned to a developer or a
team, awaiting their review. And we have 5 patches that are approved
but still needs to pass our nightly builds and tests.<br>
<br>
After a request from the Industrial Erlang User Group, we started
using Github pull requests for accepting patches into Erlang/OTP.
This has resulted in over 200 pull requests sent in less than 8
months of accepting pull requests. <br>
We are looking into ways of improving this especially in regards to
information preservation.<br>
<br>
<br>
BEFORE SUBMITTING A PATCH:<br>
<br>
To facilitate a faster review process please make sure that your
commit message conforms to the rules at the github wiki page.<br>
<a class="moz-txt-link-freetext"
href="https://github.com/erlang/otp/wiki/Writing-good-commit-messages">https://github.com/erlang/otp/wiki/Writing-good-commit-messages</a><br>
Make sure that your code compiles.<br>
Make sure that all tests for the changed application pass.<br>
<br>
If applicable you will be asked to add tests and documentation for
your patch.<br>
<br>
TESTING:<br>
<br>
We currently test on ~60 different setups, including but not limited
to Bsd, linux, solaris, darwin and windows. This includes different
hardware as well as software. This sums up to about ~850 000 test
cases each night. We also run dialyzer and cover.<br>
<br>
Unfortunately the test coverage is not 100% in all tools and
applications. Some tools and applications have bad or missing tests.
This is something we aim to improve and you are all invited to help
by submitting patches in these areas.<br>
<br>
When we are aiming for a new major release, as we currently are, all
platforms tests the master branch. When we are releasing a minor
version, we have a reasonable split amongst the test platforms so
that we still run tests for the master branch and new features.<br>
<br>
All builds consists of a mix of internal development branches, and
open source contributions. This limits the amount of open source
branches we are willing to test at the same time. We do not wish
them to interfere with our branches or other open source branches.<br>
This might be another reason as to why your branch is not tested for
a few days.<br>
<br>
<br>
Useful links<br>
<a class="moz-txt-link-freetext"
href="https://github.com/erlang/otp/wiki">https://github.com/erlang/otp/wiki</a><br>
<a class="moz-txt-link-freetext"
href="http://www.erlang.org/development/">http://www.erlang.org/development/</a><br>
<a class="moz-txt-link-freetext"
href="https://github.com/erlang/otp/wiki/Writing-good-commit-messages">https://github.com/erlang/otp/wiki/Writing-good-commit-messages</a>
<pre class="moz-signature" cols="72">--
/Henrik Nord Erlang/OTP</pre>
</body>
</html>