[Reviewers] Experimental extension criteria
Martin von Zweigbergk
martinvonz at google.com
Thu Feb 25 13:02:19 UTC 2016
You talked about the review process being a problem for these extensions,
since they want to move very fast. I think the candidates listed there are
mature enough that we should expect the same code quality and review
process when they move into hg.hg. Narrowhg currently is not that good
quality, but I also don't see a need to already get it in.
On Thu, Feb 25, 2016, 04:57 Pierre-Yves David <
pierre-yves.david at ens-lyon.org> wrote:
>
>
> On 02/25/2016 01:52 PM, Martin von Zweigbergk wrote:
> > 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?
>
> What do you mean by "moving that fast".
>
> (see the candidate section for current candidate)
>
> --
> Pierre-Yves David
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-reviewers/attachments/20160225/3481ead2/attachment-0002.html>
More information about the Reviewers
mailing list