On Thu, Jan 14, 2010 at 11:07 AM, Pablo López <plval...@gmail.com> wrote:
> I know, but it looked a django bug, that is why I posted here, because > I think it makes more sense discussing about _potential_ django bugs > with their developers than doing it with their users. I'll search > better for next time. > > Note if you are quite sure you have found a bug, the right place to go is the tracker. Search there, and it you don't find that it has already been reported, open a ticket. There is no need to get clearance from the developer's list first (but please do search first). Most bugs don't require discussion on the dev list, it's only when the bug raises some design question that discussion might be taken to the list. If you aren't sure, the right place to ask is the user's list. You are not limiting your audience that way: far more people read -users than -developers, and core developers read and participate in discussions on the user's list. You may well get a quicker answer there than here. If it does seem like a genuine unreported bug someone will likely ask you to open a ticket in the tracker for it. This list: http://docs.djangoproject.com/en/dev/internals/contributing/#id1is useful for getting a sense of what is the preferred approach to use for various situations. Karen--
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.
