How to confirm a bugfix for Mercurial
Kevin Bullock
kbullock at ringworld.org
Thu Jan 30 14:30:08 UTC 2020
> On Jan 29, 2020, at 6:06 AM, Alexander Johannes <aj at juston.com> wrote:
>
> I had an issue with the interactive commit (aka crecord), which has been fixed by this commit:
>
> https://www.mercurial-scm.org/repo/hg/rev/ae596fac8ba0
>
> I found no changed tests for this issue or a corresponding bug ticket. How do the hg maintainers decide that this fix will be shipped with the next release?
Thanks for reporting the issue. The fix is committed on the stable branch, therefore it will be in the next stable release, which is due in a few days (see https://www.mercurial-scm.org/wiki/TimeBasedReleasePlan).
As far as test changes, it looks to me like an issue that would have passed tests on Python 2 but failed on Python 3. The test suite is run against both versions as Python 3 support is being stabilized.
pacem in terris / мир / शान्ति / سَلاَم / 平和
Kevin R. Bullock
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20200130/f180d462/attachment-0002.html>
More information about the Mercurial
mailing list