On Wed, Jun 11, 2008 at 9:13 PM, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > On Thu, Jun 12, 2008 at 10:03 AM, Jacob Kaplan-Moss > <[EMAIL PROTECTED]> wrote: >> >> ``django.contrib.comments`` still uses ``oldforms`` as well, but there's >> special situation here; see below. > > Jacob - unless I'm going blind, you've missed out the 'below' section > that this refers to.
You are not blind; I, however, have mad wicked copy-paste skillz. Ahem. On comments ----------- ``django.contrib.comments`` is a bit of special case here: ideally, Django 1.0 will ship with *no* core use of oldforms. However, refactoring the comment system -- not just replacing forms -- is overdue, and is the subject of a Summer of Code project. So we'd like to deal with that situation a bit specially. I've unfortunately not had a chance to ask Thejaswi (the student working on comments) or Jannis (his mentor) about this, so obviously they'll need to be OK with the idea. But, assuming this works, I'd like to do the following: August 11 is the suggested pencils down date for GSOC. This means that if Thejaswi is on track, he will be completed around the time of the beta 2 freeze date. July 14 is the midterm evaluation date for Summer of Code; we should be able to get a good idea then whether completion on schedule is likely. If the midterm evaluation says that the project is going badly, we abandon ship and paper over the problem by simply replacing the form components with newforms. If the midterm evaluation is positive -- which I expect it to be -- we work on the assumption that it will be merged around beta 2 (or earlier, if Thejaswi has something ready). We encourage people to push newforms-comments pretty hard, especially during sprints. If we get to August 11 and we don't have a newforms-comments release candidate, we can simply release with oldforms comments: it'll be annoying but not a deal-breaker. This does mean newforms-comments will be a late feature to the trunk (although only 3 weeks after the feature cutoff for other features), but if we encourage testing in its own branch, we should be able to mitigate the risk. I would also hope that the last 3 weeks of GSOC development would be mostly bugfixing anyway, rather than substantial changes. [With thanks to Russ -- the idea's originally his, and most of the above is coppied out of something he wrote yesterday.] Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
