On Tue, Dec 8, 2009 at 5:59 AM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > Hi folks -- > > According to our timeline, we're at (a bit past, actually) the point > where we need to take a quick look at progress towards 1.2 and decide > whether the current timeline still makes sense. > > Right now, we've completed 4.5 features on the 1.2 priority list: > > * Comment admin actions (Contrib-10). > * Improved CSRF protection (Core-01). > * The first half(ish) of merging multidb (GSoC-05) > * QuerySet.exists() (ORM-10) > * Email backends (Email-01) > > Additionally, a few features are in or close to last-call stage > (multidb and the smarter if tag).
You can also add to this list: Serialization-01: Foreign keys in serializers. Templates-05: Template caching. I'm about to send out a messaging indicating my intention to commit these two in the near future. I think ORM-12 is also a possibility, but I haven't looked at the patch yet; that was next on my todo list. However, it isn't a huge feature (in terms of code impact), so IMHO even if it doesn't make it to the alpha, it's probably OK to include it in beta-1. I'd also like to get m2m signals (#5390); It isn't officially on the list for v1.2, but it was on the list for 1.1, and got bumped due to time. Again, this isn't a huge feature, so it can probably wait until beta-1. > Our current roadmap calls for large feature freeze on December 22nd, > and a complete freeze on January 26th. > > So the question is: given what we've got done, and guess at what we > will get done, is the current timeline still feasible, or should we > push the timeline? > > My opinion is that we should keep the schedule as-is. The features > we've got done so far aren't all huge and game-changing, but if we > released 1.2 with the features *as they stand right now*, it'd still > make a solid upgrade. If we can indeed get multidb merged, that'll be > a killer feature, but if it's not done I don't want to wait for it. > > Not ever release of Django needs to be a home run; I'd settle for a > base hit every time. I'm completely fine with the schedule as-is. The features we've committed might not all be huge, but CSRF and multi-db are big ticket items, and the remainder aren't slouches either. I'm sure I'm going to stuff up the baseball analogy, but this isn't a quick sneak into first - we've safely grabbed second. My only real regret on the schedule is that validation is going to get bumped - again - but I don't think it's worth pushing the schedule - again - in the hope that it will be included. Russ %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
