Repository navigation
Migrate b.p.o issue tracking from the meta-tracker #1
Description
Step 1: ask folks to start filing new issues here rather than on http://psf.upfronthosting.co.za/roundup/meta/ (as per http://psf.upfronthosting.co.za/roundup/meta/issue655 )
Step 2: figure out what to do with previously filed issues? Close them? Migrate them somehow?
Activity
ezio-melotti commentedon Jun 15, 2018
Step 1 should be easy: there's a link a to the meta-tracker in the b.p.o sidebar and possibly a few other links in the docs/devguide that would need to be updated.
As for the other issues, I think we should go through the open ones, close the obsolete ones (e.g. the ones about rietveld), and move here the rest. I don't think we need to migrate the closed ones to github unless it's trivial to do, but it would be nice if there was still a way to access them somewhere since they do come up every once in a while (mostly when a changeset is related to a specific issue number, and I need some background about the changes).
ncoghlan commentedon Jun 16, 2018
I reviewed the titles of the open meta-tracker issues, and closed a couple as obsolete (with a link back to this issue). Most of them looked likely to still be valid, though (since they related to things like authentication, the web UI, email notifications, reply-by-email, etc).
As far as archiving goes, perhaps whatever is done for the setuptools repo (#4) could also be done for the meta-tracker repo? That way it could be frozen with a link to this issue tracker instead.
ncoghlan commentedon Jun 17, 2018
Ah, checking tracker-discuss, I see the reason the Reitveld ones were already closed is because @berkerpeksag already went through and closed them as out of date a few days ago :)
terryjreedy commentedon Feb 6, 2019
The current state relative to 'b.p.o metatracker' is a mess and that b.p.o, the devguide, and psf-infra-meta all need changes (by someone with authority to do so consistently on all three).
Point b.p.o sidebar to this tracker. The b.p.o sidebar was actually updated to https://github.com/python/psf-infra-meta. I believe that this was fairly recent, and a mistake. https://github.com/python/psf-infra-meta/blob/master/README.md says that it was mainly created for b.p.o, but https://github.com/python/psf-infra-meta/issues shows that it initially got issues for other things. Issues for b.p.o started just last December, hence the belief stated above.
Point devguide to this tracker. Link to meta tracker broken devguide#456 is about updating the devguide link. It seems it should be updated to this tracker, but that should not be done until the tracker itself is updated to this tracker.
Fix psf-infra-meta. Its readme should say that it is for things other than b.p.o and point here for b.p.o issues. Consider moving the few existing b.p.o issues here if possible.
terryjreedy commentedon Feb 6, 2019
https://psf.upfronthosting.co.za/roundup/meta/ currently resolves to a blank page with no error message. The old issues, with /issuennn, are not accessible either. Update: it eventually timed out after a few minutes.