hey folks! we’re due for another `2.13.x` … if you...
# development
w
hey folks! we’re due for another
2.13.x
… if you have any cherry-picks, please take a second to get them out today.
👍 1
there are still some unresolved issues, but we’re done cherry-picking features, so it feels like it should be an
rc
rather than an
a
b
I still can't repro https://github.com/pantsbuild/pants/issues/16099 Can someone running Mac OS try and repro using the provided repo? The user is using WSL2, which is suspect, but thought we''d give it a whirl on a different OS (I'm using Ubuntu 20)
I'm realizing I should've added support for a default value for
python_source
's
run_goal_use_sandbox
field in the `python`subsystem to unblock me in 2,13. 👍 👎 on that getting cherry-picked if I get the PR out ASAP?
w
yea, seems fine.
🎉 1
b
(not changing existing behavior w.r.t. the current default)
w
another issue was reported against
2.13.x
, so i won’t cut tonight
b
Would it be an abuse to cherry-pick https://github.com/pantsbuild/pants/pull/16215? That way the blog post I'm writing can be relevant as of 2.13
f
the GitHub shows that my commit https://github.com/pantsbuild/pants/commit/1368a18e94027b393b41c8a1a4e162c5ce2f6a6d is part of the 2.13.x and 2.14.x tags. Does this mean it will make it to the release of 2.13? It would be great so that I could build a Pants wheel on an arm machine and get it to our hosted PyPI servers so that my engineers could use Pants in our Python monorepo checkout on arm machines.
w
yes, it should! there have already been two 2.13.x alpha releases though, if you want to try it out:
2.13.0a1
in particular.
f
thanks, this is great. I'll see if I'd be able to make necessary changes in the build-support/bin scripts to produce a "stable" release version of
2.13
(the idea is that we'll have 2.13 published in a local hosted PyPI which arm users will be able to pull and the rest would go to the global PyPI seamlessly)
w
sounds good. if you make further changes to the scripts, those will need to be cherry-picked though: probably fine, depending on how significant they are
@bitter-ability-32190: um, maybe? 2.13 has taken a while to stabilize, and cutting the 2.14 branch is probably around two weeks away at this point. it seems pretty low risk though.
f
oh sorry, I wasn't clear -- I'll make those changes locally only to cheat to force the scripts think I am building a stable release 2.13 (from my past experiments it has been adding git describe string to the version). I don't indent to submit any changes to those scripts upstream
👍 1
b
2.13 holds a lot of removal of in-repo plugins for me 🤞