On 12/20/24 13:20, PIERRE AUGIER wrote:
I'm debugging a bad behavior of Windows wheels, which are quite broken because
ofhttps://foss.heptapod.net/mercurial/mercurial-devel/-/blob/branch/default/hg
andhttps://foss.heptapod.net/mercurial/mercurial-devel/-/blob/branch/default/contrib/win32/hg.bat
and because `hg` is not an entrypoint. I need to open an issue where these
things can be discussed.
Improving Mercurial in term of packaging is already difficult but if one cannot
fully usehttps://foss.heptapod.net/mercurial/mercurial-devel, that's beyond me.
Really, for the point of view of users and
contributors,https://bz.mercurial-scm.org/ is bad. I understand that it has to
stay there but at least
openhttps://foss.heptapod.net/mercurial/mercurial-devel/-/issues for people
used to more modern and integrated issue trackers.
I am not sure `https://bz.mercurial-scm.org/` "has to stay". I think we
don't want to have two issue trackers, but migrating from bz to Heptapod
could make sense. Especially now that most development and CI happens on
Heptapod. We migrated from roundup to Bugzilla in the past, we could
migrate from Bugzilla to Heptapod.
What does other developer things about that ?
--
Pierre-Yves David
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
