From rodrigc at crodrigues.org  Thu Nov  2 18:42:00 2017
From: rodrigc at crodrigues.org (Craig Rodrigues)
Date: Thu, 2 Nov 2017 15:42:00 -0700
Subject: [core-workflow] Moving to Buildbot 9 and Python 3
In-Reply-To: <CAG=rPVcs628iFr_Eje2+WrJ1F7eBMV3ppiwek45QyC070G=OJg@mail.gmail.com>
References: <CAG=rPVcs628iFr_Eje2+WrJ1F7eBMV3ppiwek45QyC070G=OJg@mail.gmail.com>
Message-ID: <CAG=rPVdX8-PRHcxhscoB7yH58oTRNFMtj4MJzpErD7SyaQzXCw@mail.gmail.com>

Zachary Ware upgraded python.org's  buildbot from 0.8 to 0.9:

https://www.python.org/dev/buildbot/

buildbot 0.9 is the first release of buildbot that
can run on Python 3.  The python.org buildbot master is running on Python
3.4:

http://buildbot.python.org/all/#/about

That master is connected to multiple workers/slaves, most of which are
0.8 running on Python 2:

http://buildbot.python.org/all/#/workers

This is a highly visible deployment of Twisted running Python 3,
and aligns with python.org's direction to move the world to Python 3. :)

--
Craig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20171102/e5e48c2b/attachment.html>

From ncoghlan at gmail.com  Fri Nov  3 00:19:17 2017
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Fri, 3 Nov 2017 14:19:17 +1000
Subject: [core-workflow] Moving to Buildbot 9 and Python 3
In-Reply-To: <CAG=rPVdX8-PRHcxhscoB7yH58oTRNFMtj4MJzpErD7SyaQzXCw@mail.gmail.com>
References: <CAG=rPVcs628iFr_Eje2+WrJ1F7eBMV3ppiwek45QyC070G=OJg@mail.gmail.com>
 <CAG=rPVdX8-PRHcxhscoB7yH58oTRNFMtj4MJzpErD7SyaQzXCw@mail.gmail.com>
Message-ID: <CADiSq7cOwDfvh2P-PH1-ga_XghciAo_tDsOh6CyNNbvOp=FWgw@mail.gmail.com>

On 3 November 2017 at 08:42, Craig Rodrigues <rodrigc at crodrigues.org> wrote:
>
> Zachary Ware upgraded python.org's  buildbot from 0.8 to 0.9:
>
> https://www.python.org/dev/buildbot/
>
> buildbot 0.9 is the first release of buildbot that
> can run on Python 3.  The python.org buildbot master is running on Python
> 3.4:
>
> http://buildbot.python.org/all/#/about
>
> That master is connected to multiple workers/slaves, most of which are
> 0.8 running on Python 2:
>
> http://buildbot.python.org/all/#/workers
>
> This is a highly visible deployment of Twisted running Python 3,
> and aligns with python.org's direction to move the world to Python 3. :)

Very cool!

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

From lev at circleci.com  Thu Nov  9 00:18:04 2017
From: lev at circleci.com (Lev Lazinskiy)
Date: Wed, 8 Nov 2017 21:18:04 -0800
Subject: [core-workflow] Using CircleCI
Message-ID: <CAMHGOmQQvQ2TC94v27j0FxgL5wGf1gSP5QOD_R_HuRLPai0VBw@mail.gmail.com>

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/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20171108/969e50ca/attachment.html>

From brett at python.org  Tue Nov 14 15:56:02 2017
From: brett at python.org (Brett Cannon)
Date: Tue, 14 Nov 2017 20:56:02 +0000
Subject: [core-workflow] Using CircleCI
In-Reply-To: <CAMHGOmQQvQ2TC94v27j0FxgL5wGf1gSP5QOD_R_HuRLPai0VBw@mail.gmail.com>
References: <CAMHGOmQQvQ2TC94v27j0FxgL5wGf1gSP5QOD_R_HuRLPai0VBw@mail.gmail.com>
Message-ID: <CAP1=2W5ChvOsA1-R-xZkMDJ9JMk3MVVCF8QThHUtWbWf-ESLhA@mail.gmail.com>

