On 12 March 2017 at 23:58, R. David Murray wrote:
> On Sun, 12 Mar 2017 11:37:21 -, Paul Moore
> wrote:
> > I don't have a problem with the new "PRs attached to this issue" field
> > - that's of course important to have. But is there any way to not have
> > them generate emails (probably on
I agree that overall the new workflow is great. I haven't done a ton of
commits, but the ones I did went very smoothly (modulo the known and hopefully
soon to be fixed Misc/News conflicts). I also love being able to do reviews
on GH, and I think the more testing automation we can do, the better.
On Mar 13, 2017, at 01:12 AM, Brett Cannon wrote:
>Since there doesn't seem to be strong support I'm leaning towards switching
>it off as well, but I will wait until there's been at least a weekday
>around the globe for people to notice this email thread.
I actually kind of like the idea of a men
That suggests an interesting question: Why is the Touched It Last so
different from the domain expert :-)
Alex
On Mon, Mar 13, 2017 at 11:54 AM, Barry Warsaw wrote:
> On Mar 13, 2017, at 01:12 AM, Brett Cannon wrote:
>
> >Since there doesn't seem to be strong support I'm leaning towards
> switc
Le 13/03/2017 à 16:56, Alex Gaynor a écrit :
> That suggests an interesting question: Why is the Touched It Last so
> different from the domain expert :-)
Because there are many changes which don't necessitate a domain expert's
intervention (such as replacing one argument-parsing API with another
Hi,
First, I'm really happy that we moved to git and GH. The GH review tool
is super convenient and CI integration helps.
I'm less happy about requiring to make a PR for every commit. It's a no
problem for new features development, but it's a huge pain for a bug
fixing workflow. Last week
> On Mar 13, 2017, at 11:54 AM, Barry Warsaw wrote:
>
> I actually kind of like the idea of a mentionbot, but the current
> implementation has some problems. Rather than calculating who should be
> mentioned based on TIL (touched it last), it would be nicer if this got closer
> to solving Raymo
On Mon, 13 Mar 2017 12:48:30 -0400, Yury Selivanov
wrote:
> Yesterday I was working on a few asyncio PRs and a bug in async/await.
> All PRs required cherry-picking. Again, I was spending significant
> amount of time just creating branches/PRs for cherry-picking. Again
> waiting for CI chec
