On Jan 23, 5:14 pm, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > On Fri, Jan 23, 2009 at 2:38 PM, Julien Phalip <jpha...@gmail.com> wrote: > > > Now, I know that this is sort of an edge case, and I also know that > > there are more important and more urgent matters at this moment. But > > I'd be keen to hear what is the official (or tacit) policy for that > > kind of small bug reports. There probably are a few other tickets in > > that situation (#9404 is another example). So, what is the best way to > > go for people interested in having them checked in? Is it simply by > > bringing them up on this mailing list from time to time? If so, then I > > can try again after 1.1 lands. > > Hi Julien, > > Unfortunately, there's no simple answer to this question. > > The short answer is that it is all about timing and opportunity. > > A polite, well-timed message to the mailing list is certainly one way > to get attention. Keep an eye on the grand schedule. If you make noise > when the core devs are under the hammer trying to hit a feature > deadline or manage a planning phase, you're probably going to get > ignored. However, raising the ticket when the core devs are paying > attention to bugs - just before a bug fixing sprint, or in the leadup > to a beta release for example - is likely to get some traction. > > Gentle IRC reminders can also work - again, strategically timed > (during a bug sprint would be a very good time, for example). > > Another way to get traction is to pull related items together. When I > jump into the code to fix a bug in an area I haven't touched for a > while, it can take a few minutes to refresh my memory on exactly how > things work. If you collect minor bugs together into similarly themed > groups, you make an attractive target for us core devs (who are, after > all, exceedingly lazy and like easy jobs much more than hard jobs :-) > > I wish I could give you a concrete answer (ask by email, written in > sanskrit, between 1 and 1:10 pm UTC on Tuesday afternoons :-) but like > all things open source, it isn't that simple. > > Yours, > Russ Magee %-)
Thank you Russell for your clear explanation. In fact, I would copy/ paste your reply right into the Django documentation (http:// docs.djangoproject.com/en/dev/internals/contributing/#id1). Those tips are very useful to know! Julien --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
