Extending extension lookups

[Martijn Pieters]

On Mon, Jan 18, 2016 at 2:10 AM, Matt Mackall <mpm at selenic.com> wrote:
> I guess I don't see what the advantage is here over simply adding the
> "(EXPERIMENTAL)" flag to the top of the docs. Commands and extensions marked
> experimental are hidden from the help today (see the chg extension) and we are
> free to have whatever stability policy we want with them.
>
> I guess if people find extensions by poking around on disk, they might be slightly more prone to not realizing a given extension is experimental if it's not in a separate directory.. but I must confess I have pretty limited sympathy for people who poke around in source code without looking at either the source or the docs.

The underlying goal was to separate release cycles and contribution
requirements for the experimental extensions from the main mercurial
repo. See https://www.mercurial-scm.org/wiki/ExperimentalExtensionsPlan.

I'm not specifically attached to hgext/experimental in that respect;
if a separate package (`hgext_experimental`, for example) works better
to facilitate the goal of separation then so be it.

-- 
Martijn Pieters