> Is there any important fix which must be included?

Recently there was some discussion here about incompatible changes to
Ratis since 1.0.  Nicholas mentioned that the next release could be
2.0 instead of 1.1 and declare it's not fully backward compatible.  Is
the async API stable now so that we can avoid the same situation soon
after the next release?  (There are some outstanding PRs related to
it.)  Or would it make sense to cut a release branch for 1.1 without
changes related to RATIS-979 and apply other fixes?

thanks,
Attila

Reply via email to