On 11/8/05, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > What's the state of this branch? Last time I tried it out -- a few > weeks ago, IIRC -- there seemed to be a bunch more work to be done. > I'd obviously LOVE to see this get rolled in, but if it's a "few > months" thing I don't think it would hurt to let it hit in 1.1.
I'd like to see a solution to "core=True" before 1.0 -- i.e., not having to use that anymore. This goes beyond what new-admin offers, and it would probably be a backwards-incompatible change (hence the 1.0 requirement). > What do you think we ought to document? RSS and the comments > framework come to my mind; anything else? We should come up with a > list and work out who will write what. * RSS * Comments framework * Authentication (already started; I need to finish) * Admin-site documentation (already started on my laptop; I need to finish) * Views (already started on my laptop; I need to finish) * Finish tutorial * How to contribute to Django, and how development works * How to integrate third-party template systems I'd prefer to do all of these myself, with the exception of the last two. > These might be more difficult as they should ideally be taken *of* > 1.0 (not before), so they might need to be something we do after 1.0 > is done. Perhaps the best approach would be to make these when we > hit a 1.0 release candidate (after all the above is done). Good call. > * A solution to the "OR" dilemma; #251 seems like an OK fix to me. Yes, we should fix this one. #251 still rubbed me the wrong way last time I checked, but I'll give it some more thought. > * Solidifying the middleware API and the "stacking" issue (I've got a > draft proposal of this including an explanation of why I did it the > way I did; I'll try to wrap it up and post it soon). Looking forward to it... Adrian -- Adrian Holovaty holovaty.com | djangoproject.com | chicagocrime.org
