Hi, On Thu, May 01, 2014 at 10:57:29PM +0300, Samuli Seppänen wrote: > I will have a look at the developer docs to ensure they accurately > reflects our current practices. I will also try to outline the various > ways people can use get their patches merged more easily with least > amount of frustration and delays.
Thanks.
It might be good to also point out our ACK regime ("it does not go in
unless reviewed by someone who is trusted to understand the impact of
the change"), and the reason why things sometimes just do not seem to
be moving - "lack of development time".
I do like Timeothe's enthusiasm, but things like "if nobody said something
for 14 days, it goes *in*" is just not realistic with the amount of
potential ACKers we have right now - and at some times, we all have very
very busy phases, where we can barely follow the list, let alone give
meaningful advice about patches. This approach is also dangerous - our
ACK policy is there to ensure that patches are reviewed for security
critical side effects, and in doubt, well-tested. So far, this succeeded
quite well - even if it's a major pain at times, because it truly slows
down everything...
Also, someone would actually have to "put it in" in that case, and as
the only one actively committing stuff right now is *me*, somethings
things just don't happen. Like, for the next few weeks, I will be busy
with paid-for work that is not openvpn related, so I won't be very
active unless some sort of emergency patch comes up.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgpYf9ppRN0jz.pgp
Description: PGP signature
