On Mon, Apr 19, 2010 at 11:05 AM, Dennis Kaarsemaker <den...@kaarsemaker.net> wrote: > I've been thinking of starting a proper contribution in django in a > similar way: a github repo with per-ticket branches that are trunk-ready > and regularly updated (rebased) against trunk until they are applied. > > So far I've only done so for a pony of mine as a test, but as soon as > the ash cloud clears, I will look at existing tickets. Would this > approach be useful for core committers to pull patches from?
If the quality's good, yes -- very much so. Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
