[riot-devel] Pull request procedure

Oleg Hahm oliver.hahm at inria.fr
Thu Aug 20 16:46:33 CEST 2015

Dear requesting IoTlers,

in order to improve and hopefully speed up the Pull request/review process, I
think it would be beneficial to describe in a better defined way how a Pull
request should be created and maintained. Therefore, I plan to put the
following rules into the wiki:

* The title and initial description of a Pull request must describe its basic
  idea and what goal is intended to be achieved in a brief and comprehensible
* The provided code and its documentation should make it very clear how this
  goal is intended to be solved.
* Keep Pull requests as small as possible. The smaller a PR, the more likely
  it gets reviewed in short time.
* Support your reviewer! Try to react as quick as possible to your reviewer's
  comments - and if only by letting her/him know, that you have currently no
  time to incorporate her/his feedback. Also, let the reviewer know if you do
  not plan to continue to work on a certain PR. Furthermore, if your reviewer
  don't react for some days, remind him!

What do you think?

panic("Unable to find empty mailbox for aha1542.\n");
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20150820/67b5fc84/attachment.sig>

More information about the devel mailing list