[Tracker-discuss] 'regression' type

"Martin v. Löwis" martin at v.loewis.de
Thu Apr 8 09:52:51 CEST 2010

> I think it is a normal workflow. How else could people state that
> issue is important for them? 

They can't, and that's a good thing, IMO. If they could state that
issues are important to them, they would have the expectation that these
things also get higher priority with the developers - however, the
developers have priorities that are completely unrelated to a specific
users needs. Then people get upset because the issues they reported as
urgent didn't get proper attention.

It is important that submitters understand that they submit bug reports
not to help them, but to help the Python community. A patch is a better
help than a bug report (typically), and a detailed bug report is a
better help than a fuzzy one.

If people need help themselves, they shouldn't post to the bug tracker.
Instead, they can post in mailing lists; if all else fails, they can
hire somebody to do the work for them.

> If a person thinks that the issue
> is 'critical' or a 'blocker' - that means this person is very
> interested (or even very-very interested) in fixing the issue.

Why is it important for the Python community to know that the bug is
urgent for the submitter? Typically, everybody sees their own bug report
as urgent.

> All you
> need is to show this person that his help is required and assist in
> making a proper contribution.

I typically post a message "do you want to provide a patch?" to indicate
to the submitter that this would be the best way to advance the issue.

> After a few 1-9 cycles you will be able to create a Python
> Contribution Manual, similar or even better than
> http://subversion.apache.org/docs/community-guide/

We have that already:



More information about the Tracker-discuss mailing list