[bind10-dev] policy on reverting changes due to broken builds for too long

[Jeremy C. Reed]

We should discuss a policy to revert commits that break builds for too 
many systems for too long.

Based on comments from others on jabber:

- possibly delays other merges

- if other merges fail, we may not easily or quickly recognize

- should be fixed at the highest priority (before other work?)

- should be fixed with a few hours

- if fix requires intensive reviews or time to fix, then offending 
change should be reverted

As a suggestion:

If build fails on two or more different platforms (operating systems or 
architectures) or two or more compilers, and it becomes realized that 
the fix will take more than three hours, let's revert the commit and 
have it fixed in a branch.

So what is needed is a way to get branches tested on the build servers. 
In the meanwhile, developers may use some of the build servers to verify 
manually.

Any comments?

  Jeremy C. Reed
  ISC