Hi, This discussion sounds a little like RHEL (TG1) and Fedora (TG2).
Suggest you keep the existing TG1.x infrastructure on SVN. Split TG2 trac and repo out. Perhaps setup trac1.turbo... and trac2.turbo... for the different versions? trac.turbo... just points to trac1.turbo... Allows the bleeding edge types who want to experiment the full flexabilty of hg. Just my 2 cents. I don't spend much time on python or use CVS/SVN/hg in my day job to comment further. I enjoy the passion and excitement of this group and the ideals you are all trying to achieve. I loved being able to use TG trunk to construct an Operations Monitoring tool that has given us visibility into monthly batch processing runs that we never had before. The MVC in python and templating sure beats PERL anyday. At least I can go back to the python code and understand it... Keep up the good work on all fronts. Andrew. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
