Milestone closed_at date is wrong

[mkoeppe]

as seen in https://34.105.185.241/sagemath/sage-all-2023-01-14-004/milestones?state=closed

[mkoeppe]

I now set both closed_at and updated_at, but after the import both show the time of import.

This seems to be a bug of the importer -- question for the GH migration team.

[kwankyu]

This is important. Was the question asked to the GH team?

[kwankyu]

So this is not fixed even in the import to GitHub.com.

[mkoeppe]

Yes. Out GH contacts indicate that it cannot be fixed.

After the import, I suppose we can edit the milestone description to include the correct closing date.

[kwankyu]

The correct closing date is defined by some event in the repo or is a new information that we should fetch from trac?

[mkoeppe]

We have it in the migration archive, in these files:

milestones_000000.json.txt
milestones_000001.json.txt

[kwankyu]

It's strange that GH cannot fix the obvious bug in their importer.

Hopefully we could edit the dates in an automatic way later.

Thanks.