Am 21.02.2006 um 22:58 schrieb Jacob Kaplan-Moss: > I, for one, want to get m-r wrapped up and merged back to trunk as > soon as humanely possible. I feel like it's starting to be a drag on > new users trying to figure out why development on trunk seems to have > stopped, and I want to get us all back to one codebase.
I agree 100% with that goal... but I'm curious on how you want to get there. In its current state, magic-removal is severely broken in many significant ways. Don't get me wrong, I'm a big fan of the general direction of the branch... the "magic modules" part of Django was really a turnoff for me before. To an outsider like myself, it looks like there's been a rush towards a major refactoring that (pretty much) stopped somewhere along half the way, leaving quite a number of those features that make Django such a great framework non-functional. And there's no documentation (and only sparse archived discussion) about how the currently broken functionality should be fixed... otherwise I'd have contributed a good share of patches by now. IMHO, what the Django community needs at this point is for someone in the know to update the RemovingTheMagic page, and add meat to the "What's not done yet" section. Limit the scope of the branch, point out what areas need fixing and how those are supposed to be approached. I'm sure the "masterplan" is somewhere in the heads of the developers, but it needs to be communicated to users and potential contributors if we are to test and contribute to the branch. Cheers, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
