@wide-energy-11069: do y’all know whether you’re planning to get on 1.27.x?

I cut 1.27.0rc0 friday before last

@witty-crayon-22786 not yet. we will look through the commits between 1.26 and 1.27, and see how many we need. If not too many, we’d heavily lean towards freezing at 1.26

@wide-energy-11069 it sounds like you all won’t go to 1.28.x, then, right? If so, could we proceed with dropping Centos6 for 1.28.x? We won’t touch 1.26.x or 1.27.x.

that sounds reasonable yeah

Awesome, thank you!

Look good for a reply to Stu’s email to pants-devel from February 2019 about centos6?

Hello! We plan to move forward with 1.28.x being the first release to be built with Centos7, which means that the pantsbuild.pants wheel will be built with manylinux2014 instead of manylinux2010*.

Please reply to this email if you are still depending on manylinux2010 and we will explore alternatives to maintain manylinux2010 compatibility a bit longer.

Additionally, we will no longer be building a single cp36-abi3 wheel, but will build distinct wheels for cp36-cp36m, cp37-cp37m, and cp38-cp38m. This should have no direct impact on you. The ./pants script will still download the correct version of Pants for you, regardless of which version of Python 3 you are using to run Pants.

*We've been incorrectly marking pantsbuild.pants as manylinux1. It is really manylinux2010, as we have been building it on Centos6 instead of Centos5. 

Thanks,
Eric Arellano

(the abi3 thing also means we won’t support

3.9

immediately as well, but not sure if worth calling out)

Yes, that is true

Related. Now that we’re building distinct wheels, at what point do we want to deprecate running Pants with Python 3.6? It isn’t EOL until December 2021, but I think John proposed generally only supporting the latest two Python releases. Python 3.9 comes out in October

i’d like to sidestep that question by embedding, if possible.

but. it feels too early to get rid of 3.6. no hard data.

Agreed, I think probably at least 2 more months

@witty-crayon-22786 starting cherry picks to 1.26.x for an rc1 with tokio compat and notify.

fire away

except it will be

1.26.1rc0

heh

so we cut a stable 1.26.1 recently?

no, i finished cutting 1.26.0 yesterday

the next stable release after

1.26.0

will be

1.26.1

, and the first release for

1.26.1

will be

1.26.1rc0

see https://www.pantsbuild.org/release_strategy.html#examples

Ah. I get it.

@wide-energy-11069: will you be able to do the release today?

was just talking with @happy-kitchen-89482: given that we won’t have Twitter helping to vet stable releases, we’ll need to double down on asking the community (and Toolchain) to actually test rcs

and we’ll probably need to abide more closely to the rc testing windows… currently it says “5 business days without an issue report”.

right now that would qualify

1.27.0rc0

to graduate to

1.27.0

(and toolchain is done testing it, so)

1.27.0rc0 has several bugs I’ve fixed that need to be cherry-picked into 1.27.0rc1

But agreed, generally