RCs for active branches:
- <https://github.com/pan...
# developmentc
curved-manchester-66006
11/05/2025, 9:26 PMRCs for active branches:
• https://github.com/pantsbuild/pants/pull/22858
• https://github.com/pantsbuild/pants/pull/22859
• https://github.com/pantsbuild/pants/pull/22860
We are in this pattern where we are doing releases off these branches at the same rate as we are backporting, we we never get past an RC release. If nothing comes up, I'll probably do another round Friday to break that chain.
👍 2
curved-manchester-66006
11/07/2025, 7:59 PMRelease a-paolooza
• https://github.com/pantsbuild/pants/pull/22867
• https://github.com/pantsbuild/pants/pull/22868
• https://github.com/pantsbuild/pants/pull/22869
• https://github.com/pantsbuild/pants/pull/22870
• https://github.com/pantsbuild/pants/pull/22871
After this, I'd like to close the 2.27.x and 2.28.x milestones. We don't have this written down as something formal, but they are old at this point and this is a lot of branchs.
🚢 1
f
fast-nail-55400
11/07/2025, 10:42 PMI'm fine with at least 2.27.x being closed. 2.28.0 was released in September so maybe we should leave it open for more than two months? 2.27.0 is from June so seems fine to close since it is more like 6 months open.
h
happy-kitchen-89482
11/09/2025, 4:46 AMI concur re closing 2.27.x
happy-kitchen-89482
11/09/2025, 4:46 AMBut I would wait on 2.28.x since it seems odd to close two release branches at the same time
4 Views