[core-workflow] Tracker workflow proposal

[Guido van Rossum]

If there is considerable work in porting something between branches you
might have a task per branch. (This might also provide clarity about which
branches are being targeted.) Or sometimes you might have separate tasks
for code, tests, docs.

Then again, it does sound pretty marginal, and I'm not saying that our
current process is broken where these specific flows are concerned.


On Mon, Apr 21, 2014 at 1:42 PM, Barry Warsaw <barry at python.org> wrote:

> On Apr 21, 2014, at 04:29 PM, R. David Murray wrote:
>
> >I have to say that as an outsider looking in, this was *totally*
> >confusing.  I signed up to see 'python' bugs, and most of the traffic
> >on the tickets seemed to be about changes to things that looked like
> >other tickets but I guess were bug tasks.
> >
> >Our case would be more straightforward...but I'm still not sure that
> >the extra complexity would be worth it.
>
> Right.  It makes a lot more sense when you're working on multiple packages
> across the distro instead of primarily on a single package.
>
> It may not make sense for the Python tracker, where you're essentially
> working
> on a single project, although I wonder if adding alternative
> implementations,
> or subprojects (e.g. idle) might make it more relevant.  Anyway, I was
> mostly
> just throwing that out there to think about.
>
> -Barry
>
> P.S. I'll mostly leave the blocker/deferred discussion to active RMs, since
> they're most affected by it.  But I think it probably does make sense to
> have
> a release-manager role with certain additional privileges.
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>



-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20140421/427c3285/attachment.html>