On Nov 10, 2007 10:01 PM, ToddG <[EMAIL PROTECTED]> wrote: > I don't think (at least hope) that people in general are slighting the > amount of effort that goes into a release -- a big recurring theme > seems to be though that what you keep graciously going to great > lengths to repeat here isn't publicly posted in an idiot-proof manner > on the site or wiki or anywhere (at least obvious enough that everyone > can find it, including myself). Also since 'Roadmaps' is disabled in > Trac, that usual place to look for a general overview is missing as > well.
While I agree that, in general, we can do a much better job of explaining where Django is going, I'm never entirely certain of what the best method is right at the moment, and there are several factors which make it difficult right now. For example, Django's currently pre-1.0 software, which means that -- even though most of the framework is extremely stable -- we're still working on nailing down APIs and internals to get to something we can commit to maintaining for a while once we have a 1.0 release (and there is a document outlining APIs that we're happy with and that people can safely rely on[1]). Being pre-1.0 also means that Django really doesn't have a formalized release process yet; right now the goal is to get all the APIs stable and finish all the features we need to have before calling it "1.0". Most of that's easy to glean from existing documentation or from casual skimming of the development timeline and the developers' mailing list, but it complicates the process of trying to forecast releases; once we're at 1.0 it'll be much easier to lay out a road map for future features and changes (and, in fact, we'll have to do that). Finally, the fact that Django is an all-volunteer project with no direct funding or corporate support makes it difficult to get somebody assigned to maintaining documentation on the state of Django and plans for future releases (in theory that's my job as release manager, but all that means is that I know how tricky that can be). So right now it's kind of difficult to say much, aside from "we're heading for 1.0, and here's what's stable"; in the future I do want to have more detailed documentation of Django development, but for now the combination of Django's pre-1.0 state and the need to prioritize work on Django itself over documenting Django's development makes it tricky to offer much more. That said, suggestions (and, even better, offers of time and effort from people who can sit down and work on this) are always appreciated :) [1] http://www.djangoproject.com/documentation/api_stability/ -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
