Hi <@U06A03HV1>, we just landed another change to ...
# announce
w
Hi @witty-crayon-22786, we just landed another change to junit runner - https://github.com/pantsbuild/pants/commit/9c9e3ccfe5ccb65d8eec3cc38ad34cb251f73601 Would it be possible to publish it from 1.25.x-twtr branch this time? since there’s no where for it to land on master now.
w
should be able to, yea.
@wide-energy-11069: do you have access? i forget
w
not to maven central, no
happy to run it myself if access granted
w
i’ll do it. you folks might consider moving that code internally and bootstrapping it maybe
but lemme see
w
yeah that’s not a bad idea
cc @fancy-queen-20734
w
on what kind of timeline do you need this? bootstrapping from scratch in that branch is taking some time
f
We could also cherry-pick & publish it from 1.30.x if that's easier
it'd be nice to have it in the next couple weeks
w
ah, sorry: i just meant “is after hours ok?”
f
yeah, that would be fine
w
looks like it won’t be more than another 30 minutes though, can do it now.
👍 1
💯 1
f
thx
Would we want to cherry pick these into the 1.30.x branch, or if folks need JDK 11 support while v2 doesn't support the JVM are you planning on pointing people at 1.25.x-twtr?
w
we won’t point anyone at 1.25.x-twtr, unless you want us to. if this cherry-picks cleanly to 1.30.x, then it wouldn’t hurt to do so.
f
k
w
the special case to publish it (ie: “not from master”) applies equally in both cases i think.
f
yeah, that's fair
w
actually, things get a bit too crazy if we don’t cherrypick things. as an example, 1.30.x already had one more release commit than 1.25.x
the publish is about to complete:
0.0.10
should be available in about 20 minutes