Hi Guys, 2.3.5 release is nearly finished, most of the targets I had in mind for 2.3.5 have been reached so the release is going to happen in a matter of days, as soon as I'm able to test it on a real world project and confirm everything works as expected (might actually delay if bugs are found :))
Next, after 2.3.5, bugfix releases might happen, but I'll focus on 2.4. 2.4 will target the TurboGears configuration system greatly improving it. While it worked for years is something is far from being clear and reliable. We inherited the Pylons config system and somehow adapted it to the requirements of TurboGears but it doesn't cope well with the needs of extensions and pluggables, it's not clear to most users how it works and worst of all is not idempotent, so building two apps from the same AppConfig might lead to different results. I decided to tackle the config system due to many feedbacks from users that had hard times doing even simple things like setting option values. So I'm writing here to gather additional feedbacks for 2.4 improvements. Apart from the config system, is there anything you feel requires simplification or improvements in TurboGears? Please avoid requesting features like: "I want facebook login support" which can be achieved by third party modules, I'm mostly speaking about framework core features and behaviours which all users face in their daily work! Let us know! The framework should move forward based on community needs and I'm just one member of its community who might miss many needs :) -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/d/optout.
