Skip to content
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

Better release notes/Upgrade paths? #132

Open
imbeyondboredom opened this issue Oct 12, 2017 · 2 comments
Open

Better release notes/Upgrade paths? #132

imbeyondboredom opened this issue Oct 12, 2017 · 2 comments
Assignees

Comments

@imbeyondboredom
Copy link

I love that you guys are iterating fast but as someone who is trying to maintain their own tools it makes it really hard to keep everything up to date when the release notes are: "Auto release"

In particular if releases just specified something like this it would help:
"Behavior from com.this.Class moved to com.this.OtherClass"

In this case I was using buildToolHelper.waitForHub and that was moved to assertBomImportScanStartedThenFinished which I only found because ReportRequestServiceTestIT still had waitForHub in it

@stavvy-akamen
Copy link

@imbeyondboredom we are open to the idea of automating this somehow, but we did the auto release to speed up the manual clicking of the release. If there was some way to publish the changes automatically we would be happy to!

@AtzDT
Copy link

AtzDT commented Feb 21, 2019

Maybe a short summary for new major versions wouldn't be too much manual work. This would also help to keep up to date on what is going on in this project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants