Closed martinholters closed 5 years ago
I've used the script from JuliaLang/Pkg.jl#1133 but curiously had to fix to dependency UUIDs
Those don't have METADATA compatible UUIDs so should be special cased in the script. Edit: https://github.com/JuliaLang/Pkg.jl/pull/1138
I've set the version to 2.1.1-DEV here
Just set it to 2.1.0 IMO and then when the next release is about to happen we bump to 2.2.0 or 2.2.1 or w/e is appropriate.
Just set it to 2.1.0 IMO and then when the next release is about to happen we bump to 2.2.0 or 2.2.1 or w/e is appropriate.
Right, that seems much simpler.
This adds a
Project.toml
(again) as it will be needed for registering future versions. While at it, I noticed that we had atest/REQUIRE
file pulling inOffsetArrays
which wasn't used anymore, so I've removed that.I've used the script from https://github.com/JuliaLang/Pkg.jl/pull/1133 but curiously had to fix to dependency UUIDs, cc @StefanKarpinski, see second commit. Note that I've used the script, but the Pkg version from
1.2.0-DEV.629
, not Pkg master, if that's a problem.I've set the version to
2.1.1-DEV
here, expecting it to be bumped to2.2.0-DEV
when the first new feature is added and then to2.2.0
for the next release. (Assuming we're not doing a bugfix release 2.1.1.) The commit that sets version to2.2.0
should then be registered and the very next commit bump the version to2.2.1-DEV
. That workflow sounds tedious and error-prone, so suggestions welcome.