Closed Datseris closed 1 year ago
Thankfully, no cherry picking was necessary. The history was linear. I have pushed online the branch v2.8 immediatelly after merging in #267 . I can tag if @kahaaga is okay.
Everything on master should be backwards-compatible, so releasing 2.8 immediately should be fine. Tag along, @Datseris!
Well I just learned that all of this wasn't necessary: I could have tagged directly from a commit ID. Anyways, here is the version tag: https://github.com/JuliaRegistries/General/pull/88392
I need
allprobabilities
for another paper I am writing. Given the recent suggestions of adding more stuff, I can't afford to wait for the 3.0 release because I plan to submit this paper on Friday and reviewing all extra information measure / probabilities estimators API will take much longer.Hence, I would like to release a 2.8 version with
allprobabilities
. My plan for this is to branch out from the latest tag of 2.7.2. Then, add theallprobabilities
function by cherry picking the corresponding PR. Then, push the branch 2.8, and tag a release from this branch instead ofmain
branch.