Testing an RC of evolve 11.0.0 and topic 1.0.0

[Anton Shestakov]

03.02.2023 00:34, Uwe Brauer пишет:
>> 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)
>>
>> 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
> 
> I use topics quite extensively, but my collaborators not.
> Strangely enough I see this structure sometimes in the current evolve version (and it annoys me quite a bit). Will this behavior be configurable (ie. Switch it off)?

By "this" do you mean "branch:topic" or "branch//topic"?

What version of evolve do you have?

> BTW what are the minimum requirements for this evolve version you describe.

At the moment we're planning to still support Mercurial 4.8.

> Would be hg 5.2 ok (either compiled with python 3.5 or 2.7)?

It would, but you should upgrade.