On Sat, Jun 7, 2008 at 2: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.
vote(-(sys.maxint)) Newforms-admin needs to get done. Putting it off from the first couple betas or RCs will just increase the temptation to put it off further, so what we should do is identify anything that's slowing it down and work to resolve that. If that means organizing a sprint or two on it and then doing a trunk merge to get more eyeballs on the code, then let's do that instead. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
