Re: [tg-trunk] Another suggestion for the Trac migration

2011-03-07 Thread Christoph Zwerschke
Am 07.03.2011 02:15 schrieb Mark Ramm: I have no objections to this approach. As for the TG2 as sf.net location, I'm partial to /p/turbogears2/ but can be persuaded by somebody with a strong argument/ Ok, so let's follow that plan now. I'm also for using turbogears1 and turbogears2 as

Re: [tg-trunk] Another suggestion for the Trac migration

2011-03-07 Thread Alessandro Molina
On Mon, Mar 7, 2011 at 10:34 AM, Christoph Zwerschke c...@online.de wrote: Am 07.03.2011 02:15 schrieb Mark Ramm: I have no objections to this approach. As for the TG2 as sf.net location, I'm partial to /p/turbogears2/ but can be persuaded by somebody with a strong argument/ Ok, so let's

Re: [tg-trunk] Another suggestion for the Trac migration

2011-03-07 Thread Michael Pedersen
I've been doing a mix of get this code done for this ticket and close this ticket. Right now, I'm stuck on a failing test. I'll work on getting the TG2 tracker configured on SF tonight, so that we should be able to migrate starting tomorrow. I got basics done last night, but there's definitely

Re: [tg-trunk] Another suggestion for the Trac migration

2011-03-06 Thread Christoph Zwerschke
Am 05.03.2011 19:43 schrieb Michael Pedersen: I'm not about to leave you alone for it. I'll help. I'll start looking at the 2.x tickets tonight. Does that mean you agree with me that we should start on SF with a clean plate? We could then create these new Allura trackers for TG1 and TG2

Re: [tg-trunk] Another suggestion for the Trac migration

2011-03-06 Thread Ken Kuhlman
On Sun, Mar 6, 2011 at 3:21 PM, Christoph Zwerschke c...@online.de wrote: I did not hear opinions from anybody else, though. So if anybody has objections, please raise them *now* and don't complain later! Sounds like a reasonable approach to me. I can help move the open 1.x tickets over

[tg-trunk] Another suggestion for the Trac migration

2011-03-05 Thread Christoph Zwerschke
As already posted, one of the things that is hampering us for too long already is the migration of our old Trac. We actually wanted to move to SF to minimize the admin work, but it turned out to make more work as expected, and I'm still doubt how faithful/useful the migrated tickets and

Re: [tg-trunk] Another suggestion for the Trac migration

2011-03-05 Thread Christoph Zwerschke
Am 05.03.2011 13:19 schrieb Christoph Zwerschke: * simple - do it immediately and close * more complex - manually enter them in Allura and close in Trac * irrelevant, outdated, not reproducable etc. - just close In the last category, we could already clarify the tickets, add ideas for solutions

Re: [tg-trunk] Another suggestion for the Trac migration

2011-03-05 Thread Michael Pedersen
I'm actually leaning towards a slightly different approach, but am not invested in it. What I was thinking of doing is simply migrating Trac to the latest and greatest on the new server. We'll execute the switchover to the new server before March 14, and have everything directed there. Since

Re: [tg-trunk] Another suggestion for the Trac migration

2011-03-05 Thread Michael Pedersen
I'm not about to leave you alone for it. I'll help. I'll start looking at the 2.x tickets tonight. Since we're going to go after this actively, I'm going to suggest we assign tickets to ourselves as soon as we start looking at them, regardless of who they are currently assigned to. Well, unless