Mercurial 5.2rc0 tagged

[Gregory Szorc]

I was planning on hacking on Python 3 packaging this week. Expect some
patches for stable for that. I could be quite a number, however.

Regarding Python 3, did we decide how to communicate the Python version
split in Mercurial's version numbers? I know we floated doing a Python 3
primary release of 5.2 a week or two after 5.2 is released. Should we make
that 5.3? Or do we just want to put the Python version in the package
filename somewhere?

On Mon, Oct 21, 2019 at 8:31 AM Augie Fackler <raf at durin42.com> wrote:

> Please update your package builds, thanks.
>
> Release notes are being aggregated, but this does include one substantial
> change: `hg grep` now does what users expect, instead of something that
> nobody ever used. If you have a mechanism for communicating big changes
> like that to your users, you may want to advise them of that one.
> _______________________________________________
> Mercurial-packaging mailing list
> Mercurial-packaging at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-packaging
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-packaging/attachments/20191021/e85a75d2/attachment-0002.html>