https://pantsbuild.org/ logo
Join Slack
Powered by
Are there any workarounds for the release note con...
# development
p
Are there any workarounds for the release note conflicts so auto cherry-pick can work? I'm afraid I'll have to cherry-pick manually: https://github.com/pantsbuild/pants/pull/21047#issuecomment-2176678148
✅ 1
f
I have a PR which may partially fix the issue. https://github.com/pantsbuild/pants/issues/21015
But no time currently to finish it off.
And it does not solve the issue of updating the release notes specific to the branch.
p
I think 
towncrier
or similar will be the most robust fix for these issues. 😞 Oh well. I'll cherry pick manually for now.
Hmm. Everything in 
docs/notes
or 
src/python/pants/notes
is for the 
.0
release, not for point releases. Is there somewhere for point release notes to go? Or does the release manager just have to compile those in the github releases page?
I just added 
release-notes:not-required
on https://github.com/pantsbuild/pants/pull/21086 ... Is that the right thing to do for a cherry-pick PR?
b
That one is going into 2.22, which technically hasn’t had 2.22.0 released yet, so mentioning it in the release notes might be good, in a perfect world, but I don’t think it’s critical
p
Oh. Ok. I'll add it.
b
Sorry for the confusion. I agree Towncrier would be a good approach. (Unfortunately ive been spending all my pants time on process/infra things recently, and need a break from that.)
p
Could I get an approval on these cherry-pick PRs? I had to do them since the bot was unable to, so I can't approve them. https://github.com/pantsbuild/pants/pull/21084 https://github.com/pantsbuild/pants/pull/21085 https://github.com/pantsbuild/pants/pull/21086
✅ 1
Open in Slack
PreviousNext
Powered by