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

Pants

lol some tests timed out, I restarted them

ok hit merge on <https://github.com/pantsbuild/pants/pull/9530>

Starting release prep for 1.27.0rc0. anyone have anything they want to make sure gets in?

I myself would like to get <https://github.com/pantsbuild/pants/pull/9552> merged assuming it passes CI soon

but while that CI is still going, <https://github.com/pantsbuild/pants/pull/9573>

<@U0AALHEDR>: hey: so i think that twitter was very close to dropping Centos6? given that, we’re looking at swapping wheel building to Centos7

Hey Stu, chatted with Prathap, a few more folks need to be migrated, so end of Q2 likely.

Are the release branches force push protected? I want to re-write some history because I messed up the pick I did to 1.25.x. If not I can fix forward, but the history will be a little ugly.

I don’t even think master is protected?

Maybe it is force push protected, but I’m pretty you sure you can push directly to master at a minimum

Yeah, that isn’t as scary to me, though maybe not ideal

But as far as you know release branches are setup as normal branches?

Yes. They get created during the release process by the releaser creating the branch locally then doing `git push origin 1.26.x`

set the channel topic: <https://www.pantsbuild.org/release.html>

Is v1.26 or v1.27 the next release? What distinguishes these two releases?

Hello! There are a couple releases in process:
* 1.26.0rc2
* 1.27.0rc0
* 1.28.0.dev0

The reason there are so many is that we always have a weekly release, but after about 3-5 releases we branch off a stable release series, like 1.26.x. We use as many release candidates as necessary for a final “stable” release like 1.26.0 to be released. When testing RCs (release candidates), we try to fix any bugs, including performance bugs, found by users in testing out the series.

1.26.0 has taken a particularly long time to land because it upgrades from Pex 1.0 to Pex 2.0, which was a major rewrite of Pex to use Pip to resolve dependencies instead of its own custom resolver. This generally works much better, but there’s one remaining issue with increased network usage.

--

If you want the latest and greatest, we recommend 1.28.0.dev0 (it’s what we use at Toolchain). In particular, if you’re using the V2 implementation of Python documented at <https://pants.readme.io/docs>, we recommend 1.27.0rc0 or 1.28.0.dev0 because it makes several improvements to that experience.

You can see release notes at <https://www.pantsbuild.org/notes-master.html>.

Thank you for laying it out.

I saw there was a network issue. pantsbuild is waiting for `pip` to implement a change for that one, if I was following the slack stream correctly.

Cool. You’ll want to stay on 1.25.x, then, for now. The post right below this is about a fix to the network request issue

I am interested in the V2 improvements so I will test out `1.27.0rc0`.

I don't think my company's team is big enough for the pip network issues to be a bottleneck. But I will watch out for it.

Awesome! Please let us know if we can help with anything or you find any issues. See <https://github.com/pantsbuild/example-python> for an example Python repository demoing how to turn on V2 and how to use all its features

(Warning that the very first time you run something like `./pants test` will be slower than we’d like because we have to download all your 3rd party dependencies. We’re working to speed this up. After the first run, the cache will kick in and it should be much faster.)

erk?! `example-python/helloworld/main.py` but but where is all the `pants` bureaucracy directories? :troll: Now I'm going to have to update our documentation and not indoctrinate every new hire into why `helloworld/src/python/helloworld` makes sense. I see `1:1:1` is still a thing. :+1:

I have some RTNewM to do.

Hehe you can still use `src/python` if you want :wink: it’s particularly useful for polyglot repos (i.e. multiple languages). But, if you just have Python, then indeed it is much simpler to drop the `src/python`

Yes, 1:1:1 is still recommended :slightly_smiling_face: You can of course use a different pattern, but 1:1:1 works nicely because of default `sources` values

speaking of which: <@U051221NF>: if you have time to take a look at <https://github.com/pantsbuild/pip/pull/7> it would be appreciated. it was one of the last things blocking 1.26.x, iirc. cc <@U0AALHEDR>

I can rubber-stamp it, but I expect <@U04S45AHA> will have smarter thoughts about how much we should be drifting on our Pip fork.

that reminds me — the other pip fix i made a while ago has since been merged upstream. i’ll make a followup diff to get ours using the same code as upstream?

Although I guess since this is a cherry-pick from an upstream PR linked to an upstream issue, there's a decent chance something like this will get in, so... approved

we have a little bit of leeway at the moment, as we are shifting our repo to be pypi index style

we can push on <https://github.com/pantsbuild/pip/pull/7> if shifting repo style turns out to be problematic

<@U0AALHEDR>: so, if that’s the case, should we go ahead and finalize 1.26.x?

would be really good to have a stable release out.

can we wait till it’s released for a couple of days? aiming to land tmr

and “finalize” is too strong a word. just “cut final”, and then you can cheerry-pick

<@U0AALHEDR>: so, at this point it’s been 14 days since the last commit in <https://github.com/pantsbuild/pants/tree/1.26.x>

1.26.0. it wouldn’t stop additional cherrypicks from hitting the branch

Ah I see. In that case, please go ahead. Thanks!

yea, i’ll* do that. you can continue to pick there if need be.

<https://github.com/pantsbuild/pants/pull/9654>

related: who is going to run the 1.27.x release? i think Greg cut it, but it’s unclear who will be vetting.