-
Notifications
You must be signed in to change notification settings - Fork 167
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
A new release and a CHANGELOG? #281
Comments
@jeremywadsack our gem release process is undergoing change. We plan a new release, hope I can update on that soon. CC @cben |
One question I'd love feedback on is how useful a "stable" release branch with cherrypicks is at all? |
Yeah, that last commit is confusing:
Too bad GitHub UI doesn't show CommitDate when != AuthorDate. If you look at history prior to that commit https://github.com/abonas/kubeclient/commits/v2.5.1 you'll see the merged commits are recent. |
Interim update:
We started labeling PRs with "v2.x/yes" and "v2.x/no". I'll post a summary when that's done. |
@cben That sounds great. Thanks for all the work on this (to the whole team). To your earlier question (that I somehow missed), I'm not sure I understand what you're asking, but I'm preferential to regular releases, with semantic versioning. If I don't want to address breaking changes on my end, I can always pin the dependency in my |
After some indecision on #289 on small vs large compatible release, we settled on releasing master as 3.0.0 first. |
If anyone has specific preferences on what you want in 2.x release(s), please share. |
Version bump for 3.0.0 release (#281)
tagged & released v3.0.0 from master 🎉 |
Also working on small v2.5.2 release: #287, #301, #302, #303. The fixes we'll include in v2.5.2 (https://github.com/abonas/kubeclient/blob/v2.x/CHANGELOG.md):
I'm shelving the large 2.6 attempt (#289) for now. |
tagged & released v2.5.2 🎉 |
The releases on
rubygems
are confusing.Version 2.5.1 says it was released on 2017-10-12, but the tag shows the latest commit was 2017-05-09.
Lacking a
CHANGELOG
orHISTORY
document, it's hard to understand what changes are in each version and we're left with comparing releases and reading the commit statements (e.g. 2.3.0 to 2.5.1).It would be really helpful to have a log of changes for each release. :)
It would also be nice to have a new release as there have been lots of changes, some of which were merged over a year ago.
The text was updated successfully, but these errors were encountered: