On Nov 28, 4:40 am, Russell Keith-Magee <russ...@keith-magee.com> wrote:
> Any practical suggestions on how we can improve on this situation will > be gratefully accepted. Core has grown, but it seems to me there is a fair amount of cultural and procedural knowledge that more veteran core members have not yet transferred, due to understandable lack of personal bandwidth. Being able to commit to Django-the-codebase does not confer the same knowledge required to cut a release of Django-the-project. Perhaps if James Bennet could do a brain dump, in outline form, of the procedural steps of release on a wiki page to augment the more public focused: https://docs.djangoproject.com/en/dev/internals/release-process/ Determine if there is someone newer to core (or unfamiliar with the release process) who is interested in being mentored in the process. Open a call for current core devs to comment on what in-progress features they want to champion into 1.4 and get a rough self imposed due date. If those cluster nicely, use a soft average of those dates as the target release date for the alpha. Explicitly determine which core-dev will take ownership of which remaining release blockers. I have a few tickets I have in progress, and all I can do from my position, is do my best to prioritize them, and get the top ones wrapped up, rather than have all remain uncompleted. -Preston -- 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.
