New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added release-drafter.yml #850
Added release-drafter.yml #850
Conversation
I think there's definitely something here to explore more!
Just some early thoughts. Thank you so much for your contribution! |
Greetings of the day @daxpryce,
In my humble opinion we can do it in two ways :
What do you suggest ? Thanks & Regards |
I was talking to @bdpedigo about this a few weeks ago where I suggested we use the PR title as the release notes bullet, and then be diligent about keeping our PR titles "release notes worthy". I suggested something like:
If we do that, then we can rely on the PR titles to form the release notes. I'm still not sure how to make release drafter prepend these changes to the On top of that, rst is a pain in the butt 99 times out of 98, so I'm disgruntled just thinking about it. Meh. Anyway, I don't have any direction yet. Let's treat this as a good conversation spot for now and try to come up with something that works for our release as it is. There's a possibility we could simplify the release-drafter portion by leaning on releases through Github more vs. our current implicit "prereleases happen when we merge to dev, releases happen when we merge to main" strategy. I just... don't want to rework everything right now, since I'm kinda strapped for time. Is it okay if we a: keep talking and b: pause if we have to do any major rework of the CICD stuff for it? (Aside, this is why release engineering is such a pain - it's like an infinite yarn pull of an infinite sweater. It. Never. Stops.) |
Greetings of the day @daxpryce, I've been researching on automating release notes the conclusion is as follows :
An implementation of it could be found here. Thanks & Regards |
@jonmclean can you take a look into this and see how, if at all, we could get it to work with our new flow now? @shikharvashistha was very helpful and if we can end up using this or modifying it to work with our new doc generation system that would be a very nice thing |
Reference Issues/PRs #842
What does this implement/fix? Briefly explain your changes.
Greetings of the day @daxpryce,
I would suggest using release_drafter for automating release notes. Please review the pr and let me know in case of any changes/suggestions if required.
Reference : here
Thanks & Regards
@shikharvashistha