On Sat, Jun 7, 2008 at 11:48 AM, Rob Hudson <[EMAIL PROTECTED]> wrote: > I think the most often reason why I've heard is that it takes time to > create a release, post it, push security patches to it, etc. Which > makes sense, but at the same time there are a lot of valid points in > the blog post.
It does indeed take time to roll a release. More importantly, issuing a release means that we -- the Django team -- make a promise of support for it, which is the important part and the part that ultimately ends up eating much more time. It's also the part people tend to forget about when they start asking why we don't just roll a new release whenever they think we should. We've stated in the past that the next official supported release of Django will be 1.0. I think that's a good idea, and I personally think we ought to stick to it; the things we've outlined for 1.0 are significant enough that incrementally pushing releases before that will do more harm (in terms of presenting a constantly-moving target to the people who believe releases mean long-term stability) than good. And, really, that's the catch-22: if we released much more frequently than we do now we'd likely get just as many complaints, only from a different group of folks. As has been stated before, having people upgrade from 0.96 to a 0.97 release based on current trunk would subject those people to a fair number of required changes; having them upgrade at each step along the way to 1.0 would impose that on them repeatedly. That's not something I'd be comfortable with; I'd rather try to minimize the number of releases which involve significant end-user changes. The ideal is to just do it once, and then we're at 1.0 with a compatibility guarantee toward the future. So personally, I think discussion of more aggressive release schedules should happen once we're *at* 1.0, with a hard promise of stability. Once we're there, more frequent releases (say, to add new features or to expand django.contrib) make a whole lot more sense to me. But right now as we're working through the changes necessary to reach 1.0, I don't see much good in diverting that goal to produce interim packages that will, in turn, increase our support workload. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
