[Reviewers] Experimental extension criteria

[Martin von Zweigbergk]

I just didn't see what experimental extensions might be candidates. If they
need to be moving that fast, I'm wondering if they can't just handle it
themselves by living in a fork of hg core. Can you give examples of
extensions that we're talking about?

On Thu, Feb 25, 2016, 00:55 Pierre-Yves David <
pierre-yves.david at ens-lyon.org> wrote:

>
>
> On 02/25/2016 01:06 AM, Martin von Zweigbergk wrote:
> > Perhaps an alternative would be to develop these experimental extensions
> > in forks/branches of hg core? That would address the "Easier to
> > contribute (same process and testing as the rest of the core work)."
> > item. Has that been considered?
>
> It seems like you have broken out of the criteria section ;-).
>
> I'm not too concerned about the "possible drawback" section for now.
> There is multiple extensions that are used only by Facebook/Google (and
> therefore don't car about release cycle) and that are mature enough to
> not see major amount of code update yet (mostly on Facebook side). So
> I'm trying to move forward with the less contrainted one.
>
> Should I read the fact your break out of the criteria section without
> comment as "You have no complains/improvement idea" about the criteria.
>
> If so, when can we expect narrow to drop there :)
>
> --
> Pierre-Yves David
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-reviewers/attachments/20160225/4451fddb/attachment-0002.html>