-
Notifications
You must be signed in to change notification settings - Fork 97
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 non-breaking release of BenchmarkTools.jl? #344
Comments
PS: I tried to maintain this package for a while but I clearly don't have the bandwidth, so once I get those changes release I'll step aside for a good long while |
Looking at https://juliahub.com/ui/Search?q=leaves&type=symbols&u=use I don't see any use of (the relevant) |
then I propose we release 1.4.0 |
doing it now since there has not been an objection |
Since the last release, there have been 3 commits that I deem possibly breaking:
BenchmarkGroup
on access #309 => makes it easier to overwrite existing benchmark groups without noticing, but arguably this is a bad practice anywayIn my view, semantic versioning is slightly looser when it comes to dev-facing packages like BenchmarkTools.jl, and so we could tag a non-breaking release. What do other people think?
The text was updated successfully, but these errors were encountered: