moving trac tickets to GitHub

[sa2ajj]

Rationale

easier linking of incoming PRs to existing tickets

Must have

Only 0.9+ tickets are migrated

Nice to have

bb-bot is the "reporter" of the issues.

What else to have?

Express your requirements here.

Trac Ticket Fields

• summary
• reporter
• description
• type
• priority
• milestone
• version
• keywords
• CC

GitHub Ticket Fields

• title
• body
• assignees
• milestone
• labels

Mapping

GitHub tickets do not have priority => label?

GitHub tickets do not have type => label?

GitHub tickets do not have version => ??

GitHub tickets do not have resolution => ??

Projects

GitHub has projects, it might be a good idea to use them.

[dustin]

From today's meeting:

• AGREED: will migrate only 0.9+ bugs, but with the proviso that we keep the old data accessible somewhere (djmitche, 16:45:54)
• AGREED: migrated issues are owned by bb-bot, with author information in the first comment (djmitche, 16:50:00)

[sa2ajj]

an update:

• got the stuff (everything in the filesystem)
• got the db dump (to play around)
• got the required eggs

next steps:

• get a local instance of trac
• play with it (see how API works)
• try to get a local instance of bb trac
• try to play with it to see how ticket API works...
• outline what needs to be on the GitHub side API

[sa2ajj]

description is updated with field information