On 8/11/06, James Bennett <[EMAIL PROTECTED]> wrote: > Since I just lost about an hour of my life to dealing with a problem > in pre-m-r Django which had a fix in Trac that was never applied > (ticket #1113 for those who are interested), I'm suddenly intensely > curious about the possibility of this happening. > > Would it be prohibitively difficult for some of us to scour Trac > sometime for known bugs and patches in which came between 0.91 and the > pre-magic-removal tag, and work on rollin a release out of that?
As long as it's strictly bug fixes, and no feature additions, that sounds fine by me. The reason I say "no feature additions" is that it wouldn't be in our best interest to have another competing branch, as we did with magic-removal vs. 0.91 a while back. Granted, I think people overwhelmingly agree that there's really no reason to continue using pre-magic-removal Django except for legacy reasons, so there's not much incentive to add feature additions to this branch in the first place -- but I figured it was worth pointing out. James, assuming you agree with these goals, are you volunteering to maintain the branch? :-) Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
