Migrating to Github Issues

[Will Coleda]

On Wed, Oct 19, 2011 at 3:29 PM, Jonathan "Duke" Leto <jonathan at leto.net> wrote:
> 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.

Long standing nit of mine, but old doesn't a priori mean irrelevant.
When in doubt, leave it alone (there are plenty of other tickets!), or
ask on #parrot.

Any outstanding patches that don't apply to the current code base can
be regretfully and safely rejected.

Any build problems not of a recent vintage can probably be closed,
with an encouraging word for people to submit to gh any new issues.

> 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.

I would tend to avoid doing manual migration if we're just moving the
ticket (See Andy's followup); I did see that for the several tickets
Duke moved today, the new ticket has more/different detail, and isn't
just a "see this other ticket", so that's fine. It's basically a new
ticket, with a link for historical notes.

One of the reasons to keep things as automated as possible is to track
things like the original poster, so that when we do have updates, they
are kept in the loop automatically. This was something that I think we
tried to do with the manual migration to trac, by setting the
"reporter" field, but I'm sure some of this was dropped on the floor
in that migration.

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

Done. I had one open ticket that actually should have been closed.

> 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.
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>



-- 
Will "Coke" Coleda