Although I normally encourage plenty of formalization, I don't think this is a good idea right now. Here's why: 1) The deadlines referred to in documentation are for a small team with money coming in. Django is a larger "team" (meaning lots of input from various interests) with no money as a direct result of their work. Don't hold them to the same expectations! 2) The contribution team is rather small and actually communicates a lot amongst themselves. Even if it is not all that clear what state we are in, I think they have a pretty good idea of things. 3) Merging magic-removal will destabalize the trunk for a while. Its hard to get accurate estimates from there. 4) There is already some planning on the wiki. Basically the only thing that is missing is number 2 from above - the release deadline date.
I see the desire you have for a concrete date to rely upon, but consider the cons of a deadline - quality is now a variable standard. I've seen plenty of projects pushed out with poor quality because of this, and deadline driven development leaves a bad taste in my mouth. Please lets wait a month or so and reevaluate this option. I think by then it will be much easier to get a solid handle on what should be in 1.0 and when would be a good date to aim for. -rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
