-
Notifications
You must be signed in to change notification settings - Fork 484
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
Tag 2.3 Release #128
Comments
The following test files I so far haven't "modernized":
'ConvolutionTests.swift' looks fine to me, but 'HyperbolicTests.swift' and 'TrigonometricTests.swift' still have tests & benchmarks combined, which I would like to split up/clean up. And I'd want to update the README's inventory, adding any missing Other than that I think we're in a good shape for a 2.3 🙂. |
@mattt With the issues of above comment fixed by now I'd say v2.3 is good to go. 👍 |
I think this is a great opportunity to revisit our release process. I don't want to hold things up too much, and maybe these are things that we can defer to 2.3.1 or 3.0, but here's what I'd like to see at some point:
@regexident Do you have strong opinions about any of these? Anything else you'd like us to incorporate as part of our release process? |
👌 🎉 In theory aggregating the release notes should result in the change log, but keeping an actual As such
If we were to use the https://keepachangelog.com/en/1.0.0/ "standard" for Alternatively one could simply link from the release note to the corresponding section of I have no experience with automating Github releases though, so just guessing. All of this sounds like a good candidate for adding a While we're at that we might as well add |
Github Actions? 🤔 |
|
For 2.3.0 I opted to do things manually for now. (Cocoapods has been updated, too.) There are however a few actions that look like they could come in handy, most notably:
|
With Xcode 11 and Swift 5.1 now officially released, and with so many improvements and additions to the library, I think now would be a great time to cut a new minor release.
@regexident Is there any work still pending that you'd like to include in 2.3?
The text was updated successfully, but these errors were encountered: