On Tue, 18 Aug 2015 12:47:22 +1000, Ben Finney ben+pyt...@benfinney.id.au
wrote:
Robert Collins robe...@robertcollins.net writes:
However - 9 isn't a bad number for 'patches that the triagers think
are ready to commit' inventory.
So yay!. Also - triagers, thank you for feeding patches
On 8/18/15 7:52 AM, R. David Murray wrote:
On Tue, 18 Aug 2015 12:47:22 +1000, Ben Finney ben+pyt...@benfinney.id.au
wrote:
Robert Collins robe...@robertcollins.net writes:
However - 9 isn't a bad number for 'patches that the triagers think
are ready to commit' inventory.
So yay!. Also -
On Mon, Aug 17, 2015 at 7:37 PM, Robert Collins
robe...@robertcollins.net wrote:
On 26 July 2015 at 07:28, Robert Collins robe...@robertcollins.net wrote:
For my part, I'm going to pick up more or less one thing a day and
review it, but I think it would be great if other committers were to
Robert Collins robe...@robertcollins.net writes:
However - 9 isn't a bad number for 'patches that the triagers think
are ready to commit' inventory.
So yay!. Also - triagers, thank you for feeding patches through the
process. Please keep it up :)
If I were a cheerleader I would be able to
On 26 July 2015 at 07:28, Robert Collins robe...@robertcollins.net wrote:
On 21 July 2015 at 19:40, Nick Coghlan ncogh...@gmail.com wrote:
All of this is why the chart that I believe should be worrying people
is the topmost one on this page:
http://bugs.python.org/issue?@template=stats
Both
On 7/26/15 6:37 PM, R. David Murray wrote:
On Sun, 26 Jul 2015 22:59:51 +0100, Paul Moore p.f.mo...@gmail.com wrote:
On 26 July 2015 at 16:39, Berker PeksaÄŸ berker.pek...@gmail.com wrote:
So, I'm hoping Carol will take what I've written above and turn it into
updates for the devguide
On 25 July 2015 at 20:28, Robert Collins robe...@robertcollins.net wrote:
Those charts doesn't show patches in 'commit-review' -
On Sun, Jul 26, 2015 at 2:58 PM, Paul Moore p.f.mo...@gmail.com wrote:
On 25 July 2015 at 20:28, Robert Collins robe...@robertcollins.net wrote:
Those charts doesn't show patches in 'commit-review' -
On Sun, Jul 26, 2015 at 11:39 AM, Berker Peksağ berker.pek...@gmail.com
wrote:
I'm not actually clear what Commit Review status means. I did do a
quick check of the dev guide, and couldn't come up with anything,
https://docs.python.org/devguide/triaging.html#stage
What is probably missing
On 26/07/2015 22:59, Paul Moore wrote:
On 26 July 2015 at 16:39, Berker Peksağ berker.pek...@gmail.com wrote:
I'm not actually clear what Commit Review status means. I did do a
quick check of the dev guide, and couldn't come up with anything,
On 26 July 2015 at 16:39, Berker Peksağ berker.pek...@gmail.com wrote:
I'm not actually clear what Commit Review status means. I did do a
quick check of the dev guide, and couldn't come up with anything,
https://docs.python.org/devguide/triaging.html#stage
Thanks, I missed that. The patches I
On Sun, 26 Jul 2015 22:59:51 +0100, Paul Moore p.f.mo...@gmail.com wrote:
On 26 July 2015 at 16:39, Berker PeksaÄ berker.pek...@gmail.com wrote:
I'm not actually clear what Commit Review status means. I did do a
quick check of the dev guide, and couldn't come up with anything,
On 27 July 2015 at 11:37, R. David Murray rdmur...@bitdance.com wrote:
My goal here is to *transfer* the knowledge of what makes a good review
process and a good patch from the existing committers to new committers,
and therefore acquire new committers.
+1000 :)
A few years back, I wrote this
On 21 July 2015 at 19:40, Nick Coghlan ncogh...@gmail.com wrote:
All of this is why the chart that I believe should be worrying people
is the topmost one on this page:
http://bugs.python.org/issue?@template=stats
Both the number of open issues and the number of open issues with
patches are
14 matches
Mail list logo
