On Sat, Jun 7, 2008 at 12:06 PM, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > * Start a "train release" schedule: schedule a couple of 1.0 betas, a > rc or two, and then a final release. Features that are done by the > dates get released, those that aren't, don't. Make these dates > aggressive but not crazy. And -- here's the controversial part -- make > newforms-admin an "optional" part. If it's done, awesome; if not, > include it in the next release. The current admin has some bugs, yes, > but it's usable enough. As long as we advertised that it's on the way > out we shouldn't have too much trouble.
This is similar to the Ubuntu release schedule -- release every 6 months and whatever is done/stable at the time makes it, otherwise things wait for the next release (which isn't too far out). +1 from me, and it provides for a little motivation since there is a target date on the horizon. -Rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---