I would like to bump this thread up.
What do we need for a new release?
As I see we have 5 patch available tasks:
- the ratis site is unrelated but I prefer to publish it soon
- I created two release releated one: RATIS-173/RATIS-174 (create binary
release artifact/ignore some javadoc warnings).
- 2 other: RATIS-140/RATIS-160
Question: Do you see any other outstanding issue which should be
included in a release?
I propose to wait for the merge of these tasks and create a 0.2.0
release after that.
I would be happy to go through on the mechanical part of releasing
process (and document all the required steps for the next releases)
Marton
On 10/12/2017 06:12 AM, Mingliang Liu wrote:
+1
On Oct 10, 2017, at 8:15 PM, Tsz Wo Sze <[email protected]> wrote:
It has been more than 4 months after the 0.1-alpha release. After
that, we have some API change (introducing RaftGroup) and a few bug
fixes. How about we roll a 0.2-alpha release?
Tsz-Wo
