Given the decision in <https://pantsbuild.slack.co...
# development
h
Given the decision in https://pantsbuild.slack.com/archives/C0D7TNJHL/p1650042070758419?thread_ts=1647036837.835999&amp;cid=C0D7TNJHL to not spend more time on Code gen for JVM in 2.11, fyi our blockers for stabilization: • documentation ◦ buf ◦ go protobuf ◦ pex lockfiles • finish release blog (almost done!) • pex blog • multiple resolves ux (error messages)
w
@hundreds-father-404 and i talked about this a bit more, and we think that we should probably timebox 2.11.0 to sometime next week (subject to discussion, and obviously discovery of any blocker bugs) (discussion in thread…)
i think that aiming to do a final release Wednesday night / Thursday morning might make sense from a “time left to deal with pre/post launch surprises” perspective
👍 2
h
I will do a release today after 2 cherry-picks - I want to get out the pex lock file performance fix
@happy-kitchen-89482 if you have an extra cycle, it may help to do https://github.com/pantsbuild/pants/issues/13612. It would be good to fix in 2.10 and 2.11 Stu and I discussed that I personally focus for now on the documentation because it blocks the release, whereas this bug fix + multiple resolves UX are only "good to have"
h
Funny, I was going to tackle that as a side project on the flight
Great minds think alike
💪 1