On 13/03/2023 15:44, Raphaël Gomès wrote:
The idea is to have everything run through the CI. Contributions going
through the repo and thus Heptapod makes it much easier for reviewers.
Email remains as the lowest bar of entry (since you don't need an
account and two out-of-core extensions) and for people truly allergic
to the new workflow.
I get so few email patches I forget how to queue patches that need
amending, heh. Maybe the mbox extension would help, but it's pretty
low priority for me ATM.
I agree that email patches are the simplest way to contribute -
especially when you already have it setup and working.
Also, I consider it important that Mercurial is fully self hosted when
using email patches, and it support all client side workflows. It seems
like contributing through heptapod depends on using the evolve extension
and changing the development workflow. Thanks, but no thanks.
https://www.mercurial-scm.org/wiki/ContributingChanges still mentions
email as a valid option. I will rely on that. And figure out what to do
if it is removed without a good alternative.
I hope you the patches can land for 6.4 . There will still be many test
failures for Python 3.12 , but it will be possible to get far enough to
see and fix them individually.
/Mads
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
