[Dev] Rotating build sheriff duties?

[Andi Vajda]

On Wed, 7 Dec 2005, Mike Taylor wrote:

>
> On Dec 7, 2005, at 2:50 PM, Andi Vajda wrote:
>
>> 
> With SVN (and even CVS) you just cannot "override" access without having 
> access to the server - that would mean that each person who wanted to commit 
> would need to connect to the server, flip the config file to enable their 
> acount, commit, flip it back and then log out.  Sounds worse than just 
> telling people to be aware (which they should be anyway IMO.)

This can be done with an ssh-based script. Doing it manually would be bad 
indeed.

> I just don't get why this is such a hard or tedious task - don't devs already 
> have a "best practices" list of things to do:
>

>  - check code status to make sure you have latest build
    yes

>  - verify your code works with latest tests
    no, run *all* unit tests, even the old ones, before you check in

>  - verify you are only checking in code that you want to check in
    yes

> and so on - why not just add "check tinderbox in X minutes" to make sure your 
> change hasn't broken the different OS related builds?

   I'm much more likely to check my email than the tinderboxes. I also have an
   IRC window open most of the time. But I don't have a browser window open
   most of the time (small laptop screen).

Andi..