Migrating to Github Issues

[Jonathan "Duke" Leto]

Howdy,

As far as I can tell, a vote in #ps yesterday cemented the decision to migrate
to Github issues. This will be a multi-step process.

If you have a Trac account, please log in and go through the tickets that are
assigned to you.

Close any that are no longer relevant. If a ticket hasn't been touched in over
a year, it is probably no longer relevant. Use your best judgment.

We are planning to migrate TT's to Github issues, but we want to close as many
as we can in Trac, so we don't create more work for ourselves.

In a good faith effort, I closed or manually migrated many of my own
TT's this morning.

If each Parrot dev cleans out their assigned TT's, this process will
happen faster
and be distributed.

If you want help getting a free Github account so you can create issues, please
let me know off-list.  I am looking at your, doughera++ :)

If you are new to the Parrot community and want to help with this
task, but you don't
quite know how to help, respond to this email and somebody will set
you in the right
direction.

Duke

-- 
Jonathan "Duke" Leto <jonathan at leto.net>
Leto Labs LLC
209.691.DUKE // http://labs.leto.net
NOTE: Personal email is only checked twice a day at 10am/2pm PST,
please call/text for time-sensitive matters.