Open ezio-melotti opened 4 years ago
Make bpo read-only and keep Roundup running;
I really like this option but coupled with (3), maybe a read-only instance could be available on archive.bugs.python.org
or similar and then bugs.python.org/issueXXXX
links could redirect to the new Github issue. That way existing links continue to take you to the latest place for discussion but people still have the ability to search on the archived read-only roundup instance.
Roundup has a "core" and one or more tracker "instances". The fork of Roundup that we are currently hosting/running is used by 3 instances:
Since the other two instances rely on us, we need to keep this into account before we shut down Roundup/bpo.
Jython
Roundup
CPython
After the migration to GitHub issues is completed, we have at least 3 options:
Make bpo read-only and keep Roundup running;
Create a static mirror of bpo and shut down Roundup:
Create a script that redirects to the corresponding GH issue:
Since this issue is non-blocking, we can adopt the first option and then switch to the second or third down the line, depending on what the other projects do.