In a discussion at the sprints today Nick observed that 'invalid' was a
resolution that carried a rather negative subtext ("your bug report was
invalid", ie: "you made a mistake") , and that Red Hat used 'not a bug',
which we all agreed was much more descriptive of the actual resolution.
So, I've changed the text associated with the 'invalid' resolution
to read 'not a bug' instead.
Apologies for the cross post, but I want to make sure committers who
aren't reading python-dev for one reason or another see this:
Based on a number of conversations at PyCon, we've created a new mailing list:
The purpose of this list is to facilitate the conversations and coordinate
the work that needs to happen to improve our development workflow.
Nick's PEP is one piece of this conversation, but there are many other
aspects to it as well.
Here is the list description:
This is a place to discuss and work on improvements to the CPython core
development workflow and the infrastructure that supports that workflow.
This includes changes to the roundup interface and functionality, rietveld,
mercurial, buildbots, and any other infrastructure we may add. It also
includes discussing how we use these tools, and most importantly how we use
these tools to integrate the community beyond the core developers into the
workflow that gets patches committed to the python repository. This means
that it also includes discussions of the process of bringing in new
contributors, including how we use the core-mentorship list, as well as how
we organize ticket triage, and how we make use of external resources such
as openhatch. Discussions of documentation and how we organize and
maintain the documentation are also appropriate.
Anyone who is interested helping with this, or who wants to keep up with the
evolution of our thoughts on these topics, are invited to sign up to the
We will of course check in with python-dev and/or python-committers
I responded to Vinay, but I haven't heard back. I'm forwarding here in case someone else is impacted.
I meant to make this change on the default branch only, but I accidentally made it on 3.4. If someone could revert it for me, I'd appreciate it. I'm away from a computer all day. I'll fix it when I get back.
Begin forwarded message:
> From: Vinay Sajip <vinay_sajip(a)yahoo.co.uk>
> Date: April 15, 2014 at 6:29:11 AM EDT
> To: Eric Smith <eric(a)trueblade.com>
> Subject: CPython repository - changeset not merged into default from 3.4?
> Reply-To: Vinay Sajip <vinay_sajip(a)yahoo.co.uk>
> Hi Eric,
> I made some changes in the Python 3.4 branch which I want to merge into default. I noticed that you made some changes in 3.4 in changeset 16efa8d27e4c which don't appear in default - is this intentional? Your changes are lumped in with mine when I try to merge :-(
> Vinay Sajip