Trac Ticket Migration

matysek edited this page Oct 18, 2014 · 7 revisions

This page describes some details about the migration process and related issues.

  • Script that was used for ticket migration: https://github.com/matysek/trac-hub

  • It was not possible to preserve the original date or map all users to github. In every migrated ticket you will find items Original Date and Original Reporter:

Original date: 2013/12/22 Original reporter: UsuallyUserName


* Github user **pyinstaller-tickets-migration** is the account that was used for migrating tickets. This user account is the author of Issues/Comments that were not mapped to github logins.
* Github handles pull requests and issues in the same ID space:
  * PyInstaller already has **156** pull requests.
  * Only tickets with ID **157+** will be preserved.
  * Tickets with lower IDs will be also migrated but their ID will be different.
  * The IDs in commit messages for ID 1-156 won't point to the correct issue.

## Trac ID Mapping Table
Table with old ticket IDs in Trac and their new ID in github issues.

<table>
<tr><th>Trac ID</th><th>Github ID</th></tr>
<tr><td>1-112</td><td>956-1042</td></tr><
<tr><td>138-156</td><td>1043-1061</td></tr>
<tr><td>395</td><td>396</td></tr>
<tr><td>396</td><td>397</td></tr>
<tr><td>397</td><td>398</td></tr>
<tr><td>980</td><td>1062</td></tr>
<tr><td>1083</td><td>1065</td></tr>
<tr><td></td><td></td></tr>
</table>

## Holes in ID Range
Due spam Trac continues some ranges of IDs without issues. For this case were created empty issues on github.

<table>
<tr><th>ID Range</th></tr>
<tr><td>190-197</td></tr>
<tr><td>214-219</td></tr>
<tr><td>243-285</td></tr>
<tr><td>288-292</td></tr>
<tr><td>916-955</td></tr>
<tr><td></td></tr>
</table>
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.