plan for a thg 7.2 release?

[Antonio Muci]

Hi,

I think it would be useful to tag a thg 7.2 release with compatibility
with Mercurial 7.2.

This would trickle down to Linux distributions, benefiting them, since
most of them are currently packaging hg 7.2 and thg 7.0.1, which are
incompatible.

My attention is limited to the linux world. Do the Windows installer
also need to bundle hg-git? Can a thg version be tagged and hg-git be
packaged later on?
Moreover, I see that the CI on Heptapod is in need of some maintenance
(currently, some jobs fail because uv is not in the base image), but I
do not know who takes care of that, and if that problem is a blocker or not.

I was not able to attend the London sprint, so I do not know if there is
a high level plan. I just wanted to know what are the most pressing open
points.

Antonio

[Matt Harbison]

First, thanks for all of the effort to adapt to the 7.2 changes.

Second, I just sent a series that should mostly fix up the CI for now- it's finally green.  The one thing not fixed is we still use the old style version strings for non-tagged builds, so I had to hardcode setup.py.  If you pull the ci-uv topic, you'll see what I mean.  When my series lands, I'll rebase this one commit and you can stack any other changes on top of that in your own topic when using CI until that gets fixed.  This doesn't affect tagged builds, so we should be able to tag a 7.2.2 release without untangling that.

I asked in IRC what the status of hg-git is, and haven't gotten an answer, so I assume it is broken.  I'm fine with skipping the Windows build for now, so we can get the linux distros straightened out.

The next up is modernizing the build process, namely migrating to pyproject.toml.  We're probably getting lucky that it still builds when Mercurial wants a much newer version of setuptools.  There's a topic called "pep517" that starts this work, but I couldn't get it working.  Feel free to add stuff to that if you're knowledgeable in that area.  If we have to drop Qt5 support, we can, but it is more stable than Qt6 and would be another pile of headaches to deal with on Windows.

I also need to make a new container image, but the process for doing it has totally changed so there's a bit of a learning curve.  It'll be a good opportunity to add modern python and other tools, but what we have now should be good enough in the short term.