On 6/22/2021 3:52 PM, Brett Cannon wrote:
One thing I will remind people is I personally have led the work to move
this project from:
1. SourceForge to our own infrastructure
2. Mercurial to git
3. Our own infrastructure to GitHub for code management
At this point, I (once a skeptic) agree that the migration is an overall
improvement, with CI being the roughest.
As for issue migration: github PRs are much 'richer' in info than
Rietveld reviews, and there is now duplication of information with bpo
issues. (Where synchonization is not automated, this can be a nuisance.)
This means to me that the github issue metadata can be simplified.
After making the migration easier, this will mean less bad metadata to
be corrected by triagers.
With 2.x gone and a backport flow, essentially all issues are for main,
so leave version tags off the issue (and eliminate the need to update
them!). [3.x] in PR titles and backport labels are enough. Backport
labels imply 'behavior' versus 'enhancement.
Stage info is also on the PR.
--
Terry Jan Reedy
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/RM2ETTE2TNSC6W7QCG2HZHW4D72IWUGU/
Code of Conduct: http://python.org/psf/codeofconduct/
