On 28/11/11 20:33, Adrian Holovaty wrote: > And that someone will be me. See my post here: > http://www.holovaty.com/writing/back-to-django/
Great stuff! > I plan on starting this next week. Is there a list somewhere of what > needs to get done? If not, I can make it, but obviously it'd be great > if that already existed. 1) Release blockers: https://code.djangoproject.com/query?status=!closed&severity=Release+blocker&order=priority 2) Broken tests: http://ci.djangoproject.com/builds It looks like tests are failing on Oracle and spatialite. I guess any failing tests need to be added to the release blockers. 3) We don't have a fully documented release process. It seems that only James Bennett knows exactly what our release process is. Ideally we would get this not only fully documented but fully automated, perhaps even with the script checked in to trunk so that any of the core developers can do a release - whether for alpha/beta/RC/final. There was a bunch of triage work to do with unreviewed tickets, but Aymeric polished most of it off recently. 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. I think we've ended up with a fairly nice set of improvements despite the lack of explicit direction. https://docs.djangoproject.com/en/dev/releases/1.4/ Regarding the great Python 3 work that Vinay has done, I think this should be deferred until after the 1.4 release, which will give the core devs time to get up to speed with how things are going to work going forward. Regards, Luke -- Noise proves nothing. Often a hen who has merely laid an egg cackles as if she laid an asteroid. -- Mark Twain Luke Plant || http://lukeplant.me.uk/ -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
