On Mon, Aug 3, 2015 at 11:31 PM, Emmanuel Lécharny <[email protected]> wrote:
> Le 03/08/15 16:58, Zheng, Kai a écrit : > > I just thought of another two items to do for the release. They came to > my mind during related discussions. > > 1. Double check all the left issues/JIRAs. If not must to have, we can > retarget them for 1.0.0-rc2, 1.0.0, and 2.0.0 accordingly. > > 2. Mavibot backend, it still relying on SNAPSHOT version of Mavibot. If > sounds good, how about retargeting it for 1.0.0, and move it out of the > release? > > > > Kiran, would you comment on this? Thanks. > We can cut a release of Mavibot, but it will be a Milstone, not a RC. In > we can cut a release > any case, if needed, we can either discard the Mavobot backend, or if we > have a RC for Mavinot, use it. > > IMHO mavibot backend is a must, cause this is the only embeddable simple persisting <K,V> store present in Kerby, the other stores are either in-memory or run in a separate process. -- Kiran Ayyagari http://keydap.com
