core-workflow November 2017

core-workflow@python.org

12 participants
7 discussions

Travis CI running out of disk space
by Mariatta Wijaya 30 Nov '17

30 Nov '17

I saw this twice in the past week, Travis build on CPython failed because "disk quota exceeded". 1st: https://github.com/python/cpython/pull/4573#issuecomment-347039503 2nd: https://github.com/python/cpython/pull/4507#issuecomment-347914746 For now, the build can be re-triggered by: - closing & re-opening the PR - pushing a new change Is it possible to request more disk quota from Travis?

5 4

Adding some concrete examples to the NEWS entry guide?
by Nick Coghlan 27 Nov '17

27 Nov '17

While the lack of conflicts with the new snippet based NEWS entries is excellent, I've noticed something I didn't even realise I was previously relying on: when adding a new NEWS entry, I don't have any example entries to look at the way I did when I was editing Misc/NEWS directly. With the move to conflict-free NEWS, we should probably also move https://devguide.python.org/committing/#what-s-new-and-news-entries out of the committers' section and make it a section under https://devguide.python.org/pullrequest/ instead. So what I'm thinking we could do is: - add some concrete examples for a few different kinds of changes (e.g. bug fix, feature addition, significant internal refactoring) - add those examples to the end of the blurb entry template as comments - migrate most of the existing What's New & NEWS content into the PR guide, and change the "Accepting a PR" section to be about deciding whether or not those entries are needed -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

4 4

Re: Adding some concrete examples to the NEWS entry guide?
by Michael AM Felt 27 Nov '17

27 Nov '17

Having examples in the templates could instill more consistency and hopefully prevent errors as my first attempt failed (did not like bpo- in the first (summary) line. Do not forget clear instructions for when you cannot, for whatever reason, use blurb add. Sent from my iPhoneTenzij hierboven anders aangegeven: / Unless stated otherwise above: IBM Nederland B.V. Gevestigd te Amsterdam Inschrijving Handelsregister Amsterdam Nr. 33054214

1 0

Turning off bedevere-bot messages for core dev PRs?
by Nick Coghlan 23 Nov '17

23 Nov '17

When reviewing other core dev's PRs, the extra state change messages from bedevere-bot don't feel especially helpful. How would folks feel about the idea of tweaking the bot to check if the PR submitter was a core dev, and skip the process explanation messages in that case? Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

3 6

Migration of this list to Mailman 3 imminent
by Nick Coghlan 16 Nov '17

16 Nov '17

Brett's asked for the core-workflow list to be switched over to Mailman 3. This should be transparent to existing subscribers, but the web experience will change: - site wide per-user passwords (not stored in plain text!) - admin and moderator permissions based on user ID, rather than knowing a specific password - the interactive HyperKitty web gateway instead of the static pipermail archives We'll post the details of the URLs after the migration is complete. Cheers, Nick. P.S. We'll also be using this as an information gathering exercise before migrating the larger lists like python-dev, python-ideas, and distutils-sig. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

2 3

Using CircleCI
by Lev Lazinskiy 14 Nov '17

14 Nov '17

Hi team! I recently submitted a PoC PR to the dev guide repo [1] that shows how this repo could be built on CircleCI. The immediate problem that I was trying to solve was to get a free and easy way to store the linkchecker results as a build artifact. A couple of things to note about that build: 1. The entire build (including linkcheck) ran in under 1 minute. 2. We are able to store the build output as artifacts. 3. We can also store the HTML of the build as preview to make it easy to see the entire dev guide site in its state for any commit. Brett commented on the PR and mentioned that there may be a few hurdles in getting the python organization to adopt CircleCI, so I would love to get a conversation going. One thing that Brett mentioned was that there is a limit to the number of concurrent builds that can run at any given time. By default, for all open source projects CircleCI offers four free containers which means you can run four builds at a time (for any project in a given org). I spoke to our developer advocate team and we would be happy to provide the python organization with a total of 15 containers at no cost. Thank you for your time and I am looking forward to hearing from you soon! [1] https://github.com/python/devguide/pull/294 -- Best, Lev Lazinskiy Operator Experience Team Lead | CircleCI https://circleci.com/

2 1

Moving to Buildbot 9 and Python 3
by Craig Rodrigues 03 Nov '17

03 Nov '17

I initiated discussion about moving python.org to using Buildbot 9 and Python 3: https://mail.python.org/pipermail/python-buildbots/2017-September/000133.ht… Folks involved with core-workflow may want to monitor that thread, because I believe it has implications on core developer workflow for Python. Luckily, I think the implications are good. :) Some of the implications I can think of include: - buildbot 9 runs on Python 3, whereas the current buildbot 8 does not (and never will) - buildbot 9 exposes a REST API with queryable endpoints - buildbot 9 has better integration with GitHub pull requests, as can be seen here: http://nine.buildbot.net/#/console - buildbot 9 has better support for Docker, and providers who work with containers such as Hyper.sh -- Craig

3 3

2022

2021

2020

2019

2018

2017

2016

2015

2014

core-workflow November 2017