On Wed, Oct 21, 2009 at 12:22 PM, mrts <mrts.py...@gmail.com> wrote: > A DVCS mm-tree > -------------- > > Quoting > http://en.wikipedia.org/wiki/Andrew_Morton_(computer_programmer) > > "He currently maintains a patchset known as the mm-tree, > which contains not yet sufficiently tested patches that > might later be accepted into the official Linux tree." > > I.e. there would be a DVCS branch (avoiding the f-word now) > maintained either by a core dev or a designated community > member that would accept patches more liberally -- but still > only patches that are up to Django standards, i.e. tests and > docs remain mandatory. > > This will probably be most effective in context of the bug > days, otherwise the management overhead may be too big. > > Also, that branch would have a few buildbots running tests > on it.
Another benefit of a merge-queue branch is testing and verifying that multiple patches play well together before actually hitting trunk. For multiple big branches this is even more important. -Rob --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
