Several of you alerted us that the dev site was down for a couple
weeks while I was on vacation.
We've had Trac database corruption before; assuming this is going to
happen again eventually, it no longer seems worthwhile to maintain the
Trac site. All the code lives on github anyway, so, we're going to
get rid of Trac and use Github for issues and wiki as well.
Here's where I need help:
If you have ever reported or commented on an issue to the Trac issue
tracker, can you please email me privately with your Trac login id and
your GitHub user name, if you have one? That way, I can properly
preserve history (there's a script for this).
I'll wait a few days to see if any of those trickle in; then I'll run
the issue migration script.
The wiki is already done - I've just finished migrating it. Please let
me know if you notice anything is missing or broken - or just fix it
yourself :)
On Mon, Aug 06, 2012 at 01:06:41PM -0400, Paul Winkler wrote:
> Here's where I need help:
> If you have ever reported or commented on an issue to the Trac issue
> tracker, can you please email me privately with your Trac login id and
> your GitHub user name, if you have one? That way, I can properly
> preserve history (there's a script for this).
... Never mind. I just realized the github API does not allow
specifying the reporter of an issue. It only allows setting the
assignee, which is not really helpful here.
I'll use another feature of the script which allows assigning labels
based on the trac issue reporter.
We recently migrated GeoNode from trac issues to GitHub and ran into
the same issue, but did find out that GitHub has a sort of 'beta'
program where you can create the issues as you would with the API, but
are able to set the reporter and just write the json files to disk ...
then package up the issues and email to them in an archive. They will
then import them and retain the reporter etc.
On Mon, Aug 6, 2012 at 5:06 PM, Paul Winkler <p...@openplans.org> wrote:
> On Mon, Aug 06, 2012 at 01:06:41PM -0400, Paul Winkler wrote:
>> Here's where I need help:
>> If you have ever reported or commented on an issue to the Trac issue
>> tracker, can you please email me privately with your Trac login id and
>> your GitHub user name, if you have one? That way, I can properly
>> preserve history (there's a script for this).
> ... Never mind. I just realized the github API does not allow
> specifying the reporter of an issue. It only allows setting the
> assignee, which is not really helpful here.
> I'll use another feature of the script which allows assigning labels
> based on the trac issue reporter.
> --
> You received this message because you are subscribed to the Google Groups "eb code" group.
> To post to this group, send email to ebcode@googlegroups.com.
> To unsubscribe from this group, send email to ebcode+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/ebcode?hl=en.
Just a very belated but hearty THANK YOU for keeping trac going this long and for taking the lead on migrating over to github. If OpenBlock had a benevolent dictator for life, you'd be the front-runner for sure. Thanks again, Ryan
On Monday, August 6, 2012 1:06:41 PM UTC-4, Paul Winkler wrote:
> Hi folks,
> Several of you alerted us that the dev site was down for a couple > weeks while I was on vacation.
> We've had Trac database corruption before; assuming this is going to > happen again eventually, it no longer seems worthwhile to maintain the > Trac site. All the code lives on github anyway, so, we're going to > get rid of Trac and use Github for issues and wiki as well.
> Here's where I need help:
> If you have ever reported or commented on an issue to the Trac issue > tracker, can you please email me privately with your Trac login id and > your GitHub user name, if you have one? That way, I can properly > preserve history (there's a script for this).
> I'll wait a few days to see if any of those trickle in; then I'll run > the issue migration script.
> The wiki is already done - I've just finished migrating it. Please let > me know if you notice anything is missing or broken - or just fix it > yourself :)
On Mon, Aug 06, 2012 at 05:15:41PM -0400, Jeffrey Johnson wrote:
> Paul,
> We recently migrated GeoNode from trac issues to GitHub and ran into
> the same issue, but did find out that GitHub has a sort of 'beta'
> program where you can create the issues as you would with the API, but
> are able to set the reporter and just write the json files to disk ...
> then package up the issues and email to them in an archive. They will
> then import them and retain the reporter etc.
> I will forward some info to you off-list.
> Jeff
> On Mon, Aug 6, 2012 at 5:06 PM, Paul Winkler <p...@openplans.org> wrote:
> > On Mon, Aug 06, 2012 at 01:06:41PM -0400, Paul Winkler wrote:
> >> Here's where I need help:
> >> If you have ever reported or commented on an issue to the Trac issue
> >> tracker, can you please email me privately with your Trac login id and
> >> your GitHub user name, if you have one? That way, I can properly
> >> preserve history (there's a script for this).
> > ... Never mind. I just realized the github API does not allow
> > specifying the reporter of an issue. It only allows setting the
> > assignee, which is not really helpful here.
> > I'll use another feature of the script which allows assigning labels
> > based on the trac issue reporter.
> > --
> > You received this message because you are subscribed to the Google Groups "eb code" group.
> > To post to this group, send email to ebcode@googlegroups.com.
> > To unsubscribe from this group, send email to ebcode+unsubscribe@googlegroups.com.
> > For more options, visit this group at http://groups.google.com/group/ebcode?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "eb code" group.
> To post to this group, send email to ebcode@googlegroups.com.
> To unsubscribe from this group, send email to ebcode+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/ebcode?hl=en.
Well. After I went and did all the work, Github turned off their bulk-import beta program. So I had to do it with the issues API after all.
I've finally moved all the trac issues to github. The wiki content was already moved.
As part of this move, I discovered that there were a bunch of existing ancient issues in the github tracker, from before we set up trac, but it's apparently impossible to remove them. This would totally screw up the issue numbers.
As a workaround, I created a new repository, renamed the old repository, then renamed the new repository. It has all the same branches, tags, wiki content, and allowed commiters, so it should function just the same as before.
The only thing that didn't get moved is pull requests. The existing ones are mostly requests from Tim Shedor with his excellent theme work for Larryville, which unfortunately I couldn't figure out a good way to use without just clobbering the existing default theme, and I didn't want to commit to that. Sorry Tim, I'd love to have found a good way to use that work.
On Monday, August 6, 2012 1:06:41 PM UTC-4, Paul Winkler wrote:
> Hi folks,
> Several of you alerted us that the dev site was down for a couple > weeks while I was on vacation.
> We've had Trac database corruption before; assuming this is going to > happen again eventually, it no longer seems worthwhile to maintain the > Trac site. All the code lives on github anyway, so, we're going to > get rid of Trac and use Github for issues and wiki as well.
> Here's where I need help:
> If you have ever reported or commented on an issue to the Trac issue > tracker, can you please email me privately with your Trac login id and > your GitHub user name, if you have one? That way, I can properly > preserve history (there's a script for this).
> I'll wait a few days to see if any of those trickle in; then I'll run > the issue migration script.
> The wiki is already done - I've just finished migrating it. Please let > me know if you notice anything is missing or broken - or just fix it > yourself :)
Oops, one consequence of this. Existing checkouts may have trouble pushing or pulling. If you have problems pulling or pushing updates in your existing checkout, here's what you can do, assuming you're currently on the master branch:
On Friday, September 28, 2012 5:06:00 PM UTC-4, Paul Winkler wrote:
> Well. After I went and did all the work, Github turned off their > bulk-import beta program. > So I had to do it with the issues API after all.
> I've finally moved all the trac issues to github. > The wiki content was already moved.
> As part of this move, I discovered that there were a bunch of existing > ancient issues in the github tracker, from before we set up trac, but > it's apparently impossible to remove them. This would totally screw > up the issue numbers.
> As a workaround, I created a new repository, renamed the old > repository, then renamed the new repository. > It has all the same branches, tags, wiki content, and allowed > commiters, so it should function just the same as before.
> The only thing that didn't get moved is pull requests. The existing > ones are mostly requests from Tim Shedor with his excellent theme work > for Larryville, which unfortunately I couldn't figure out a good way > to use without just clobbering the existing default theme, and I > didn't want to commit to that. Sorry Tim, I'd love to have found a > good way to use that work.
> On Monday, August 6, 2012 1:06:41 PM UTC-4, Paul Winkler wrote:
>> Hi folks,
>> Several of you alerted us that the dev site was down for a couple >> weeks while I was on vacation.
>> We've had Trac database corruption before; assuming this is going to >> happen again eventually, it no longer seems worthwhile to maintain the >> Trac site. All the code lives on github anyway, so, we're going to >> get rid of Trac and use Github for issues and wiki as well.
>> Here's where I need help:
>> If you have ever reported or commented on an issue to the Trac issue >> tracker, can you please email me privately with your Trac login id and >> your GitHub user name, if you have one? That way, I can properly >> preserve history (there's a script for this).
>> I'll wait a few days to see if any of those trickle in; then I'll run >> the issue migration script.
>> The wiki is already done - I've just finished migrating it. Please let >> me know if you notice anything is missing or broken - or just fix it >> yourself :)
