Tickets are moving to Github

[aslak hellesoy]

Last week Cucumber moved from http://github.com/aslakhellesoy/cucumber to http://github.com/cucumber/cucumber

This week tickets are moving from https://rspec.lighthouseapp.com/projects/16211-cucumber/tickets to https://github.com/cucumber/cucumber/issues

After discussing with Matt Wynne we decided not to automate the migration from Lighthouse to Github. The main reason is that we cannot create Github tickets on behalf of other people, and maintaining proper markup (and authorship) of ticket threads is also somewhat tricky. Instead we'll rely on the community to pick the tickets they care about and create Github tickets pointing to the original one on Lighthouse so we can go there and read old discussions. Here is what you need to do to keep a ticket alive:

1) Create a ticket on https://github.com/cucumber/cucumber/issues with a title that is identical to the original Lighthouse ticket's title. On the first line of the ticket body, add a link to the original Lighthouse ticket in Markdown - for example:

        [Original Lighthouse Ticket 165](https://rspec.lighthouseapp.com/projects/16211/tickets/165-error-when-not-caching-classes)

2) In the old Lighthouse ticket - add a link to the new Github ticket so other people don't accidentally create dupes.

Lighthouse tickets that don't get reopened on Github can be considered dead. Now I'm going to run a script that will close *all* tickets on Lighthouse and add a little comment that points to this message.

Thanks for your help,

Aslak and the cuke team.

[aslak hellesoy]

On Wed, May 18, 2011 at 10:25 PM, aslak hellesoy <aslak.h...@gmail.com> wrote:

Last week Cucumber moved from http://github.com/aslakhellesoy/cucumber to http://github.com/cucumber/cucumber

This week tickets are moving from https://rspec.lighthouseapp.com/projects/16211-cucumber/tickets to https://github.com/cucumber/cucumber/issues

After discussing with Matt Wynne we decided not to automate the migration from Lighthouse to Github. The main reason is that we cannot create Github tickets on behalf of other people, and maintaining proper markup (and authorship) of ticket threads is also somewhat tricky. Instead we'll rely on the community to pick the tickets they care about and create Github tickets pointing to the original one on Lighthouse so we can go there and read old discussions. Here is what you need to do to keep a ticket alive:

1) Create a ticket on https://github.com/cucumber/cucumber/issues with a title that is identical to the original Lighthouse ticket's title. On the first line of the ticket body, add a link to the original Lighthouse ticket in Markdown - for example:

        [Original Lighthouse Ticket 165](https://rspec.lighthouseapp.com/projects/16211/tickets/165-error-when-not-caching-classes)

2) In the old Lighthouse ticket - add a link to the new Github ticket so other people don't accidentally create dupes.

In fact - skip step 2) folks.

I went ahead and marked the old Lighthouse tracker as read-only to prevent people from accidentally adding new tickets there or continuing discussions.

I don't think dupes on Github will be a big issue as long as people use the same ticket titles as the original and look around on Github before moving tickets over.

Aslak

[John Firebaugh]

On May 18, 2:40 pm, aslak hellesoy <aslak.helle...@gmail.com> wrote:
> I went ahead and marked the old Lighthouse tracker as read-only to prevent
> people from accidentally adding new tickets there or continuing discussions.

Unfortunately, this prevents non-admins from even accessing the old
tickets.

E.g., all I see when I try to view one of my tickets is:

Oops! : This is not a public project
If you think this is an error, please contact one of the
administrators
of this site. You can also log in with another profile.

This makes it difficult to transfer said ticket to github. :)

[aslak hellesoy]

On Wed, May 18, 2011 at 10:50 PM, John Firebaugh <john.fi...@gmail.com> wrote:

On May 18, 2:40 pm, aslak hellesoy <aslak.helle...@gmail.com> wrote:
> I went ahead and marked the old Lighthouse tracker as read-only to prevent
> people from accidentally adding new tickets there or continuing discussions.

Unfortunately, this prevents non-admins from even accessing the old
tickets.

That's a shame. I have unarchived it now, so feel free to follow step 2) anyway :-)

Aslak

 

E.g., all I see when I try to view one of my tickets is:

   Oops! : This is not a public project
   If you think this is an error, please contact one of the
administrators
   of this site. You can also log in with another profile.

This makes it difficult to transfer said ticket to github. :)

--
You received this message because you are subscribed to the Google Groups "Cukes" group.
To post to this group, send email to cu...@googlegroups.com.
To unsubscribe from this group, send email to cukes+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/cukes?hl=en.