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 it's you, me, or someone else who pops in and says they're working tickets. Also, add a comment stating that you're working on it, in case it's an older one that was assigned to you. Basically, make sure we know it's actively being worked. For actual development work, well, git changes things slightly. Do any dev work on topical branch from the development branch, and we'll merge back to master when we get a release done. For 2.0, we don't have that luxury, so we'll just have to work off the branch-2.0 in git. On Sat, Mar 5, 2011 at 1:27 PM, Christoph Zwerschke <[email protected]> wrote: > Am 05.03.2011 17:37 schrieb Michael Pedersen: > > Since we'll be on the latest Trac version, we an use it as is while we >> clean up 1.1, 1.5, 2.0.4, and 2.1.1. After each release of each version, >> we can re-evaluate the current status. If we can move to Allure easily >> at that point, we set Trac to read only and move. If we're not able to >> easily move yet, we continue using Trac. >> >> What do you think? Is it worth the effort (I think it's even less effort >> than your current plan, personally), or would you prefer to make the >> switch now? >> > > My point is that if we start with a clean slate, there is nothing to *move* > i.e. we can start using Allura right now. It's probably not even desirable > to move all the closed tickets to Allura, even if that will be possible > later. Interesting for us are primarily the active tickets, and triaging > them and re-entering on Allura where necessary can easily be managed by us > in one or two weeks. Heck, I am willing to do this alone in one day if > nobody helps, just to end this drama. We need to screen the active tickets > anyway. After that, we can move the closed Trac tickets to a read-only > instance, just as an archive. Making it a read-only archive also has the > advantage that we don't need to set up and care about authentication, spam > protection etc. for the Trac. > > > -- Christoph > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/turbogears-trunk?hl=en. > > -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
