[bind10-dev] Handling regressions due to #213

[JINMEI Tatuya / 神明達哉]

At Fri, 21 Oct 2011 16:07:59 +0200,
Michal 'vorner' Vaner <michal.vaner at nic.cz> wrote:

> Currently, the #213 is in review (it's the configuration for boss ticket).
> However, it turned out quite big already and there are few things to do, some of
> them are annoying regressions. The most annoying parts are:
> 
> • The brittle mode is gone. We might want to return it or not, as the new way of
>   configuration allows admin to specify all components as core, which in turn
>   will mean if they die, the whole system goes down. It's just more work to do,
>   as the configuration is not global, but per-component and isn't per one run of
>   boss.
> • The delayed restart is gone, it restarts right away. If there's a problem why
>   it can't start, it loops.
> • The bindctl handling of named_set isn't the best possible, which means it's
>   quite hell to figure out how to configure it.
> • No user docs. At all.

For these I personally only care about the second one.  I've never
used the brittle mode; configuration difficulty is not good but to be
fair it's not that easy for other modules anyway, so at least as long
as the default configuration works fine I'm okay with that; lack of
doc is also bad, but again it's not so different from the current
situation (and no doc does not itself cause program crash or other
behavioral regression).

But different people should have different opinions/preferences, and I
guess Jeremy is the champion on this kind of thing.

> I believe these are problematic enough not to give it to users this way. So
> there are actually three ways to solve it, each one having some pros and cons,
> so I'd like to discuss what should we do about them:
> • Act as nothing usual happens, just merge the branch once it's reviewed
>   properly, create tickets for them and hope we solve them before release
> • Branch from that branch, and merge it back to master once they are solved.

I'd choose either of this (for the first case, as soon as we support
the delayed restart).  If you (we) choose the second option, I'd also
suggest performing various automatic tests on the buildbots for that
branch (or those branches).

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.