@ezio-melotti, if I understand correctly, Eric is asking about the opposite to what you described. He’d like to migrate the old issues first, only marking those as read-only on BPO.
This idea is very complicated in practice because:
- as soon as those closed issues were migrated, Github issues would be open and would require policing that “this is for old issues only for now, please don’t create new ones!”;
- while closed issues are closed, some still receive activity, to the point of being re-opened.
We currently don’t have the ability to keep Github issues disabled during the migration. Our friends at Github are looking into whether this could be introduced but from their initial assessment, it looks like they would need a much longer timeframe to implement changes to their migration tooling than we are willing to wait.
The idea to have two issue trackers open at the same time is making me nervous.