Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

the s3 publishing happens in the first two shards

but yea, you're right about the network aspect to integration tests.

darn. that's probably going to be the largest blocker.

unless we committed to getting our own scoot deploy.

but seems like it's possible (though unlikely?) that they will allow network access.

do you remember who it was that announced that at bazelcon? or know any keywords?

David Stanke is probably the person to talk to

... bit stale maybe: <https://twitter.com/davidstanke>

image.png

<@U054MQUPL> uploaded a file: <https://pantsbuild.slack.com/files/U054MQUPL/F9DPFLJFR/image.png|image.png>

...whoops. that was supposed to have been me.

Based on our new, higher-cadence release schedule, should 1.4.0 be released this week?

<@U051221NF>: um, i think the docs say something like "stable releases involve at most 5 days per rc" or something like that

in practice though, we're going to have to figure out what a good rc/final schedule looks like

The last rc was almost a month ago I think? I just haven’t been following it, but it suddenly occurred to me.

basically, we ended up releasing `1.4.0rc1` internally... we found one more bug, hence the next rc

so, they're pretty darn stable. but i noticed recently that `pip` will only install stable releases... so currently i think it's still installing `1.3.0` for folks =(

so yea, getting a final release out will be important. assuming i'm able to successfully release `rc2` internally, i'll probably immediately cut `1.4.0` final

and <@U0AALHEDR> is trying to find a good candidate for `1.5.0rc0`, but <https://github.com/pantsbuild/pants/issues/5426> is currently blocking that, because master isn't looking good in our repo

reverts look a bit too fishy with all of the package reorganization, so hoping John has time to fix forward next week.

blargh. looks like pypi might have broken gpg signing somehow.

```twine --version
twine version 1.9.1 (pkginfo: 1.4.1, requests: 2.18.4, setuptools: 38.5.1,
requests-toolbelt: 0.8.0, tqdm: 4.19.5)``` is getting a response from pypi indicating that the gpg signature: ```HTTPError: 400 Client Error: gpg_signature: Should not be a tuple. for url: <https://upload.pypi.org/legacy/>```

i have no idea why it is trying to upload to the legacy url though. i don't have it mentioned anywhere, and i've confirmed that all of twine, pip, setuptools, python are modern enough (EDIT: `<https://upload.pypi.org/legacy/>` is actually the correct/modern/default url)