core-workflow February 2018

core-workflow@python.org

10 participants
7 discussions

Add a "refactoring" type to the issue tracker?
by Nick Coghlan 07 Apr '18

07 Apr '18

For https://bugs.python.org/issue32836, I ended up picking "behaviour" as the issue type (since we're reporting that we're using a symbol that we don't actually use), but it did prompt the thought: should we add a "refactoring" type to the issue tracker? Right now, we tend to mark refactoring changes as "enhancement", but I'm thinking there would be value in making it clear that we don't expect end users to notice a particular change, it's just for the benefit of current and future maintainers. Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

5 6

How to retrigger appveyor?
by Mariatta Wijaya 26 Feb '18

26 Feb '18

PRs https://github.com/python/cpython/pull/5775 and https://github.com/python/cpython/pull/5776 are 5 days old, but appveyor never started. Any other way to retrigger appveyor, other than closing and re-opening the PRs? Thanks. Mariatta Wijaya ᐧ

4 3

Making 'blurb' more visible?
by Chris Angelico 21 Feb '18

21 Feb '18

On my recent PR (#340 on GitHub, fwiw), I got a Bedevere check failure for not including a NEWS entry. Couldn't remember the name of the tool used to create them, and had to go digging quite a bit before I found it. Is it possible to add extra info to the failure message, linking to https://devguide.python.org/committing/#what-s-new-and-news-entries ? That would have saved a fair amount of fiddling around. Not sure if this is a workflow question or a Bedevere question, my apologies if I ought to have put this elsewhere. ChrisA

2 2

How long to wait for any reaction to a (new) PR?
by michael＠felt.demon.nl 06 Feb '18

06 Feb '18

a) Hope this is the right place! b) I assume everyone is very busy so I would never assume a reaction with one to two weeks, but - how long is "normal" before asking for a TTT, or something. As an aside - I see that when it takes too long (call it unlucky) something that worked is suddenly "in conflict". More specific, was submitted against 'master' before the 3.7 tag was introduced - and now the master has moved far enough that CI says it cannot merge aka merge conflicts. Again, I understand this is life, but I do not want to make unnecessary noise. If you say, it comes when it comes then I'll just have to wait. Til tomorrow! Michael

3 3

How to filter your issues by the branch name
by Stephane Wirtel 03 Feb '18

03 Feb '18

Hi all, During the week, I just sent an email to this mailing list where I asked if we could add new labels for the issues, these new labels could be '3.5', '3.6', '3.7' etc... In fact, we can search the Pull Requests about a specific branch with the advanced search of Github. For example, if we are looking for the PR of the branch 3.6, we can use:: is:pr is:open base:3.6 just with `base:X.Y` Here is my 2 cents. Have a nice day, Stéphane -- Stéphane Wirtel - http://wirtel.be - @matrixise

1 0

Re: [python-committers] I created the "needs backport to 3.7" labelon GitHub
by Mariatta Wijaya 01 Feb '18

01 Feb '18

If it's protected then backport PR can still happen, but then only Ned can merge it, right? On Jan 31, 2018 6:59 PM, "Steve Dower" <steve.dower(a)python.org> wrote: > I’d suggest not porting anything to that branch until Ned gives the okay. > Hopefully it’s locked right now anyway. > > > > Top-posted from my Windows phone > > > > *From: *Alex Gaynor <alex.gaynor(a)gmail.com> > *Sent: *Thursday, February 1, 2018 10:44 > *To: *Mariatta Wijaya <mariatta.wijaya(a)gmail.com> > *Cc: *core-workflow <core-workflow(a)python.org>; python-committers > <python-committers(a)python.org> > *Subject: *Re: [python-committers] I created the "needs backport to 3.7" > labelon GitHub > > > > Is there documentation somewhere on "how to create a release branch" that > we should add "creating a label" step to? > > > > Alex > > > > On Wed, Jan 31, 2018 at 6:40 PM, Mariatta Wijaya < > mariatta.wijaya(a)gmail.com> wrote: > > I noticed that there is a 3.7 branch now. > > So you can use this label if you want miss-islington to backport a PR to > 3.7. > > > > > _______________________________________________ > python-committers mailing list > python-committers(a)python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > > > > > > -- > > "I disapprove of what you say, but I will defend to the death your right > to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) > "The people's good is the highest law." -- Cicero > > GPG Key fingerprint: D1B3 ADC0 E023 8CA6 > > > > >

1 0

I created the "needs backport to 3.7" label on GitHub
by Mariatta Wijaya 01 Feb '18

01 Feb '18

I noticed that there is a 3.7 branch now. So you can use this label if you want miss-islington to backport a PR to 3.7.

3 3

2022

2021

2020

2019

2018

2017

2016

2015

2014

core-workflow February 2018