Prepare the 1.15.0rc0 release.

[stuhood]

No description provided.

[cosmicexplorer]

Lots of exciting changes!!

[Eric-Arellano]

Woohoo!

We've discussed this a bit over Slack. Because we've now put out to the universe that 1.15.0 is the first stable release to support Py3, we might need to cherry-pick a few PRs in these RCs. The remaining issues we have:

• Py37 CI
• Releasing as Py3 compatible PEX
• Fixing flaky Idea test
• Fixing Python tasks test, which I think is blocked by Pex upgrade
• Fixing console test, which I think was blocked by Pex upgrade but not sure

Of these, the only that seems essential to cherry-pick is releasing as Py3 Pex, along with any of the test fixes if they end up involving changes to src code. Consequently, I'll prioritize pursuing that.

[stuhood]

Of these, the only that seems essential to cherry-pick is releasing as Py3 Pex, along with any of the test fixes if they end up involving changes to src code. Consequently, I'll prioritize pursuing that.

Which changes are blocking that, do we think?

[Eric-Arellano]

Which changes are blocking that [i.e. releasing as Py3 compatible PEX], do we think?

• Honor interpreter constraints even when PEX_PYTHON and PEX_PYTHON_PATH not set pex-tool/pex#668. Borja has been working on it, and I'm helping out now to cross finish line.
• PEX releasing more flexible binaries (Release more flexible pex binaries. pex-tool/pex#654)
• Pants upgrading to newest PEX.
• Tweaks to release.sh.

If this is out of scope or it takes too long to land, I do not think it's the end of the world to wait for Py3 support for Pex until 1.16.0.

Alternatively, we could temporarily release a Pex27, Pex36, and Pex37 like Pex does. Thoughts?

[stuhood]

Alternatively, we could temporarily release a Pex27, Pex36, and Pex37 like Pex does. Thoughts?

That would be a much more reasonable thing to cherry pick I think.