Update CHANGELOG.md and gem version for 3.0.0 release #244
Conversation
Sinjo
force-pushed
the
sinjo-release-3.0.0
branch
2 times, most recently
from
a3fea5f
to
ddb3035
Compare
Sinjo
force-pushed
the
sinjo-release-3.0.0
branch
2 times, most recently
from
4b68d99
to
ddb3035
Compare
Includes the changes in `master` that we'll release in `2.2.0`, and the ones that we can't because of breaking changes, which we'll release in `3.0.0` Signed-off-by: Daniel Magliola <dmagliola@crystalgears.com>
Sinjo
force-pushed
the
sinjo-release-3.0.0
branch
from
ddb3035
to
966301a
Compare
Signed-off-by: Chris Sinjakli <chris@sinjakli.co.uk>
Signed-off-by: Chris Sinjakli <chris@sinjakli.co.uk>
Signed-off-by: Chris Sinjakli <chris@sinjakli.co.uk>
Sinjo
force-pushed
the
sinjo-release-3.0.0
branch
from
966301a
to
e213a71
Compare
|
@dmagliola One question before we merge this: do you think it's worth us putting a release candidate out given the number of changes? I'm thinking it might be worth it if we also post it on prometheus-announce so that there's more chance of people giving it a go. Equally, I know how reticent people are to use software that's labelled as a release candidate (but would be totally fine with using if it were a proper release), which limits their value. |
|
I've taken a look at the changes which we introduced, and I feel like we can be fairly confident that they'll work. I'd put out a release candidate if we ever merge lzap's change to the DirectFileStore, that kind of change seems more like something that could have hard-to-predict implications. What we've done in these commits is the kind of thing that is pretty testable, and it's tested. I think we can release as 3.0.0, to be honest. |
@dmagliola I've pulled in your work from #228, which we were going to use to cut an interim 2.2.0 release, and combined it all into one big section for the 3.0.0 release which we decided to go with instead.
Fixes #241