[python-committers] Fwd: Trunk and 3.0 branch are now open
Brett Cannon
brett at python.org
Thu Aug 21 22:31:37 CEST 2008
More information about the python-committers mailing list
Thu Aug 21 22:31:37 CEST 2008
- Previous message: [python-committers] Fwd: Trunk and 3.0 branch are now open
- Next message: [python-committers] Fwd: Trunk and 3.0 branch are now open
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Aug 21, 2008 at 12:00 PM, Benjamin Peterson <musiccomposition at gmail.com> wrote: > ---------- Forwarded message ---------- > From: Benjamin Peterson <musiccomposition at gmail.com> > Date: Thu, Aug 21, 2008 at 1:58 PM > Subject: Re: [python-committers] Trunk and 3.0 branch are now open > To: Brett Cannon <brett at python.org> > > > On Thu, Aug 21, 2008 at 1:30 PM, Brett Cannon <brett at python.org> wrote: >> >> That's what I was thinking; either real name or username, which ever >> you remember at the time. Since we don't have a way to flag an issue >> with a patch as needing a committer review, either we just continually >> check for release blockers with patches or we email here saying what >> issues have a patch ready and just need a second review. > > I've created a keyword, "needs review", that we can attach to issues. > Then you use the "Needs review" query [1] to find them. > This will work short-term until after final is out and we discuss how we want our triage process to go. And it is probably best not to deselect the "patch" keyword if you do set this keyword; they are not mutually exclusive. -Brett
- Previous message: [python-committers] Fwd: Trunk and 3.0 branch are now open
- Next message: [python-committers] Fwd: Trunk and 3.0 branch are now open
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list