First up: I've used the same tactics to migrated the devtools and docs repositories to sf.net. They're up and visible right now at https://sourceforge.net/p/pylonsproject/tg2/home/ so please check them over and see if the results work for you.
Caveats: The devtools repo has no tags for 2.0. There were none in the original bb repository either. The TG docs repository has no named branches as there were none. There was also no tg-2.0 docs, so there's just the repository. Those caveats aside, I'm liking the results. I can clone using git and Mercurial, and they work. Any feedback for potential problems would be very appreciated, though, so please, everybody who can, take a gander, and let me know of any problems. I'd like to close down the bb repositories within a week or so, so feedback matters. On Tue, Feb 1, 2011 at 12:26 PM, Christoph Zwerschke <[email protected]> wrote: > The more difficult part will be to get the Trac migrated. We need to > both update to the latest Trac version (or the latest one available at > SF) and to split up the trac into two tracs or a multi-repository trac > for TG1 and TG2. We could then remove the tickets for TG2 in the TG1 > trac and the tickets for TG2 in the TG2 trac with some SQL delete > commands. The problem is whether the trac installation on SF allows > manipulating or importing the database directly and also installation of > useful Trac plugins. Another solution would be to use trac for TG1 and > the SF tracker for TG2 if that is better. Well, since each project and sub-project can have its own tracker, I'm going to vote we find a way to split the two up. We'll probably have to make some custom export script that can be used to import the data onto the sf.net tracker. Not sure of the details beyond that, other than that we can expect some serious tweaking on the script. Hell, that one might be worth doing its own repository for until we can get it right. > If you like I can care about the SVN and Trac this week so you can > concentrate on the homepage (layout and content), download section, > integration of Blogs, News section etc. We also need to find a way to > publish the Sphinx docs at SF, so that they can easily be updated from > the repository. I will migrate the TG1 docs to Sphinx too, so we can use > the same publishing mechanism for that. Or, you can work on that script. I like that idea ;) Seriously, once we can get soem info on what we can do for that, I'll be happy to help. Now, in the meantime, I guess it's time for me to look at the homepage for the projects, and see what I can figure out. Hopefully, it's possible to do more than what I can find so far. The sub-project looks to be somewhat on the limited side right now. -- 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.
