Am 24.10.2010 15:57 schrieb Jan Koprowski:
I was supprised thinks like this happen in Turbo Gears because this looks like TG doesn't have adequate set of tests which allow avoid this kind of problems. Am I correct this issue is caused because of week code coverage?
I think the main problem is that TG2 is dependent of so many different libraries some of which are moving targets. So simply running the test suite is not enough, it must be actually done in different environments with different Python, Pylons, WebOb etc. versions. For instance, the recent problems seem to be causeed by the differences between Pylons 0.9.7, 0.10 and 1.0.
Therefore, I think what the TG project desparetly needs is an official continuous integration server where TG is tested in different environments. Ideally there should be also performance benchmarks so we can not only see if things stop working, but also if performance starts degrading.
My hope is that this can be solved together with the planned move to a different development infrastructure at SourceForge.
Apart from that, to make our lifes easier, my suggestion is to make stricter requirements like only supporting Pylons 1.0 in TG 2.1.
-- Christoph -- You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en.
