[core-workflow] Tracker workflow proposal

[Berker Peksağ]

On Mon, Apr 21, 2014 at 7:04 PM, R. David Murray <rdmurray at bitdance.com> wrote:
> Priority
> ~~~~~~~~
>
>     low
>     normal
>     high
>     deferred blocker
>     release blocker
>
> The only change here is to eliminate 'critical'.  I'm not wedded to
> that, but if we have both 'critical' and 'high' priorities, 'high'
> ends up getting treated as pretty much equivalent to either 'normal' or
> 'critical', depending on the person.  I would argue that anything that
> is severe enough to be marked 'critical' should in fact be a release
> blocker, and anything that is not a release blocker is effectively only
> 'high' priority.
>
> The priority is currently operational only in that one can sort issues by
> priority.  I propose that we make them much more operational, by posting
> a count and/or list of the bugs with more than normal priority somewhere
> public on a regular basis, such as python-dev, python-committers,
> and/or #python-dev.  (Well, definitely #python-dev.)

The Django project uses a development dashboard to display numbers
like "release blockers", "patches needing review", etc:
https://dashboard.djangoproject.com/ It would be good if there is a
dashboard like that for CPython (by using Roundup's XML-RPC API:
http://roundup.sourceforge.net/docs/xmlrpc.html#client-api )

--Berker