[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