#171 Move out of Lighhouse

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#171 open

Move out of Lighhouse

Reported by Daniele Varrazzo | July 13th, 2013 @ 09:37 AM

Lighthouse has been useful but the experience has not been without problems:

service problems
weird model (no mark as duplicate, just for one that would have been useful yesterday)
spam

recently we moved the repos to github. Not using github bug tracker we are missing:

integration with the source code
a more familiar tool to have bugs reported.

So I think it's time to say thank you to Lighthouse and move away. What I don't want to lose is the history here. Definitely I don't want overlap with the bug numbers. There are two possibility.

a. find a way to use Lighthouse and GitHub APIs and move the bugs and the comments there, matching the numbers. Currently up to 7 are used on GitHub by pull requests (which share the same bug counter with the bugs)

b. don't be OCD and "consume" bug numbers on github with placeholders, then leave these Lighthouse read-only somehow.

Comments and changes to this ticket

Federico Di Gregorio July 15th, 2013 @ 08:54 AM
We can transfer the bugs from Lighthouse to GitHub and just forget about the numbers. If possible we could add a final comment to every lighthouse bug with a link to its GitHub counterpart.
Daniele Varrazzo July 19th, 2013 @ 02:00 PM
Chris, I'm not working on this, I don't think I'll do anything about it in these days.

If you want to try working at it I'd be very grateful.

It would be great to manage to import both the issue body and the comments. But the bodies only and a link to the original thread would be a good start anyway.

In order to keep the numbers paired without too much trouble we could just import only the issues after the #7 (or whatever will be the last github issue by that time).
Daniele Varrazzo August 22nd, 2014 @ 04:09 AM
- Assigned user set to “Daniele Varrazzo”

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<b>WARNING:</b> the informations in this tracker are archived. Please submit new tickets or comments to <a href="https://github.com/psycopg/psycopg2/issues">the new tracker</a>.
<br/>
Psycopg is the most used PostgreSQL adapter for the Python programming language. At the core it fully implements the Python DB API 2.0 specifications. Several extensions allow access to many of the features offered by PostgreSQL.