Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Tickets are moving to Github
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  4 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
aslak hellesoy  
View profile  
 More options May 18 2011, 5:25 pm
From: aslak hellesoy <aslak.helle...@gmail.com>
Date: Wed, 18 May 2011 22:25:45 +0100
Local: Wed, May 18 2011 5:25 pm
Subject: Tickets are moving to Github

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

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.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
aslak hellesoy  
View profile  
 More options May 18 2011, 5:40 pm
From: aslak hellesoy <aslak.helle...@gmail.com>
Date: Wed, 18 May 2011 22:40:20 +0100
Local: Wed, May 18 2011 5:40 pm
Subject: Re: Tickets are moving to Github

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

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

Lighthouse tickets that don't get reopened on Github can be considered dead.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John Firebaugh  
View profile  
 More options May 18 2011, 5:50 pm
From: John Firebaugh <john.fireba...@gmail.com>
Date: Wed, 18 May 2011 14:50:36 -0700 (PDT)
Local: Wed, May 18 2011 5:50 pm
Subject: Re: Tickets are moving to Github
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. :)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
aslak hellesoy  
View profile  
 More options May 18 2011, 5:55 pm
From: aslak hellesoy <aslak.helle...@gmail.com>
Date: Wed, 18 May 2011 22:55:42 +0100
Local: Wed, May 18 2011 5:55 pm
Subject: Re: [Cucumber:7924] Re: Tickets are moving to Github

On Wed, May 18, 2011 at 10:50 PM, John Firebaugh
<john.fireba...@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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »