Message info
 
To:django-developers@googlegroups.com From:ptone Subject:Re: Ticket 16317 https://code.djangoproject.com/ticket/16317 Date:Sun, 18 Mar 2012 09:19:55 -0700 (PDT)
 



On Friday, March 16, 2012 7:00:32 AM UTC-7, Marcob wrote:
The ticket 16317 has a very nice 4 months old patch (it's has a two
lines fix, remainder are just test fixes).
It was marked for 1.3 version but now it's better to change it to 1.4
version.
As I really hate to patch django I think my only solution is "to
lobby" this ticket here :-)
Is there anything else I can do?

This is where the community can help the core about by:

- applying the patch and verifying that it applies cleanly to current trunk
- see if it fixes the issue as you understand it or are experiencing it
- do your best to review the tests and determine if docs would be needed

If all looks OK, comment that you have done the above and mark "Ready for checkin"

I think too few people realize that this last step is something they can do.  It is not a guarantee of a prompt checkin - but it certainly increases the chance it will be seen.  I'd say only after it has sat in that state for a bit, does it make sense to post a nudge here.

-Preston

Ciao.
Marco.
P.S. Someone said the putting your email in cc in a ticket isn't the
way to go.

--
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/-/3Delk-NooHsJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to django-developers+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.