Re: Enter the build sheriff: Jacob.

[jacob berkman <jacob ximian com>]

On Thu, 2002-03-14 at 02:36, Daniel Veillard wrote:
> On Mon, Mar 11, 2002 at 11:37:00AM +0000, hobbit aloss ukuu org uk wrote:
> > Putting my release team hat on here: 
> > 
> > On Mon, Mar 04, 2002 at 03:53:35PM +0000 or thereabouts, Michael Meeks wrote:
> > >
> > > 	Maintainers of all modules are encouraged to add general
> > > provision for sheriffs, by appending: "build sheriff commits welcome"
> > > to their HACKING files. alternatively, something like "the following
> > > people may commit as build sheriffs: A.N.Other" would limit the list
> > > of approved sheriffs to those named.
> > 
> > Quite a few people have done this, but please, if you have a stable
> > module and have opinions on build sheriffs, add something relevant
> > to the HACKING file. 
> 
>   I did not update the HACKING file. I want to retain controle of
> my module. I want to receive a message with explanations before something
> get changed in my module.
>   BUT, the build sheriff commited twice already without sending any mail
> informing me of the potential problem.

i checked HACKING and it said:

     In the exceptional case where a serious breakage in this module
    prevents other core projects from making progress, then feel free
    to patch first and send mail afterward as long as the changes are
    limited.
    
and in both cases this was true.

jacob
--