> > > Since we never had a list of features that we were committing to adding
> for 1.4, I don't see any reason why we can't release an alpha as soon as > > the release blockers are dealt with. <https://docs.djangoproject.com/en/dev/releases/1.4/>Agreed. There will > always be extra features that we can add (app > refactor, anyone?) but I think we're well past the point where an > alpha is called for. Great stuff people, super exciting! I don't know how quickly the alpha might be do-able, but from my point of view it'd be good if there's a little bit of notice to give devs a chance to close off any new feature tickets they might be working on prior to the feature-freeze deadline. Got at least a couple in mind (eg. defiantly 17193<https://code.djangoproject.com/ticket/17193>, and perhaps 2879 <https://code.djangoproject.com/ticket/2879>) that I'd like to see get to RFC if possible, but it'd be useful to know how much or little headroom I'd have before 1.4. Might make sense to fix a planned alpha date? Tom -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/vXVQZi1aJSEJ. To post to this group, send email to django-developers@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.
