D761: test: backout update evolution config

2017-10-16 Thread lothiraldan (Boris Feld)
lothiraldan abandoned this revision. lothiraldan added a comment. I've started splitting the configuration, need to finish it before the freeze. As the stack will be unrelated to https://phab.mercurial-scm.org/D761 and https://phab.mercurial-scm.org/D762, I think we can close this stack. REP

D761: test: backout update evolution config

2017-10-13 Thread durin42 (Augie Fackler)
durin42 added a comment. In https://phab.mercurial-scm.org/D761#13848, @lothiraldan wrote: > @durin42 Good for me, I don't have strong opinion on the matter. I will have a patch ready for the sprint. What's the story with this revision? Should we close it and https://phab.mercuri

D761: test: backout update evolution config

2017-09-27 Thread lothiraldan (Boris Feld)
lothiraldan added a comment. @durin42 Good for me, I don't have strong opinion on the matter. I will have a patch ready for the sprint. REPOSITORY rHG Mercurial REVISION DETAIL https://phab.mercurial-scm.org/D761 To: lothiraldan, #hg-reviewers, pulkit, quark Cc: durin42, quark, pulkit,

D761: test: backout update evolution config

2017-09-26 Thread durin42 (Augie Fackler)
durin42 added a comment. I would bias towards just having one change that advances to using `[experimental]` if we want to rename this again. I don't think we need to take the rollback-then-forward approach, seems like unnecessary ceremony. Let's just talk this over at the sprint? REPOSITOR

D761: test: backout update evolution config

2017-09-26 Thread lothiraldan (Boris Feld)
lothiraldan added a comment. Sorry for the lag, I was at a conference. I didn't planned for such changes, but I think it's a very good idea! I'm gonna send patches soon. Do you think I should start a new series of patch or add new patch on top of the backout? REPOSITORY rHG Mercurial

D761: test: backout update evolution config

2017-09-21 Thread durin42 (Augie Fackler)
durin42 added a comment. I concur with @quark: if we're going to bother renaming this again, we should just use the `[experimental]` namespace. REPOSITORY rHG Mercurial REVISION DETAIL https://phab.mercurial-scm.org/D761 To: lothiraldan, #hg-reviewers, pulkit, quark Cc: durin42, quark,

D761: test: backout update evolution config

2017-09-21 Thread quark (Jun Wu)
quark requested changes to this revision. quark added a comment. This revision now requires changes to proceed. Although "stabilization" may be controversial, but I don't think "evolution" is a strictly better than that. I think it makes more sense to split the giant config into different

D761: test: backout update evolution config

2017-09-21 Thread pulkit (Pulkit Goyal)
pulkit accepted this revision. pulkit added a comment. The evolution config name makes sense. stabilization was ambiguous. REPOSITORY rHG Mercurial REVISION DETAIL https://phab.mercurial-scm.org/D761 To: lothiraldan, #hg-reviewers, pulkit Cc: pulkit, mercurial-devel _

D761: test: backout update evolution config

2017-09-21 Thread lothiraldan (Boris Feld)
lothiraldan created this revision. Herald added a subscriber: mercurial-devel. Herald added a reviewer: hg-reviewers. REVISION SUMMARY The concept is still call "Changeset Evolution". The "troubles" got renamed to "instability", so the action can be renamed from "evolve troubles" to "stabili