On 11/30/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > Let's get a definitive list of features we want in Django 1.0, and > let's release it.
Sounds great to me :) > What am I forgetting? I'd add model subclassing to the list, if only because it feels as if the API has been mostly agreed upon at this point, and a whole lot of documentation updates/additions and possibly refactoring (there's plenty of room for post-1.0 improvement, of course, but there are also a lot of things we should document if we're going to commit to maintaining compatibility). > My second reason for choosing 2.0 is, shall we say, less wholesome. > After having endured a 2.5+ year deluge of "When is 1.0 coming out?" > blog entries, comments, e-mails and in-person confrontations from > people all around the world, I would find it incredibly satisfying, in > a devilish way, to release this thing and slap a "2.0" on it. It would > underscore the project's stability while at the same time > demonstrating that version numbers are completely arbitrary. I'd be OK with it; in my previous life as a PHP guy I worked a lot with Textpattern, which went through a multi-year development process and then decided to call the result "version 4.0" ;) -- "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 -~----------~----~----~----~------~----~------~--~---
