Re: Testing an RC of evolve 11.0.0 and topic 1.0.0
>>> "AS" == Anton Shestakov writes: Hi Anton, > Hello, users of Mercurial, Evolve and/or Topic! > We're planning to release a feature release candidate of evolve and > topic extensions that contains an implementation of a concept that was > in the plans for quite some time: topic namespaces (the name could > change, if we find something better) > https://www.mercurial-scm.org/wiki/TopicPlan#sub_branches.2C_namespacing_and_representation > In short, topic namespaces are trying to fix one of our major UX > flaws: branches can continue to be used for release management, and > topics can still be used for implementing features, but now there > would be something for organizing topics into wider concepts. Topic > namespaces, just like topics, are designed to go away when you publish > your commits, and we tried to make them as unobtrusive as possible, to > not get in the way of current workflows. There is a default topic > namespace that will not clutter the UI, and users can keep using only > branches and topics as usual. > But we did change some things in the UI. Remember seeing > "branch:topic" format in `hg branches`? Well, it was a temporary > implementation detail. With the implementation of topic namespaces we > introduce a more thought-out way to represent branches plus topics. In > this new format, topic namespaces become sort of a glue for all things > related to (named) branching, e.g. this is what you'd see in hg log: > branch//namespace/topic > or, if you don't set topic namespace: > branch//topic Strangely enough I see this sometimes in the current evolve version (and it annoys me quite a bit). Will this behavior be configurable (ie. Switch it off)? BTW what are the minimum requirements for this evolve version you describe. Would be hg 5.2 ok (either compiled with python 3.5 or 2.7)? Regards Uwe Brauer smime.p7s Description: S/MIME cryptographic signature ___ Mercurial-devel mailing list Mercurial-devel@lists.mercurial-scm.org https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
mercurial-devel | Failed pipeline for branch/stable | ac93876e
Pipeline #62092 has failed! Project: mercurial-devel ( https://foss.heptapod.net/mercurial/mercurial-devel ) Branch: branch/stable ( https://foss.heptapod.net/mercurial/mercurial-devel/-/commits/branch/stable ) Commit: ac93876e ( https://foss.heptapod.net/mercurial/mercurial-devel/-/commit/ac93876ea2dff400ab05097ee5c32da210b7c395 ) Commit Message: setup: treat error output and non-zero return c... Commit Author: Pierre-Yves David ( https://foss.heptapod.net/marmoute ) Pipeline #62092 ( https://foss.heptapod.net/mercurial/mercurial-devel/-/pipelines/62092 ) triggered by Raphaël Gomès ( https://foss.heptapod.net/raphael.gomes ) had 1 failed job. Job #1662421 ( https://foss.heptapod.net/mercurial/mercurial-devel/-/jobs/1662421/raw ) Stage: tests Name: test-chg -- You're receiving this email because of your account on foss.heptapod.net. ___ Mercurial-devel mailing list Mercurial-devel@lists.mercurial-scm.org https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
mercurial@49971: 2 new changesets (2 on stable)
2 new changesets (2 on stable) in mercurial: https://www.mercurial-scm.org/repo/hg/rev/8d390a13474d changeset: 49970:8d390a13474d branch: stable user:Pierre-Yves David date:Mon Jan 30 18:41:59 2023 +0100 summary: setup: make the version computation process more resistant https://www.mercurial-scm.org/repo/hg/rev/ac93876ea2df changeset: 49971:ac93876ea2df branch: stable tag: tip user:Pierre-Yves David date:Mon Jan 30 18:50:11 2023 +0100 summary: setup: treat error output and non-zero return code differently -- Repository URL: https://www.mercurial-scm.org/repo/hg ___ Mercurial-devel mailing list Mercurial-devel@lists.mercurial-scm.org https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
mercurial@49969: new changeset (1 on stable)
New changeset (1 on stable) in mercurial: https://www.mercurial-scm.org/repo/hg/rev/84680c003d44 changeset: 49969:84680c003d44 branch: stable tag: tip user:Matt Harbison date:Mon Jan 30 18:25:11 2023 -0500 summary: bundlerepo: enforce the requirements declared by the underlying repository -- Repository URL: https://www.mercurial-scm.org/repo/hg ___ Mercurial-devel mailing list Mercurial-devel@lists.mercurial-scm.org https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
Announcing Mercurial Paris 2023 schedule and speakers
We’ve finalized picking our speakers for the *Mercurial Conference Paris 2023*! https://mercurial.paris/posts/2023/01/20/mercurial-paris-2023-speakers-talks-announcement/ The event will take place from *the Wednesday 5th of April 9:00 am to the Friday 7th of April 5:00pm* in *Paris, Sorbonne University.* The first day, will be dedicated to *workshops*, the second to *talks* and the third to *sprint* and hack around Mercurial. Register your tickets now and see you in April in Paris to hear the #mercurial experts! https://mercurial.paris/events/mercurial-conference-paris-2023/ Best regards --- Franck Bret Software Developer @octobus Mercurial Conference Paris Organization Committee +33(0)6 03 90 65 98 https://mercurial.paris/ ___ Mercurial-devel mailing list Mercurial-devel@lists.mercurial-scm.org https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
