I'm +1 for both of those. But I'll postpone them at 2.2 as suggested by Christoph and I reaaaaally don't want to see anymore my app depending from 6 packages just to make auth work. After 2.1.4 I think we should freeze and start thinking at 2.2
I think that they are too big changes for 2.1.4 and I would like to release 2.1.4 this month. I really need help from a mako user by the way, because there are some pending tickets which are mako related and I don't use mako at all so I'm not the best person to solve them. My personal targets are: * 2.1.4 - Create a good and reliable hooks system for tg to make plugins easy to inject (should be already there on the dev branch) - Make fastest and easier to use tgext.admin and tgext.crud. (EasyCrudRestController is a step in the right direction, I recently been able to write a full small application without writing one single controller method using only tgext.crud and I realized some minor improvements that it might need but not many) - Ming hooks system (Sent a patch to Rick, waiting for him to approve this) - Release tgext.debugbar as an external dependency that people can start using (requires the hooks in tg and ming) - Improve sprox and tgext.admin ming support * Between 2.1.4 and 2.2 - Release tgext.pluggableapps to mount complete ready to use applications like django apps using the 2.1.4 hooks system - Improve the website, hell we don't even have a news box on the website and still the tgext.pages crashes every time I try to save an edit * 2.2 - Integrate tgext.debugbar and tgext.pluggableapps inside the standard quickstart - WebOb1.2 support - Make tw2 the default option? We still quickstart on tw1 while tw2 is at least as much stable and more maintained. - Trash away most of the repoze.who/what dependencies - Find a decent solution to dependencies management. On Fri, Nov 18, 2011 at 9:06 PM, Michael Pedersen <[email protected]> wrote: > After doing the release for 2.1.3, and reading some of what's going on in > the word of our packages, I think I'm looking at a couple of growing > problems for TG2. One of these I wanted to bring up earlier, but the other > only really hit me today as something we should consider. > First up: Python 2.4. I've said it in the past few months, but it's starting > to look like we must address this sooner rather than later. Other projects > are dropping support for it (for instance, WebOb, as of 1.1b1, has dropped > support). I'm even willing to mark the next release as 2.2 just so we can > drop 2.4 support entirely, and make our minimum either 2.5 or 2.6 (I'd like > it to be 2.6 personally, so that we don't have to reach a similar point in > another year or two). What does everybody else say? > Second up: repoze.who is at 2.0. With our current set up, we are locked in > at the 1.x series. I'd like to find a way to bring 2.0 support in so that it > works easily for people. We can make it so that it is not required (similar > to how TW1 and TW2 are both options), but I definitely want to get all of > our packages upgraded to support the latest of everything. This way, we > reduce some of the issues we've had where people are managing to get > incompatible versions of packages (WebOb in particular). > Finally, I'd like to push the next release back to the Christmas release. > We'll get Alessandro's debugbar added in, we'll get the above features added > in, we'll clean up the current warnings we see when running the tests, and > then we'll cut that as our next release. > What do you all think? > > -- > 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. > -- 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.
