httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject Re: svn commit: r798359 - in /httpd/httpd/branches/2.2.x: modules/ssl/ssl_engine_init.c modules/ssl/ssl_engine_kernel.c modules/ssl/ssl_engine_vars.c modules/ssl/ssl_util_ssl.c support/ab.c
Date Wed, 29 Jul 2009 00:34:47 GMT
Nick Kew wrote:
> What do you mean by "override STATUS flow"?

The convention is "propose in status, collect votes, commit when approved".

But the policy is not "propose in STATUS", the *policy* is "review, then
commit".  The devs can work these rules in whatever manner best accomplishes
forward progress, so this list is free to suspend these rules in specific
cases.  An example are platform patches; nobody complains if Guenter just
fixes a Netware build flaw, if Bill patches the win32 build files, or if
Joe went ahead and fixed the rpm build files.

Common sources generally require review-then-commit.  STATUS does NOT
override the dev@ list for decision making.  It's simply a vehicle of
convenience.  Any review that occurs on dev@ is just as binding, if not
more so, than STATUS.  Only *this list* gives STATUS binding authority.

If some minority vote against patches based on their absence from STATUS,
so be it.  Seems like bureaucracy to me in certain cases, and entirely
the most efficient approach in other cases.

View raw message