On Saturday, April 28, 2012 12:46:53 PM UTC-7, Yuval Adam wrote: > > I think this issue should be dealt with sooner rather than later. > > Django will start getting lots of orphan pull requests with no > matching trac ticket, and a policy of how community members should > contribute via github should be in place. > > As a side note, it is kind of a hassle to submit a pull request and > then go fill a new trac ticket. > For me, as a kind-of-involved user of Django, I simply won't go into > that burden.
It is a small hassle, but I've done it several times (creating a pull and ticket with cross referencing links). Writing tests can sometimes feel like a hassle. Hopefully we will see some solutions and improvements in the trac-github space, but in the meantime - it shouldn't be a barrier to contributing - a few more clicks is all. -P > On Apr 28, 10:03 am, Aymeric Augustin > <aymeric.augus...@polytechnique.org> wrote: > > On 28 avr. 2012, at 05:08, Adrian Holovaty wrote: > > > > > * We're going to keep using Trac for tickets, but pull requests on > > > GitHub are also welcome. > > > > Hi everyone, > > > > For extra safety, I recommend you still create Trac tickets for each > suggested change, until we work out how pull requests integrate into the > triage workflow. > > > > Thanks, > > > > -- > > Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/d9oL2HA1IXIJ. 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.
