[bind10-dev] policy on reverting changes due to broken builds for too long
Shane Kerr
shane at isc.org
Thu Feb 24 16:27:36 UTC 2011
Jeremy,
On Wed, 2011-02-23 at 16:24 -0600, Jeremy C. Reed wrote:
> 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?
This seems sensible to me.
Note that we should probably have a page on the Trac site describing how
to revert a merge. (I realize it's probably a one-command Git action,
but it won't hurt to write it there, right?)
I think when we revert, we should probably re-open the ticket for the
change too.
Finally, it might be useful if developers could request a build across
our test platforms in advance of merging to master. Is this something
that is easy to do?
--
Sham
More information about the bind10-dev
mailing list