Re: [DISCUSS] Re-think CI strategy?
Wes, do you primarily want to drop Python 2 to speed up Travis or to reduce
the development overhead? In my experience the development overhead is
minimal and well worth it. For Travis, we could consider looking into other
options like paying for more concurrency.
January 2019 is very soon and Python 2 is still massively popular.
On Mon, Aug 6, 2018 at 5:11 AM Wes McKinney <wesmckinn@xxxxxxxxx> wrote:
> > The 40+ minutes Travis-CI job already uses the toolchain packages AFAIK.
> > Don't they include thrift?
> I was referring to your comment about "parquet-cpp AppVeyor builds are
> abysmally slow". I think the slowness is in significant part due to
> the ExternalProject builds, where Thrift is the worst offender.