Migrating to Github Issues
Jonathan "Duke" Leto
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 <jona...@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
Andy Lester
We are planning to migrate TT's to Github issues,
Will Coleda
> 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 <jona...@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
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
Kevin Polulak
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.
I think this is a really great idea. I know this has been talked about in passing for quite a while so it's good to see things start rolling. I'll do my part in the migration this weekend.
Perhaps this would make a good project for a GCI student?
--
- Kevin Polulak (soh_cah_toa)
Andy Lester
I think this is a really great idea. I know this has been talked about in passing for quite a while so it's good to see things start rolling. I'll do my part in the migration this weekend.
Perhaps this would make a good project for a GCI student?
Will Coleda
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>
>
Are you offering to look at tickets manually? Dive right in, I think
dukeleto had already said.
Are you offering to write code to do the transition programatically? I
haven't seen anyone else say that (only that they'done similar things
in the past.)
I for one would prefer a non-manual approach, as I've said before.
Are you asking for permission? volunteers? direction?
Andy Lester
Are you offering to write code to do the transition programatically? I
haven't seen anyone else say that (only that they'done similar things
in the past.)
Will Coleda
I hope you get volunteers, but either way, thanks for taking this on!
Jonathan "Duke" Leto
Thanks for taking the helm on this Andy!
I think many people have cleaned out many tickets, but I still see Trac tickets
closing. I know that I have not had enough time to go through all of mine yet.
I will do my best but I will be at 2 confs in the next 5 days (GSoC
Mentor Summit and Git Together 2011) so I won't have many tuits in the
next week.
Do you think you can start prototyping a solution for an automatic migration? I
am thinking of something that you can actually test on a throwaway repo on
Github, so you can try to, for example, convert 10 Trac tickets to Issues and
see how the conversion works.
If it takes another 2 weeks to get a conversion script perfected, that should
be enough time for people to finish closing Trac tickets.
One additional complication is that some TT's would be better placed in repos
other than parrot.git (such as parrot-embed.git), but we can nuke that
bridge when
we come to it.
Again, thanks Andy!
Duke
--
Andy Lester
> am thinking of something that you can actually test on a throwaway repo on
> Github, so you can try to, for example, convert 10 Trac tickets to Issues and
> see how the conversion works.
Oh, sure, NOW come the implementation suggestions! :-)
Yes, what you have suggested is exactly my plan, except I wasn't going to limit it to 10. The more data we put in a throwaway repo, the better.
It'll be a while, I'm sure. I haven't even started sniffing around for pre-existing Trac->Github solutions.
xoxo,
Andy
--
Andy Lester => an...@petdance.com => www.petdance.com => AIM:petdance
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
Jonathan "Duke" Leto
Net::Github + Net::Trac (as suggested by plobsing++) look like good
places to start.
Duke
On Thu, Oct 20, 2011 at 9:13 PM, Andy Lester <an...@petdance.com> wrote:
>> Do you think you can start prototyping a solution for an automatic migration? I
>> am thinking of something that you can actually test on a throwaway repo on
>> Github, so you can try to, for example, convert 10 Trac tickets to Issues and
>> see how the conversion works.
>
> Oh, sure, NOW come the implementation suggestions! :-)
>
> Yes, what you have suggested is exactly my plan, except I wasn't going to limit it to 10. The more data we put in a throwaway repo, the better.
>
> It'll be a while, I'm sure. I haven't even started sniffing around for pre-existing Trac->Github solutions.
>
> xoxo,
> Andy
>
>
> --
> Andy Lester => an...@petdance.com => www.petdance.com => AIM:petdance
>
>
--
Kevin Polulak
Andy Lester
Net::Github + Net::Trac (as suggested by plobsing++) look like good
places to start.