On Tue, 14 Nov 2017 at 10:57 Lev Lazinskiy <lev at circleci.com> wrote:

> 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.
>

OK, so this is where I get confused by the Circle CI pricing docs every
time. :) So above you said "four free containers ... for any project in a
given org". Does that mean by default it's four builders per repo or per
organization on GitHub? My guess is it's the latter since you're offering
15 builders for the Python organization as a whole.

Another question for me is does any of this include macOS builders?

Basically the only real complaints we have received from developers about
Travis is performance due to how long it takes to run our builds. This also
bleeds into macOS support as we have simply turned it off due to the time
it has traditionally taken to get a macOS builder on Travis for open source
projects. This has also been an issue at PyCon US during the sprints when
python/cryptography managed to suck up all the builders the Python
organization shared (we learned afterwards that had we notified Travis
ahead of time we could have gotten a builder increase for that week to
handle the unusual load).

So for me, I think that if Circle CI can give us:

   1. We can move our .travis.yml over without losing functionality
   2. Faster builds than Travis
   3. macOS builds which are reliably scheduled
   4. Can give us temporary increases during PyCon US if we share builders
   across the organization

then I think this may be worth discussing.

-Brett




>
> 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/
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20171114/723bd2bc/attachment.html>

From ncoghlan at gmail.com  Wed Nov 15 18:09:47 2017
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Thu, 16 Nov 2017 09:09:47 +1000
Subject: [core-workflow] Migration of this list to Mailman 3 imminent
Message-ID: <CADiSq7fkcO9ZHQCvMeb_1VL2gxnJ-yO09Dm09uDG0ixWJGKdNQ@mail.gmail.com>

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 at gmail.com   |   Brisbane, Australia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20171116/071cb6f4/attachment.html>

From mariatta.wijaya at gmail.com  Wed Nov 15 18:20:44 2017
From: mariatta.wijaya at gmail.com (Mariatta Wijaya)
Date: Wed, 15 Nov 2017 15:20:44 -0800
Subject: [core-workflow] Migration of this list to Mailman 3 imminent
In-Reply-To: <CADiSq7fkcO9ZHQCvMeb_1VL2gxnJ-yO09Dm09uDG0ixWJGKdNQ@mail.gmail.com>
References: <CADiSq7fkcO9ZHQCvMeb_1VL2gxnJ-yO09Dm09uDG0ixWJGKdNQ@mail.gmail.com>
Message-ID: <CAGbohnZnh_+LoLC+fegb7yFkqZUB2rcZOdunAZ+opyE7m4f9nQ@mail.gmail.com>

Thanks for starting this, Nick!
The other mailing list we're looking into migrating is core-mentorship.

I've emailed postmaster and Barry about it last month. I haven't heard
anything back.

Mariatta Wijaya

On Wed, Nov 15, 2017 at 3:09 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:

> 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 at gmail.com   |   Brisbane, Australia
>
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20171115/091c401d/attachment.html>

From mariatta.wijaya at gmail.com  Wed Nov 15 19:05:06 2017
From: mariatta.wijaya at gmail.com (Mariatta Wijaya)
Date: Wed, 15 Nov 2017 16:05:06 -0800
Subject: [core-workflow] Migration of this list to Mailman 3 imminent
In-Reply-To: <CAGbohnZnh_+LoLC+fegb7yFkqZUB2rcZOdunAZ+opyE7m4f9nQ@mail.gmail.com>
References: <CADiSq7fkcO9ZHQCvMeb_1VL2gxnJ-yO09Dm09uDG0ixWJGKdNQ@mail.gmail.com>
 <CAGbohnZnh_+LoLC+fegb7yFkqZUB2rcZOdunAZ+opyE7m4f9nQ@mail.gmail.com>
Message-ID: <CAGbohna7XfKwCCC8A5f0rf293C4x4sV=yJzf-B+G3aYQcSC_HA@mail.gmail.com>

Sorry! Mark did reply to me, I missed it somehow :(

Will follow up. Thanks Mark!

Mariatta Wijaya
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20171115/d941bec3/attachment.html>