[PATCH 7 of 7] configitems: adds a developer warning when accessing undeclared configuration

Augie Fackler raf at durin42.com
Wed Oct 18 11:40:00 EDT 2017


> On Oct 18, 2017, at 09:18, Boris Feld <boris.feld at octobus.net> wrote:
> 
> On Tue, 2017-10-17 at 11:27 -0400, Augie Fackler wrote:
>> On Mon, Oct 16, 2017 at 06:53:32PM +0200, Boris Feld wrote:
>>> # HG changeset patch
>>> # User Boris Feld <boris.feld at octobus.net>
>>> # Date 1508168487 -7200
>>> #      Mon Oct 16 17:41:27 2017 +0200
>>> # Node ID 7a2c3832349499f8b00b9db64e6b87ff644faa9d
>>> # Parent  d64632aed1d71fd2750aca29fe09d8a2e86921cd
>>> # EXP-Topic config.register.ready
>>> # Available At https://bitbucket.org/octobus/mercurial-devel/
>>> #              hg pull https://bitbucket.org/octobus/mercurial-deve
>>> l/ -r 7a2c38323494
>>> configitems: adds a developer warning when accessing undeclared
>>> configuration
>> 
>> I've queued patches 1-6. This one I'm inclined to wait until the 4.5
>> cycle, given how annoyingly invasive it's going to be for third
>> parties. Otherwise there's no released-hg transition window for
>> extensions.
>> 
>> What do you think? What about others? Durham, I suspect this will be
>> particularly annoying for y'all?
> 
> We would prefer to have it in this cycle. We want all extensions to
> have their configuration registered to start beginning working on the
> cool stuff.

Closing the loop from an irc conversation: my concern was that there be a transitional release that has the registrar mechanism but not the enforcement of using the registrar, so that you don't have to have a "big bang" upgrade process where (in order to pass tests) you have to upgrade all your extensions and hg simultaneously. Fortunately, 4.3 includes the registrar mechanism, so we're good, and I've queued patch 7. Thanks!



More information about the Mercurial-devel mailing list