I'd just like to support these comments as well. moving stuff now to M-R is a bitch, but doable... there are a lot of changes there.
at the moment it is easier for me to upgrade my stuff to django M-R, compared to switching to pylons or TurboGears.. if you change to much more than it is probably easier for people like me to start from scratch again (and re-evaluate the Django decision) I'd say get DB layer and the new model syntax fixed and solid, merge that to the trunk and then work on the validation. --Ian On 3/9/06, Christopher Lenz <[EMAIL PROTECTED]> wrote: > > Am 08.03.2006 um 21:06 schrieb Tom Tobin: > > On 3/8/06, Christopher Lenz <[EMAIL PROTECTED]> wrote: > >> The patch reverts some changes (such as the removal of core fields) > >> which were never really completed. While I'm aware that a much > >> improved version of edit_inline is on the way (using Dojo/AJAX and > >> all that), I think that the branch should be merged back into trunk > >> before that work is finished, i.e. that that stuff happens on a new > >> branch after magic-removal has been merged. > > > > While I'm a *huge* advocate of getting MR wrapped up and merged before > > it achieves sentience and takes over half the Internet, I'd rather > > have any breakage happen here and now rather than post-merge. I hate > > to say it, but a feature-freeze date for MR may be in order: if > > something backwards-incompatible hasn't been proposed and agreed upon > > before then, it doesn't go (and gets postponed to trunk, perhaps for > > post-1.0), and everything post-freeze is pure implementation and > > bugfixes. > > There's the danger of a branch that never merges, because it has too > many issues to get enough exposure with users (and in turn doesn't > get enough exposure to enable all the issues to get discovered and > fixed). > > I'm all for a feature-freeze for MR: IMHO the remaining bugs should > be fixed, and the contrib apps (such as comments) updated to the new > API, but *before* there's any more major refactorings. Make another > minor release, and push -- for example -- validation-aware models and > a Dojo-enhanced admin to the next minor pre-1.0 release. > > Release often, release early. > > Cheers, > Chris > -- > Christopher Lenz > cmlenz at gmx.de > http://www.cmlenz.net/ > > > > -- [EMAIL PROTECTED] -- blog: http://feh.holsman.net/ -- PH: ++61-3-9877-0909 If everything seems under control, you're not going fast enough. - Mario Andretti --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
