Hi Tom,
If the release manager's availability is limited, perhaps they could
designate one or more proxies to approve patches. We actually want
patches which are going to be approved to be committed as early as
possible so that they at least get exposed to testing by the other
developers, rather than having them committed immediately before the
build happens. Having the caveat that you can't approve your own
patch would make sure that we got at least two opinions on everything.
I would very much like to have a process where changes to the code are
made available in patches by the developer and tested & approved by a
second person - obliged in Yellow and Red commit mode.
If you limit the approval function to a limited group of people, then
this is the process used to built Linux. But since we are already a
limited group of people, just a second developer will do.
Anyhow, the current WOW is that only Linus approves, but he will be more
tempted to approve if there are 2 of us saying that a patch should be
approved.
So in fact, Linus is often only controlling the process, not the patches.
Regards,
Michiel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
