> Here's my vote: > > 1) Create a new package with a new name. > 2) use that package with the new name by default in tg 2.1 > > continue to use TurboJson in tg 2.0 and 1.x and allow 2.1 to use > TurboJson for backwards compatability if people want.
+1 Whatever you do Jorge, please think about tg 1.x users. This means TurboJson should not evolve in a way that suddenly it stops supporting tg 1.x or get into a state where "tg 1.x compatibility can now be added back". It's fine to come up with cool new features for tg 2.0 or tg 2.1 but if this implies lost support for tg 1.x then this new code should be given a new name and correspondingly a new package. Cheers, Daniel -- Psss, psss, put it down! - http://www.cafepress.com/putitdown --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to turbogears-trunk@googlegroups.com To unsubscribe from this group, send email to turbogears-trunk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
