Releasers - testing the waters on an idea. I'd like to change the release process to automate the pypi portion - which will end up automating the whole thing such that release becomes just the process of tagging a green origin branch build. The CI run against that tag would push to pypi and publish the docsite. The motivation is killing hand-rolled VERSION munging and wheel re-writing. I've wanted to do this for a while, but Benjy's difficulties on this last release were a prompt to re-engage. This would require creating a pypi bot account for travis-ci to use.

Sounds good 🙂

We already have that. The driving idea is to kill the munging we do. We currently rewrite

src/python/pants/VERSION

, and more problematically, entire wheels / wheel contents. The latter would be nice to avoid in particular and bit Benjy in the last release. There is support for adding a build tag directly in setuptools no one knew about when this was all established that, when combined with automated release via tag will net us the same outputs we have today using standard tools we don't need to maintain.

We already have that by convention rather than because it’s enforced in a script, right?

Well, the release script generates a tag. You could try to buck the script to get a release sans tag but it would be a good bit of manual work and know-how.

Oh, didn’t realise that, I thought the tag was manual