[core-workflow] Tracker workflow proposal

[R. David Murray]

On Thu, 24 Apr 2014 14:16:48 +0200, francis <francismb at email.de> wrote:
> > 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 )
> >
> 
> Nice Dashboard:
> 
> +1 for this :-)

We should definitely experiment with some formats for dashboards.
Maybe we can have more than one :)

> BTW. from a Non-Dev point of view:
> 
> I just would like to be able to know how far or ready is a patch for
> manually review and then commit.

Yes, that's part of the goal of my making the state of an issue
more fine grained.

> The precondition for the review should IMHO be that it passes all tests, 
> pep8, bot-integration-tests, and that the patch still applies
> without rework on the 2.7, 3.X tip(s)... (some of those step are
> already doable now, but checks automation would be nice to have).

Still applies is an interesting one...currently rietveld applies against
the parent revision if it knows it, and default if it doesn't, so we'd
need to add some tooling to check it periodically (or on request) against
the tip of the branches it is supposed to be applied to (2.7 and current
maintenance for bugs, default for enhancements) and report the results.

For tests, the patch has to be approved for testing by a committer even
with a patch gating system, and yes, we will want additional feedback
into the tracker about the results of the tests runs.  The interfaces
are all there, I think, to figure that out, but we'll need a bunch of
code to tie it all together.

--David