Re: [DISCUSS] Apache Ratis 0.6.0 release

[Tsz Wo Sze]

+1 for the GA release!
Tsz-Wo

On Wed, Jun 3, 2020 at 12:46 AM Lokesh Jain  wrote:

> Yes, +1 for GA release.
>
> > On 03-Jun-2020, at 1:02 PM, Mukul Kumar Singh 
> wrote:
> >
> > Thanks for starting the discussion thread.
> >
> > How about the next release of Ratis be a GA release?
> >
> > Thanks,
> >
> > Mukul
> >
> > On 03/06/20 12:35 pm, Lokesh Jain wrote:
> >> Hi,
> >>
> >> It has been a while since our last Ratis release.
> >> We have around 95 commits after our latest 0.5.0 release.
> >>
> >> How about we start the process for a new Ratis release (0.6.0)?
> >>
> >> Thanks,
> >> Mukul
>
>

Re: [DISCUSS]Ratis Thirdparty Release 0.4.0

[Tsz Wo Sze]

+1  Thanks a lot for taking care this.
Tsz-Wo

On Thu, Apr 16, 2020 at 10:42 AM Xiaoyu Yao  wrote:
>
> +1
>
> On Thu, Apr 16, 2020 at 9:57 AM Siddharth Wagle 
> wrote:
>
> > +1
> >
> > On Thu, Apr 16, 2020 at 9:22 AM Arpit Agarwal
> > 
> > wrote:
> >
> > > +1
> > >
> > >
> > > > On Apr 16, 2020, at 2:01 AM, Lokesh Jain 
> > > wrote:
> > > >
> > > > +1
> > > >
> > > >> On 16-Apr-2020, at 2:21 PM, Mukul Kumar Singh <
> > mksingh.apa...@gmail.com>
> > > wrote:
> > > >>
> > > >> Hi,
> > > >>
> > > >>
> > > >> With RATIS-847 and RATIS-852 fixed, I propose to create a new release
> > > for Ratis Thirdparty.
> > > >>
> > > >> I would like to get everyone's thoughts on this.
> > > >>
> > > >>
> > > >> Thanks,
> > > >>
> > > >> Mukul
> > > >>
> > > >
> > >
> > >
> >

Re: [Discussion] Ratis dealing with flakey I/O

[Tsz Wo Sze]

Hi Clay,

Thanks a lot for working on this.  The approach in general looks good
to me.  As you mentioned, wrapping with FailSafe may make the code
ugly.  Also, it may be undesirable for Ratis becoming tightly coupled
with FailSafe   How about we do the following:

(1) Refactor the code so that all the system calls are moved to one
place (e,g. all the file related calls should use FileUtils.  We may
do something similar for the other system calls)
(2) Add retry support.  I prefer using our own RetryPolicy instead of
FailSafe.  I am open to make it pluggable/configurable.

How does that sound?

Tsz-Wo

On Tue, Nov 12, 2019 at 4:26 PM Clay B.  wrote:
>
> Hi Ratis Folks!
>
> I've been hacking on RATIS-695 - "Improve running in the face of flaky
> disks"[1] and I've gotten to the point I can run Ratis with 60% of I/O
> requests resulting in an `IOException` and the example server and
> arithmetic client can make forward progress and record consistent data.
>
> I have lots of questions which it seems wrong to keep to myself. I
> want to ensure that this patch does not risk making the code ugly or less
> maintainable. I/O in Ratis is not super tightly encapsulated and I'm
> touching 16 files.
>
> Right now, I am wrapping each I/O operation with a FailSafe object. Do
> folks have an opinions on a better Java construct to not risk code
> becoming bloated or ugly? There are some threading assumptions to these
> FailSafe object; they default to the ForkJoin pool's common thread
> pool[2].
>
> Similarly, do folks think this is a reasonable approach or am I making
> assumptions that may limit consumers' choices to incorporate Ratis? I am
> trying to keep all changes mostly kept to Ratis and at worst provide easy
> APIs for consumers to use.
>
> This patch would push to Ratis to protecting itself with retrying all
> (failing) I/O requests. What social or code construct may help ensure
> going forward new Ratis changes to continue to use this construct as
> changes to I/O happen? Perhaps, simply ensuring Jenkins runs the Namazu
> I/O fuzzing test and ensures it can write a specific amount of data okay?
>
> If you think this is a wrong direction, what approach would you prefer? An
> alternative I've considered is we pursue an architecture like Zookeeper
> which uses annotations on "critical threads". If a critical thread dies,
> the daemon will exit. However, a limitation to this approach would be us
> enforcing a requirement that consumers depending on Ratis follow this too.
> Second challenge would be MITT would be much longer than a function retry.
>
> I am curious what other's opinions are? Does anyone think this is the
> completely wrong approach or a reasonable approach?
>
> -Clay
>
> [1]: Pull request:
> https://github.com/apache/incubator-ratis/pull/45
> [2]: FailSafe schedulers description:
> https://jodah.net/failsafe/schedulers/

Re: [DISCUSS] 0.3.0 Ratis Thirdparty release

[Tsz Wo Sze]

+1  Thanks a lot.
Tsz-Wo

On Wed, Oct 30, 2019 at 11:51 AM Xiaoyu Yao  wrote:
>
> +1.
>
> Thanks!
>
> On Wed, Oct 30, 2019 at 9:10 AM Josh Elser  wrote:
>
> > Sounds good! Let's get an RC rolling :)
> >
> > On 10/30/19 10:57 AM, Arpit Agarwal wrote:
> > > +1
> > >
> > > Thanks for kicking this off Mukul.
> > >
> > >
> > >> On Oct 30, 2019, at 4:59 AM, Mukul Kumar Singh <
> > mksingh.apa...@gmail.com> wrote:
> > >>
> > >> Hi Ratis Dev,
> > >>
> > >>
> > >> With the discussion of Ratis 0.5.0 release in progress.
> > >> With Ratis-407 committed, a new thirdparty release is needed.
> > >>
> > >> This thread discusses a new ratis-thirdparty release so that grpc and
> > protobuf and netty versions can be updated in Ratis.
> > >>
> > >>
> > >> Thanks,
> > >>
> > >> Mukul
> > >>
> > >
> >

Re: [DISCUSS] 0.5.0 release

[Tsz Wo Sze]

Thanks everyone.

RATIS-407 is now committed.  Please let me know if there are specific
issues you like to include.  Otherwise, will roll a release later this
week or early next week.

Tsz-Wo

On Fri, Oct 25, 2019 at 2:19 PM Xiaoyu Yao  wrote:
>
> +1. Thanks for fixing those critical issues after 0.4.0.
>
> -Xiaoyu
>
> On Fri, Oct 25, 2019 at 11:04 AM Andy Wu  wrote:
>
> > +1. Since 0.4.0 is not usable, a release of 0.5.0 asap will be greatly
> > appreciated. Let me know if I can help in any way.
> >
> > On Thu, Oct 24, 2019 at 9:03 PM Mukul Kumar Singh <
> > mksingh.apa...@gmail.com>
> > wrote:
> >
> > > Lets also get https://issues.apache.org/jira/browse/RATIS-407 in for
> > > 0.5.0 as well.
> > >
> > > Thanks,
> > >
> > > Mukul
> > >
> > >
> > > On 25/10/19 3:31 am, Jitendra Pandey wrote:
> > > > +1, we have made several fixes and improvements as well.
> > > >
> > > > On Thu, Oct 24, 2019 at 2:58 PM Tsz Wo Sze  wrote:
> > > >
> > > >> Hi Ratis Dev,
> > > >>
> > > >> As reported by Henrik Hegardt and Andy Wu, Ratis 0.4.0 release has a
> > > >> NoClassDefFoundError:
> > > >> org/apache/hadoop/metrics2/lib/DefaultMetricsSystem problem.
> > > >> Therefore, we suggest rolling out 0.5.0 release as soon as possible.
> > > >> Any thought?
> > > >>
> > > >> Tsz-Wo
> > > >>
> > >
> >

[DISCUSS] 0.5.0 release

[Tsz Wo Sze]

Hi Ratis Dev,

As reported by Henrik Hegardt and Andy Wu, Ratis 0.4.0 release has a
NoClassDefFoundError:
org/apache/hadoop/metrics2/lib/DefaultMetricsSystem problem.
Therefore, we suggest rolling out 0.5.0 release as soon as possible.
Any thought?

Tsz-Wo

Re: Custom message serialization

[Tsz Wo Sze]

Hi Alexey,

I believe we are open to custom message serialization, especially,
Ratis is designed to be highly pluggable.  Indeed, it is a good time
to do so since we still do not yet need worry about backward
compatibility, since Ratis is still not yet GA.  Recently we do see
some weakness in Protobuf such as unnecessary buffer copying in some
cases.

It would be great if you could contribute in Ratis!  Contributions are
always welcome.  :)

Thanks for reaching out.
Tsz-Wo


On Fri, Oct 4, 2019 at 2:10 AM Alexey Goncharuk  wrote:
>
> Hello Ratis community, a fellow Apache member here :)
>
> I am currently researching an option to integrate a consensus module for
> Apache Ignite, mostly as metadata storage and group membership service in
> the beginning. I could not help noticing that there is a neighbor Apache
> project that looks very promising.
>
> I am just getting started and see that the messaging layer is separated
> from the core Raft algorithm implementation, but the message definitions
> and serialization are Google Protobuf-generated. In Ignite, we have a
> custom serialization protocol and try to keep the core module as small
> as possible, so the protobuf dependency does not quite fit our project.
>
> I was wondering if you have any plans for abstracting the serialization
> layer as well, or perhaps would accept a contribution that implements such
> a separation (after the design is discussed here, of course)? Or, perhaps,
> I missed something and I can plug custom messages to the Ratis core somehow?
>
> Thanks in advance,
> --Alexey Goncharuk

Re: ClassNotFoundException in Ratis

[Tsz Wo Sze]

> ... updating so ratis-metric is depending directly on the 3.1.2 ...

Sound great.  Thanks for digging it out!  Let's continue the
discussion in RATIS-699.

Tsz-Wo


On Wed, Oct 2, 2019 at 5:18 AM Henrik Hegardt
 wrote:
>
> Hi Tsz-Wo,
>
> Thank you for your reply. I've been checking up on this a little bit
> more and I believe the CNFE is my fault because I was trying to fix
> another problem, which I'm going to try to explain:
>
> Ratis-Metric is depending on the dependency
> com.github.joshelser:dropwizard-metrics-hadoop-metrics2-reporter: 0.1.2.
> This in turn depends on the org.apache.hadoop:hadoop-common:2.6.0. This
> in turn depends on org.apache.hadoop:hadoop-annotations:2.6.0 which have
> an dependency on a system scoped dependency named jdk.tools:1.6. I'm
> running java 11 and this dependency doesn't exist in my environment so I
> can't compile with ratis included in my project because it fails trying
> to resolve that dependency.
>
> However, the project ratis-hadoop depends on the the dependency
> org.apache.hadoop:hadoop-common:3.1.1 (which should be upgraded to 3.1.2
> because the sources are missing in 3.1.1) which doesn't have the
> jdk.tools:1.6 dependency. So if I depend on this I can build the project
> because the faulty 2.6.0 dependency is shadowed transitively by the
> 3.1.1 dependency and everything is compiling.
>
> The simple fix would be updating so ratis-metric is depending directly
> on the 3.1.2 dependency instead since it effectively will be the 3.1.1
> code you are going run with anyway when running with the ratis-hadoop
> dependency. I can open a bug for this.
>
> I also have a question; right now there's a dependency on
> io.dropwizard.metrics:metrics-core:3.2.5. It seems like there's an idea
> that the metric loader functionality should/would be more pluggable
> through the serviceloader API? Is this correct? I was merely thinking
> that the ratis-metric project should be less opinionated on what library
> one should use to measure things? I am willing to look into this if
> needed and see if I can do anything about it.
>
> I'm using dropwizard-metrics:4.0.5 which isn't compatible with the
> current ratis-metrics implementation, and unfortunately I cannot
> downgrade. I'd love to use ratis in my project, but this is something I
> need to fix to be able to use it.
>
> /Henrik
>
> Den 2019-10-01 kl. 00:05, skrev Tsz Wo Sze:
> > Hi Henrik,
> >
> > Thanks for reporting the problem.
> > org.apache.ratis.metrics.MetricsReporting imports
> > org.apache.hadoop.metrics2.lib.DefaultMetricsSystem,  I guess it is
> > causing the ClassNotFoundException.  It is a bug. Do you want to file
> > a JIRA?
> >
> > Tsz-Wo
> >
> > On Mon, Sep 30, 2019 at 2:23 AM Henrik Hegardt
> >  wrote:
> >> Hi everyone,
> >>
> >> I'm getting this error while running Ratis:
> >>
> >> Caused by: java.io.IOException: java.lang.NoClassDefFoundError:
> >> org/apache/hadoop/metrics2/lib/DefaultMetricsSystem
> >>   at org.apache.ratis.util.IOUtils.asIOException(IOUtils.java:54)
> >>   at org.apache.ratis.util.IOUtils.toIOException(IOUtils.java:61)
> >>   at org.apache.ratis.util.IOUtils.getFromFuture(IOUtils.java:70)
> >>   at
> >> org.apache.ratis.server.impl.RaftServerProxy.getImpls(RaftServerProxy.java:284)
> >>   at
> >> org.apache.ratis.server.impl.RaftServerProxy.start(RaftServerProxy.java:296)
> >>   at test.cluster.ClusterSevice.start(ClusterSevice.java:85)
> >>   ... 65 more
> >> Caused by: java.lang.NoClassDefFoundError:
> >> org/apache/hadoop/metrics2/lib/DefaultMetricsSystem
> >>   at
> >> org.apache.ratis.metrics.MetricsReporting.(MetricsReporting.java:42)
> >>   at
> >> org.apache.ratis.server.metrics.RatisMetrics.(RatisMetrics.java:39)
> >>   at
> >> org.apache.ratis.server.raftlog.segmented.SegmentedRaftLogWorker.(SegmentedRaftLogWorker.java:176)
> >>   at
> >> org.apache.ratis.server.raftlog.segmented.SegmentedRaftLog.(SegmentedRaftLog.java:197)
> >>   at
> >> org.apache.ratis.server.raftlog.segmented.SegmentedRaftLog.(SegmentedRaftLog.java:183)
> >>   at
> >> org.apache.ratis.server.impl.ServerState.initRaftLog(ServerState.java:188)
> >>   at
> >> org.apache.ratis.server.impl.ServerState.(ServerState.java:120)
> >>   at
> >> org.apache.ratis.server.impl.RaftServerImpl.(RaftServerImpl.java:110)
> >>   at
> >> org.apache.ratis.server.impl.RaftServerProxy.lambda$newRaftServerImpl$2(RaftServerProxy.java:208)
> &

Re: ClassNotFoundException in Ratis

[Tsz Wo Sze]

Hi Henrik,

Thanks for reporting the problem.
org.apache.ratis.metrics.MetricsReporting imports
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem,  I guess it is
causing the ClassNotFoundException.  It is a bug. Do you want to file
a JIRA?

Tsz-Wo

On Mon, Sep 30, 2019 at 2:23 AM Henrik Hegardt
 wrote:
>
> Hi everyone,
>
> I'm getting this error while running Ratis:
>
> Caused by: java.io.IOException: java.lang.NoClassDefFoundError:
> org/apache/hadoop/metrics2/lib/DefaultMetricsSystem
>  at org.apache.ratis.util.IOUtils.asIOException(IOUtils.java:54)
>  at org.apache.ratis.util.IOUtils.toIOException(IOUtils.java:61)
>  at org.apache.ratis.util.IOUtils.getFromFuture(IOUtils.java:70)
>  at
> org.apache.ratis.server.impl.RaftServerProxy.getImpls(RaftServerProxy.java:284)
>  at
> org.apache.ratis.server.impl.RaftServerProxy.start(RaftServerProxy.java:296)
>  at test.cluster.ClusterSevice.start(ClusterSevice.java:85)
>  ... 65 more
> Caused by: java.lang.NoClassDefFoundError:
> org/apache/hadoop/metrics2/lib/DefaultMetricsSystem
>  at
> org.apache.ratis.metrics.MetricsReporting.(MetricsReporting.java:42)
>  at
> org.apache.ratis.server.metrics.RatisMetrics.(RatisMetrics.java:39)
>  at
> org.apache.ratis.server.raftlog.segmented.SegmentedRaftLogWorker.(SegmentedRaftLogWorker.java:176)
>  at
> org.apache.ratis.server.raftlog.segmented.SegmentedRaftLog.(SegmentedRaftLog.java:197)
>  at
> org.apache.ratis.server.raftlog.segmented.SegmentedRaftLog.(SegmentedRaftLog.java:183)
>  at
> org.apache.ratis.server.impl.ServerState.initRaftLog(ServerState.java:188)
>  at
> org.apache.ratis.server.impl.ServerState.(ServerState.java:120)
>  at
> org.apache.ratis.server.impl.RaftServerImpl.(RaftServerImpl.java:110)
>  at
> org.apache.ratis.server.impl.RaftServerProxy.lambda$newRaftServerImpl$2(RaftServerProxy.java:208)
>  at
> java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700)
>  at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>  at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>  at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem
>  at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
>  at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
>  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
>  ... 13 more
>
> AFAICT this is a class in the dependency
> org.apache.hadoop:hadoop-common:3.1.1. I'm running with the dependencies
> and Ratis 0.4.0
>
> 
>  ratis-server
>  org.apache.ratis
>
>  
>  
>  log4j
>  log4j
>  
>  
>  org.slf4j
> slf4j-log4j12
>  
>  
>  
>  
>  ratis-grpc
>  org.apache.ratis
>  
>
> And which should be enough according to the documentation. While it's
> possible to include this dependency, it pulls in a lot of other
> dependencies. While org.apache.ratis.metrics.MetricsReporting class does
> have a dependency on the
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem class, ratis-metrics
> doesn't define a dependency to org.apache.hadoop:hadoop-common:3.1.1 in
> its pom. Is this intended or am I missing something?
>
> Thank you for all your efforts.
>
> /Henrik
>
>
>
>

Re: [VOTE] Apache Ratis incubating Release 0.4.0 rc1

[Tsz Wo Sze]

Thanks, Mukul for making the release.

https://issues.apache.org/jira/browse/RATIS-642 was reopened.  We
probably should fix the NOTICE file first.

Tsz-Wo


On Thu, Aug 1, 2019 at 12:31 PM Ankit Singhal  wrote:
>
> +1
>
> -- Built from the source - OK
> -- Hashes and Signatures[5]  - OK
> -- Ran unit tests - All passed
> -- Ran rat check on the source - OK
>
> Some comments:-
> * NOTICE[1] assembled in a binary tar doesn't include a NOTICE[2] from the
> project.
> * NOTICE[1] doesn't look exhaustive (eg:- No mention of Junit dependency
> "Eclipse Public License 1.0") under Could also use a supplemental
> model[4] for dependencies which have incomplete information about their
> NOTICE/LICENSE
> * same with LICENSE[3], for eg:- no mention of "Eclipse Public License - v
> 1.0"[4]
>
> [1]
> http://people.apache.org/~msingh/0.4.0-rc1/apache-ratis-incubating-0.4.0-rc1-bin.tar.gz
> [2] https://github.com/apache/incubator-ratis/blob/master/NOTICE
> [3]
> http://people.apache.org/~msingh/0.4.0-rc1/apache-ratis-incubating-0.4.0-rc1-bin.tar.gz
> [4]
> https://maven.apache.org/plugins/maven-remote-resources-plugin/supplemental-models.html
> [5] https://dist.apache.org/repos/dist/release/incubator/ratis/KEYS
>
> Regards,
> Ankit Singhal
>
> On Thu, Aug 1, 2019 at 11:02 AM Uma gangumalla  wrote:
>
> > +1 (binding)
> >
> > built from source
> > LICENCE and NOTICE files looks good.
> > Sig and hashes are fine
> >
> > Few test timeouts[1] came in my 'mvn clean install'. Probably that's only
> > to me as others might already ran tests and +1ed. ( Should not be a blocker
> > I guess, if they are passing with others env)
> >
> > Regards,
> > Uma
> >
> > [1]
> > [INFO] Results:
> > [INFO]
> > [ERROR] Failures:
> > [ERROR]
> >
> > TestRaftSnapshotWithGrpc>RaftSnapshotBaseTest.testBasicInstallSnapshot:220->RaftSnapshotBaseTest.assertLeaderContent:78
> > [ERROR]
> >
> > TestRaftReconfigurationWithNetty>RaftReconfigurationBaseTest.testReconfTwice:140->RaftReconfigurationBaseTest.runTestReconfTwice:192->RaftReconfigurationBaseTest.lambda$runTestReconfTwice$5:200
> > s3: ConfigurationManager, init=-1: [s0:0.0.0.0:50941, s1:0.0.0.0:45664,
> > s2:
> > 0.0.0.0:49625], old=null, confs={
> >   0 -> 0: [s0:0.0.0.0:50941, s1:0.0.0.0:45664, s2:0.0.0.0:49625], old=null
> >   41 -> 41: [s3:0.0.0.0:45637, s4:0.0.0.0:50873, s0:0.0.0.0:50941, s1:
> > 0.0.0.0:45664, s2:0.0.0.0:49625], old=[s0:0.0.0.0:50941, s1:0.0.0.0:45664,
> > s2:0.0.0.0:49625]
> >   43 -> 43: [s3:0.0.0.0:45637, s4:0.0.0.0:50873, s0:0.0.0.0:50941, s1:
> > 0.0.0.0:45664, s2:0.0.0.0:49625], old=null
> >   45 -> 45: [s3:0.0.0.0:45637, s4:0.0.0.0:50873, s2:0.0.0.0:49625],
> > old=[s3:
> > 0.0.0.0:45637, s4:0.0.0.0:50873, s0:0.0.0.0:50941, s1:0.0.0.0:45664, s2:
> > 0.0.0.0:49625]
> >   47 -> 47: [s3:0.0.0.0:45637, s4:0.0.0.0:50873, s2:0.0.0.0:49625],
> > old=null
> >   49 -> 49: [s3:0.0.0.0:45637, s4:0.0.0.0:50873, s2:0.0.0.0:49625],
> > old=null
> >   50 -> 50: [s3:0.0.0.0:45637, s4:0.0.0.0:50873, s2:0.0.0.0:49625],
> > old=null
> > } expected:<7> but was:<8>
> > [ERROR]
> >
> > TestRaftSnapshotWithNetty>RaftSnapshotBaseTest.testRestartPeer:146->RaftSnapshotBaseTest.assertLeaderContent:78
> > [ERROR]
> >
> > TestRaftLogMetrics.testFlushMetric:78->runTestFlushMetric:93->assertFlushCount:110
> > expected:<5> but was:<4>
> > [ERROR]
> >
> > TestRaftSnapshotWithSimulatedRpc>RaftSnapshotBaseTest.testBasicInstallSnapshot:220->RaftSnapshotBaseTest.assertLeaderContent:78
> > [ERROR] Errors:
> > [ERROR]
> >
> > TestRaftReconfigurationWithGrpc>RaftReconfigurationBaseTest.testReconfTimeout:207->RaftReconfigurationBaseTest.runTestReconfTimeout:217
> > » NullPointer
> > [ERROR]
> >
> > TestRequestLimitAsyncWithGrpc>RequestLimitAsyncBaseTest.testWriteElementLimit:65->RequestLimitAsyncBaseTest.runTestWriteElementLimit:119->BaseTest.getWithDefaultTimeout:168
> > » Timeout
> > [ERROR]
> >
> > TestRaftStateMachineExceptionWithNetty>RaftStateMachineExceptionTests.testRetryOnExceptionDuringReplication:177
> > » NullPointer
> > [ERROR]
> >
> > TestRaftStateMachineExceptionWithSimulatedRpc>RaftStateMachineExceptionTests.testRetryOnExceptionDuringReplication:177
> > » NullPointer
> > [INFO]
> > [ERROR] Tests run: 241, Failures: 5, Errors: 4, Skipped: 4
> >
> > On Mon, Jul 29, 2019 at 2:59 AM Mukul Kumar Singh <
> > mksingh.apa...@gmail.com>
> > wrote:
> >
> > > Hi Apache Ratis PPMC,
> > >
> > > I am calling a vote for Apache Ratis incubating Release 0.4.0 rc1.
> > > This vote is after fixing issues RATIS-642 & RATIS-621 in the rc0 vote.
> > >
> > > This is with respect to the discuss mailthread  <
> > >
> > https://lists.apache.org/thread.html/781fb6db8fe3327683f96b880496cf4b297f8666a2fab85c413c6f4b@%3Cdev.ratis.apache.org%3E
> > > >.
> > >
> > > The git tag to be voted upon:
> > >
> > >
> > https://gitbox.apache.org/repos/asf?p=incubator-ratis.git;a=shortlog;h=refs/tags/0.4.0-rc1
> > >
> > > The git commit hash:
> > >
> > >
> > 

Re: Website updates

[Tsz Wo Sze]

Filed https://issues.apache.org/jira/browse/RATIS-583 and posted a
patch.  Thanks.
Tsz-Wo

On Tue, Jun 4, 2019 at 3:48 PM Tsz Wo Sze  wrote:
>
> Sorry about that I somehow did find the asf-site-source branch earlier
> when I made the website change.
>
> Let me file a JIRA fixing it.
>
> Tsz-Wo
>
> On Tue, Jun 4, 2019 at 5:17 AM Josh Elser  wrote:
> >
> > Folks,
> >
> > In the future, please do not make changes to the asf-site branch unless
> > you have corresponding changes to the asf-site-source. Right now,
> > asf-site-source is lagging behind changes that were made by hand to
> > asf-site.
> >
> > I'll have to spend some time tomorrow to fix this, but please, again, do
> > not make changes to the generated content in the branch asf-site by hand.
> >
> > Thanks.
> >
> > - Josh

Re: Website updates

[Tsz Wo Sze]

Sorry about that I somehow did find the asf-site-source branch earlier
when I made the website change.

Let me file a JIRA fixing it.

Tsz-Wo

On Tue, Jun 4, 2019 at 5:17 AM Josh Elser  wrote:
>
> Folks,
>
> In the future, please do not make changes to the asf-site branch unless
> you have corresponding changes to the asf-site-source. Right now,
> asf-site-source is lagging behind changes that were made by hand to
> asf-site.
>
> I'll have to spend some time tomorrow to fix this, but please, again, do
> not make changes to the generated content in the branch asf-site by hand.
>
> Thanks.
>
> - Josh

[VOTE][RESULT] Apache Ratis incubating Release 0.3.0 rc2

[Tsz Wo Sze]

Thanks everyone who has verified and voted on the release candidates!

With eight +1's and no -1's, the vote for rc2 has passed.

Will start another vote in IPMC.

Tsz-Wo


On Fri, Apr 12, 2019 at 9:45 AM Jakob Homan  wrote:
>
> +1 (binding)
>
> * Check sigs
> * Check checksums
> * Build
> * Spot check licenses
> * Check NOTICE/DISCLAIMER/LICENSE
>
> Note: NOTICE needs to have copyright year updated to 2019.
>
> -Jakob
>
> On Thu, Apr 11, 2019 at 7:54 AM Elek, Marton  wrote:
> >
> > +1
> >
> > 1. Verified the Signature.
> > 2. Verified the Checksums.
> > 3. Built from Sources.
> > 4. Compiled Ozone with the 0.3.0 ratis dependency
> > 5. Executed Ozone robot tests (all passed)
> >
> > Thanks a lot,
> > Marton
> >
> > On 4/9/19 9:33 AM, Tsz Wo Sze wrote:
> > > Hi Apache Ratis PPMC,
> > >
> > > I am calling a vote for Apache Ratis incubating Release 0.3.0 rc2.
> > >
> > > The git tag to be voted upon:
> > > https://gitbox.apache.org/repos/asf?p=incubator-ratis.git=shortlog;h=refs/tags/ratis-0.3.0rc2
> > >
> > > The git commit hash:
> > > https://gitbox.apache.org/repos/asf?p=incubator-ratis.git;a=commit;h=b4bbd600f5bb1d5860cbdd8cf36ae63feedc87f9
> > >
> > > The source and binary tarballs can be found at:
> > > https://dist.apache.org/repos/dist/dev/incubator/ratis/0.3.0/rc2/
> > >
> > > The fingerprint of key to sign release artifacts:
> > > 2C33 A9CB 66AE AD59 3183  B01B 7843 4EF4 60D6 914B
> > >
> > > Release artifacts are signed with one of the keys available at:
> > > https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS
> > >
> > > This vote will remain open for at least 72 hours.
> > > Please vote on releasing this RC.  Thank you in advance.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> > > Obviously, I am +1.
> > >
> > > Regards,
> > > Tsz-Wo
> > >

[VOTE] Apache Ratis incubating Release 0.3.0 rc2

[Tsz Wo Sze]

Hi Apache Ratis PPMC,

I am calling a vote for Apache Ratis incubating Release 0.3.0 rc2.

The git tag to be voted upon:
https://gitbox.apache.org/repos/asf?p=incubator-ratis.git=shortlog;h=refs/tags/ratis-0.3.0rc2

The git commit hash:
https://gitbox.apache.org/repos/asf?p=incubator-ratis.git;a=commit;h=b4bbd600f5bb1d5860cbdd8cf36ae63feedc87f9

The source and binary tarballs can be found at:
https://dist.apache.org/repos/dist/dev/incubator/ratis/0.3.0/rc2/

The fingerprint of key to sign release artifacts:
2C33 A9CB 66AE AD59 3183  B01B 7843 4EF4 60D6 914B

Release artifacts are signed with one of the keys available at:
https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS

This vote will remain open for at least 72 hours.
Please vote on releasing this RC.  Thank you in advance.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Obviously, I am +1.

Regards,
Tsz-Wo

[VOTE] Apache Ratis incubating Release 0.3.0 rc1

[Tsz Wo Sze]

Hi Apache Ratis PPMC,

I am calling a vote for Apache Ratis incubating Release 0.3.0 rc1.

The git tag to be voted upon:
https://gitbox.apache.org/repos/asf?p=incubator-ratis.git=shortlog;h=refs/tags/ratis-0.3.0rc1

The git commit hash:
https://gitbox.apache.org/repos/asf?p=incubator-ratis.git;a=commit;h=db828919f58342ab095d633158994e5889e1ca95

The source and binary tarballs can be found at:
https://dist.apache.org/repos/dist/dev/incubator/ratis/0.3.0/rc1/

The fingerprint of key to sign release artifacts:
2C33 A9CB 66AE AD59 3183  B01B 7843 4EF4 60D6 914B

Release artifacts are signed with one of the keys available at:
https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS

This vote will remain open for at least 72 hours.
Please vote on releasing this RC.  Thank you in advance.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Obviously, I am +1.

Regards,
Tsz-Wo

Re: [VOTE] Apache Ratis incubating Release 0.3.0 rc0

[Tsz Wo Sze]

I am finally able to fix all problems in pom.xml, assembly xml and
make_rc.sh; see RATIS-513.  Please review it if you get a chance.

Will roll rc1 once RATIS-513 is committed.

Thanks.
Tsz-Wo

On Tue, Apr 2, 2019 at 9:55 AM Tsz Wo Sze  wrote:
>
> Thanks Anu and Arpit for the quick response.  The rc0 is missing a few
> modules.  Will roll rc1.
> Tsz-Wo
>
> On Tue, Apr 2, 2019 at 2:38 AM Arpit Agarwal
>  wrote:
> >
> > I also hit the same error when I build from source.
> >
> >
> > > On Apr 1, 2019, at 11:31 AM, anu engineer  wrote:
> > >
> > > Hi Tsz-Wo,
> > >
> > > Thanks for the release work. I tried out the release and checksums all
> > > match. Also verified the LICENSE, DISCLAIMER and NOTICE files. They all
> > > look good.
> > >
> > > However, when I run "mvn clean package -DskipTests", I am getting some
> > > errors.
> > > It seems to be complaining of some missing child poms. The command to 
> > > build
> > > was from the README in the root directory.
> > >
> > > [ERROR]   The project org.apache.ratis:ratis:0.3.0
> > > (/Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/pom.xml)
> > > has 4 errors
> > > [ERROR] Child module
> > > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/ratis-proto
> > > of
> > > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/pom.xml
> > > does not exist
> > > [ERROR] Child module
> > > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/ratis-test
> > > of
> > > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/pom.xml
> > > does not exist
> > > [ERROR] Child module
> > > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/ratis-examples
> > > of
> > > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/pom.xml
> > > does not exist
> > > [ERROR] Child module
> > > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/ratis-logservice
> > > of
> > > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/pom.xml
> > > does not exist
> > >
> > > Thanks
> > > Anu
> > >
> > >
> > > On Mon, Apr 1, 2019 at 9:05 AM Tsz Wo Sze  wrote:
> > >
> > >> Hi Apache Ratis PPMC,
> > >>
> > >> I am calling a vote for Apache Ratis incubating Release 0.3.0 rc0.
> > >>
> > >> The git tag to be voted upon:
> > >>
> > >> https://gitbox.apache.org/repos/asf?p=incubator-ratis.git=shortlog;h=refs/tags/ratis-0.3.0rc0
> > >>
> > >> The git commit hash:
> > >>
> > >> https://gitbox.apache.org/repos/asf?p=incubator-ratis.git;a=commit;h=0ca9879f438ffda752a3311a342e85c2ad1cac44
> > >>
> > >> The source and binary tarballs can be found at:
> > >> https://dist.apache.org/repos/dist/dev/incubator/ratis/0.3.0/rc0/
> > >>
> > >> The fingerprint of key to sign release artifacts:
> > >> 2C33 A9CB 66AE AD59 3183  B01B 7843 4EF4 60D6 914B
> > >>
> > >> Release artifacts are signed with one of the keys available at:
> > >> https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS
> > >>
> > >> This vote will remain open for at least 72 hours.
> > >> Please vote on releasing this RC.  Thank you in advance.
> > >>
> > >> [ ] +1 approve
> > >> [ ] +0 no opinion
> > >> [ ] -1 disapprove (and reason why)
> > >>
> > >> Obviously, I am +1.
> > >>
> > >> Regards,
> > >> Tsz-Wo
> > >>
> >

Re: [VOTE] Apache Ratis incubating Release 0.3.0 rc0

[Tsz Wo Sze]

Thanks Anu and Arpit for the quick response.  The rc0 is missing a few
modules.  Will roll rc1.
Tsz-Wo

On Tue, Apr 2, 2019 at 2:38 AM Arpit Agarwal
 wrote:
>
> I also hit the same error when I build from source.
>
>
> > On Apr 1, 2019, at 11:31 AM, anu engineer  wrote:
> >
> > Hi Tsz-Wo,
> >
> > Thanks for the release work. I tried out the release and checksums all
> > match. Also verified the LICENSE, DISCLAIMER and NOTICE files. They all
> > look good.
> >
> > However, when I run "mvn clean package -DskipTests", I am getting some
> > errors.
> > It seems to be complaining of some missing child poms. The command to build
> > was from the README in the root directory.
> >
> > [ERROR]   The project org.apache.ratis:ratis:0.3.0
> > (/Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/pom.xml)
> > has 4 errors
> > [ERROR] Child module
> > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/ratis-proto
> > of
> > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/pom.xml
> > does not exist
> > [ERROR] Child module
> > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/ratis-test
> > of
> > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/pom.xml
> > does not exist
> > [ERROR] Child module
> > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/ratis-examples
> > of
> > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/pom.xml
> > does not exist
> > [ERROR] Child module
> > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/ratis-logservice
> > of
> > /Users/aengineer/Downloads/ratis-release-0.3.0/ratis-incubating-0.3.0/pom.xml
> > does not exist
> >
> > Thanks
> > Anu
> >
> >
> > On Mon, Apr 1, 2019 at 9:05 AM Tsz Wo Sze  wrote:
> >
> >> Hi Apache Ratis PPMC,
> >>
> >> I am calling a vote for Apache Ratis incubating Release 0.3.0 rc0.
> >>
> >> The git tag to be voted upon:
> >>
> >> https://gitbox.apache.org/repos/asf?p=incubator-ratis.git=shortlog;h=refs/tags/ratis-0.3.0rc0
> >>
> >> The git commit hash:
> >>
> >> https://gitbox.apache.org/repos/asf?p=incubator-ratis.git;a=commit;h=0ca9879f438ffda752a3311a342e85c2ad1cac44
> >>
> >> The source and binary tarballs can be found at:
> >> https://dist.apache.org/repos/dist/dev/incubator/ratis/0.3.0/rc0/
> >>
> >> The fingerprint of key to sign release artifacts:
> >> 2C33 A9CB 66AE AD59 3183  B01B 7843 4EF4 60D6 914B
> >>
> >> Release artifacts are signed with one of the keys available at:
> >> https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS
> >>
> >> This vote will remain open for at least 72 hours.
> >> Please vote on releasing this RC.  Thank you in advance.
> >>
> >> [ ] +1 approve
> >> [ ] +0 no opinion
> >> [ ] -1 disapprove (and reason why)
> >>
> >> Obviously, I am +1.
> >>
> >> Regards,
> >> Tsz-Wo
> >>
>

[VOTE] Apache Ratis incubating Release 0.3.0 rc0

[Tsz Wo Sze]

Hi Apache Ratis PPMC,

I am calling a vote for Apache Ratis incubating Release 0.3.0 rc0.

The git tag to be voted upon:
https://gitbox.apache.org/repos/asf?p=incubator-ratis.git=shortlog;h=refs/tags/ratis-0.3.0rc0

The git commit hash:
https://gitbox.apache.org/repos/asf?p=incubator-ratis.git;a=commit;h=0ca9879f438ffda752a3311a342e85c2ad1cac44

The source and binary tarballs can be found at:
https://dist.apache.org/repos/dist/dev/incubator/ratis/0.3.0/rc0/

The fingerprint of key to sign release artifacts:
2C33 A9CB 66AE AD59 3183  B01B 7843 4EF4 60D6 914B

Release artifacts are signed with one of the keys available at:
https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS

This vote will remain open for at least 72 hours.
Please vote on releasing this RC.  Thank you in advance.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Obviously, I am +1.

Regards,
Tsz-Wo

Re: [DISCUSS] Apache Ratis 0.3.0 release

[Tsz Wo Sze]

I am going to prepare a release candidate from branch-0.3.  Thanks everyone!

Tsz-Wo

On Thu, Mar 28, 2019 at 7:23 PM Tsz Wo Sze  wrote:
>
> Rajeshbabu,
>
> Thanks a lot for the quick response!
>
> Tsz-Wo
>
> On Thu, Mar 28, 2019 at 7:06 PM rajeshb...@apache.org
>  wrote:
> >
> > committed RATIS-510 to branch 0.3.0 Tsz.
> >
> > Thanks,
> > Rajeshbabu.
> >
> > On Thu, Mar 28, 2019 at 4:28 PM rajeshb...@apache.org <
> > chrajeshbab...@gmail.com> wrote:
> >
> > > I will commit RATIS-510 Tez.
> > >
> > > Thanks,
> > > Rajeshbabu.
> > >
> > > On Thu, Mar 28, 2019, 3:58 PM Tsz Wo Sze  > >
> > >> All RATIS-503, RATIS-506 and RATIS-490 are now committed.  However, we
> > >> need RATIS-510 (missing Apache license header) or revert RATIS-475
> > >> from branch-0.3.
> > >>
> > >> Will see if we can roll a release tomorrow.
> > >>
> > >> Thanks.
> > >> Tsz-Wo
> > >>
> > >> On Tue, Mar 26, 2019 at 12:09 AM Jitendra Pandey 
> > >> wrote:
> > >> >
> > >> > +1 I would suggest we should cut a release candidate once following 3
> > >> are
> > >> > included:
> > >> > RATIS-503, RATIS-506 and RATIS-490, however RATIS-490 is not a blocker
> > >> in
> > >> > my opinion.
> > >> >
> > >> > On Mon, Mar 25, 2019 at 5:47 AM Tsz Wo Sze  wrote:
> > >> >
> > >> > > How about we roll a 0.3.0 release from branch-0.3?  Please let me 
> > >> > > know
> > >> > > if there are specific JIRAs we should include in 0.3.0.  Thanks.
> > >> > >
> > >> > > Tsz-Wo
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > On Fri, Mar 22, 2019 at 1:19 PM Tsz Wo Sze 
> > >> wrote:
> > >> > > >
> > >> > > > I just have re-created branch-0.3.  If you already have branch-0.3
> > >> > > > locally, "git pull" should be able to update all the changes.
> > >> Thanks.
> > >> > > >
> > >> > > > Tsz-Wo
> > >> > > >
> > >> > > > On Thu, Mar 21, 2019 at 12:47 AM Mukul Kumar Singh
> > >> > > >  wrote:
> > >> > > > >
> > >> > > > > +1,
> > >> > > > >
> > >> > > > > On 3/20/19, 9:20 PM, "Jitendra Pandey" 
> > >> wrote:
> > >> > > > >
> > >> > > > > > I will merge everything in master to branch-0.3 (or
> > >> re-create
> > >> > > the 0.3
> > >> > > > > branch).
> > >> > > > >
> > >> > > > > +1
> > >> > > > >
> > >> > > > > On Wed, Mar 20, 2019 at 7:58 AM Arpit Agarwal
> > >> > > 
> > >> > > > > wrote:
> > >> > > > >
> > >> > > > > > +1 for rebasing 0.3 to trunk.
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > > On Mar 20, 2019, at 2:37 AM, Tsz Wo Sze <
> > >> szets...@gmail.com>
> > >> > > wrote:
> > >> > > > > > >
> > >> > > > > > > If there is no objection, I will merge everything in
> > >> master to
> > >> > > > > > > branch-0.3 (or re-create the 0.3 branch) tomorrow.
> > >> Thanks.
> > >> > > > > > >
> > >> > > > > > > Tsz-Wo
> > >> > > > > > >
> > >> > > > > > > On Fri, Mar 1, 2019 at 6:54 AM Jitendra Pandey <
> > >> > > jiten...@hortonworks.com>
> > >> > > > > > wrote:
> > >> > > > > > >>
> > >> > > > > > >> +1
> > >> > > > > > >> There have been many fixes in trunk lately that need to
> > >> be in
> > >> > > 0.3 as
> > >> > > > > > well. Therefore, it makes sense to rebase 0.3 to the 
> > >> > > > > curre

Re: [DISCUSS] Apache Ratis 0.3.0 release

[Tsz Wo Sze]

Rajeshbabu,

Thanks a lot for the quick response!

Tsz-Wo

On Thu, Mar 28, 2019 at 7:06 PM rajeshb...@apache.org
 wrote:
>
> committed RATIS-510 to branch 0.3.0 Tsz.
>
> Thanks,
> Rajeshbabu.
>
> On Thu, Mar 28, 2019 at 4:28 PM rajeshb...@apache.org <
> chrajeshbab...@gmail.com> wrote:
>
> > I will commit RATIS-510 Tez.
> >
> > Thanks,
> > Rajeshbabu.
> >
> > On Thu, Mar 28, 2019, 3:58 PM Tsz Wo Sze  >
> >> All RATIS-503, RATIS-506 and RATIS-490 are now committed.  However, we
> >> need RATIS-510 (missing Apache license header) or revert RATIS-475
> >> from branch-0.3.
> >>
> >> Will see if we can roll a release tomorrow.
> >>
> >> Thanks.
> >> Tsz-Wo
> >>
> >> On Tue, Mar 26, 2019 at 12:09 AM Jitendra Pandey 
> >> wrote:
> >> >
> >> > +1 I would suggest we should cut a release candidate once following 3
> >> are
> >> > included:
> >> > RATIS-503, RATIS-506 and RATIS-490, however RATIS-490 is not a blocker
> >> in
> >> > my opinion.
> >> >
> >> > On Mon, Mar 25, 2019 at 5:47 AM Tsz Wo Sze  wrote:
> >> >
> >> > > How about we roll a 0.3.0 release from branch-0.3?  Please let me know
> >> > > if there are specific JIRAs we should include in 0.3.0.  Thanks.
> >> > >
> >> > > Tsz-Wo
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > On Fri, Mar 22, 2019 at 1:19 PM Tsz Wo Sze 
> >> wrote:
> >> > > >
> >> > > > I just have re-created branch-0.3.  If you already have branch-0.3
> >> > > > locally, "git pull" should be able to update all the changes.
> >> Thanks.
> >> > > >
> >> > > > Tsz-Wo
> >> > > >
> >> > > > On Thu, Mar 21, 2019 at 12:47 AM Mukul Kumar Singh
> >> > > >  wrote:
> >> > > > >
> >> > > > > +1,
> >> > > > >
> >> > > > > On 3/20/19, 9:20 PM, "Jitendra Pandey" 
> >> wrote:
> >> > > > >
> >> > > > > > I will merge everything in master to branch-0.3 (or
> >> re-create
> >> > > the 0.3
> >> > > > > branch).
> >> > > > >
> >> > > > > +1
> >> > > > >
> >> > > > > On Wed, Mar 20, 2019 at 7:58 AM Arpit Agarwal
> >> > > 
> >> > > > > wrote:
> >> > > > >
> >> > > > > > +1 for rebasing 0.3 to trunk.
> >> > > > > >
> >> > > > > >
> >> > > > > > > On Mar 20, 2019, at 2:37 AM, Tsz Wo Sze <
> >> szets...@gmail.com>
> >> > > wrote:
> >> > > > > > >
> >> > > > > > > If there is no objection, I will merge everything in
> >> master to
> >> > > > > > > branch-0.3 (or re-create the 0.3 branch) tomorrow.
> >> Thanks.
> >> > > > > > >
> >> > > > > > > Tsz-Wo
> >> > > > > > >
> >> > > > > > > On Fri, Mar 1, 2019 at 6:54 AM Jitendra Pandey <
> >> > > jiten...@hortonworks.com>
> >> > > > > > wrote:
> >> > > > > > >>
> >> > > > > > >> +1
> >> > > > > > >> There have been many fixes in trunk lately that need to
> >> be in
> >> > > 0.3 as
> >> > > > > > well. Therefore, it makes sense to rebase 0.3 to the current
> >> > > trunk.
> >> > > > > > >>
> >> > > > > > >> On 2/28/19, 2:49 PM, "Tsz Wo Sze" 
> >> wrote:
> >> > > > > > >>
> >> > > > > > >>Hi Marton,
> >> > > > > > >>
> >> > > > > > >>For Ozone, it probably needs trunk.  How about we move
> >> > > everything in
> >> > > > > > >>trunk to 0.3?
> >> > > > > > >>
> >> > > > > > >>Tsz-Wo
> >> > > > > > >>
> >> > > > > > >>On Tue, Feb 26, 2019 at 6:59 AM Elek, Marton <
> >> > > e...@apache.org>
> >> > > > > > wrote:
> >> > > > > > >>>
> >> > > > > > >>> Hi,
> >> > > > > > >>>
> >> > > > > > >>> Any comment on this?
> >> > > > > > >>>
> >> > > > > > >>> What is the plan with the next release?
> >> > > > > > >>>
> >> > > > > > >>> Thanks,
> >> > > > > > >>> Marton
> >> > > > > > >>>
> >> > > > > > >>> On 2/6/19 11:21 AM, Elek, Marton wrote:
> >> > > > > > >>>> Bumping up this thread.
> >> > > > > > >>>>
> >> > > > > > >>>> I would like to use stable ratis release for the next
> >> ozone
> >> > > release.
> >> > > > > > >>>>
> >> > > > > > >>>> As I see branch-0.3 contains only RATIS-430.
> >> > > > > > >>>>
> >> > > > > > >>>> What is the current plan of releasing 0.3.0?
> >> > > > > > >>>>
> >> > > > > > >>>> Can we release branch-0.3 as is?
> >> > > > > > >>>>
> >> > > > > > >>>> Do we need to rebase branch-0.3 on top of the latest
> >> master?
> >> > > > > > >>>>
> >> > > > > > >>>>
> >> > > > > > >>>> Thanks,
> >> > > > > > >>>> Marton
> >> > > > > > >>>>
> >> > > > > > >>>> On 11/12/18 9:37 PM, Tsz Wo Sze wrote:
> >> > > > > > >>>>> Hi,
> >> > > > > > >>>>>
> >> > > > > > >>>>> We have around 80 commits after 0.2.0 release.  How
> >> about
> >> > > we start
> >> > > > > > >>>>> preparing Ratis 0.3.0 release?
> >> > > > > > >>>>>
> >> > > > > > >>>>> We may create a 0.3.0 branch and change trunk to
> >> 0.4.0.
> >> > > Then, we can
> >> > > > > > >>>>> stabilize 0.3.0 before starting a vote.
> >> > > > > > >>>>>
> >> > > > > > >>>>> Tsz-Wo
> >> > > > > > >>>>>
> >> > > > > > >>
> >> > > > > > >>
> >> > > > > > >>
> >> > > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > >
> >>
> >

Re: [DISCUSS] Apache Ratis 0.3.0 release

[Tsz Wo Sze]

All RATIS-503, RATIS-506 and RATIS-490 are now committed.  However, we
need RATIS-510 (missing Apache license header) or revert RATIS-475
from branch-0.3.

Will see if we can roll a release tomorrow.

Thanks.
Tsz-Wo

On Tue, Mar 26, 2019 at 12:09 AM Jitendra Pandey  wrote:
>
> +1 I would suggest we should cut a release candidate once following 3 are
> included:
> RATIS-503, RATIS-506 and RATIS-490, however RATIS-490 is not a blocker in
> my opinion.
>
> On Mon, Mar 25, 2019 at 5:47 AM Tsz Wo Sze  wrote:
>
> > How about we roll a 0.3.0 release from branch-0.3?  Please let me know
> > if there are specific JIRAs we should include in 0.3.0.  Thanks.
> >
> > Tsz-Wo
> >
> >
> >
> >
> > On Fri, Mar 22, 2019 at 1:19 PM Tsz Wo Sze  wrote:
> > >
> > > I just have re-created branch-0.3.  If you already have branch-0.3
> > > locally, "git pull" should be able to update all the changes.  Thanks.
> > >
> > > Tsz-Wo
> > >
> > > On Thu, Mar 21, 2019 at 12:47 AM Mukul Kumar Singh
> > >  wrote:
> > > >
> > > > +1,
> > > >
> > > > On 3/20/19, 9:20 PM, "Jitendra Pandey"  wrote:
> > > >
> > > > > I will merge everything in master to branch-0.3 (or re-create
> > the 0.3
> > > > branch).
> > > >
> > > > +1
> > > >
> > > > On Wed, Mar 20, 2019 at 7:58 AM Arpit Agarwal
> > 
> > > > wrote:
> > > >
> > > > > +1 for rebasing 0.3 to trunk.
> > > > >
> > > > >
> > > > > > On Mar 20, 2019, at 2:37 AM, Tsz Wo Sze 
> > wrote:
> > > > > >
> > > > > > If there is no objection, I will merge everything in master to
> > > > > > branch-0.3 (or re-create the 0.3 branch) tomorrow.  Thanks.
> > > > > >
> > > > > > Tsz-Wo
> > > > > >
> > > > > > On Fri, Mar 1, 2019 at 6:54 AM Jitendra Pandey <
> > jiten...@hortonworks.com>
> > > > > wrote:
> > > > > >>
> > > > > >> +1
> > > > > >> There have been many fixes in trunk lately that need to be in
> > 0.3 as
> > > > > well. Therefore, it makes sense to rebase 0.3 to the current
> > trunk.
> > > > > >>
> > > > > >> On 2/28/19, 2:49 PM, "Tsz Wo Sze"  wrote:
> > > > > >>
> > > > > >>Hi Marton,
> > > > > >>
> > > > > >>For Ozone, it probably needs trunk.  How about we move
> > everything in
> > > > > >>trunk to 0.3?
> > > > > >>
> > > > > >>Tsz-Wo
> > > > > >>
> > > > > >>On Tue, Feb 26, 2019 at 6:59 AM Elek, Marton <
> > e...@apache.org>
> > > > > wrote:
> > > > > >>>
> > > > > >>> Hi,
> > > > > >>>
> > > > > >>> Any comment on this?
> > > > > >>>
> > > > > >>> What is the plan with the next release?
> > > > > >>>
> > > > > >>> Thanks,
> > > > > >>> Marton
> > > > > >>>
> > > > > >>> On 2/6/19 11:21 AM, Elek, Marton wrote:
> > > > > >>>> Bumping up this thread.
> > > > > >>>>
> > > > > >>>> I would like to use stable ratis release for the next ozone
> > release.
> > > > > >>>>
> > > > > >>>> As I see branch-0.3 contains only RATIS-430.
> > > > > >>>>
> > > > > >>>> What is the current plan of releasing 0.3.0?
> > > > > >>>>
> > > > > >>>> Can we release branch-0.3 as is?
> > > > > >>>>
> > > > > >>>> Do we need to rebase branch-0.3 on top of the latest master?
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> Thanks,
> > > > > >>>> Marton
> > > > > >>>>
> > > > > >>>> On 11/12/18 9:37 PM, Tsz Wo Sze wrote:
> > > > > >>>>> Hi,
> > > > > >>>>>
> > > > > >>>>> We have around 80 commits after 0.2.0 release.  How about
> > we start
> > > > > >>>>> preparing Ratis 0.3.0 release?
> > > > > >>>>>
> > > > > >>>>> We may create a 0.3.0 branch and change trunk to 0.4.0.
> > Then, we can
> > > > > >>>>> stabilize 0.3.0 before starting a vote.
> > > > > >>>>>
> > > > > >>>>> Tsz-Wo
> > > > > >>>>>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> >

Re: [DISCUSS] Apache Ratis 0.3.0 release

[Tsz Wo Sze]

How about we roll a 0.3.0 release from branch-0.3?  Please let me know
if there are specific JIRAs we should include in 0.3.0.  Thanks.

Tsz-Wo




On Fri, Mar 22, 2019 at 1:19 PM Tsz Wo Sze  wrote:
>
> I just have re-created branch-0.3.  If you already have branch-0.3
> locally, "git pull" should be able to update all the changes.  Thanks.
>
> Tsz-Wo
>
> On Thu, Mar 21, 2019 at 12:47 AM Mukul Kumar Singh
>  wrote:
> >
> > +1,
> >
> > On 3/20/19, 9:20 PM, "Jitendra Pandey"  wrote:
> >
> > > I will merge everything in master to branch-0.3 (or re-create the 0.3
> > branch).
> >
> > +1
> >
> > On Wed, Mar 20, 2019 at 7:58 AM Arpit Agarwal 
> > 
> >     wrote:
> >
> > > +1 for rebasing 0.3 to trunk.
> > >
> > >
> > > > On Mar 20, 2019, at 2:37 AM, Tsz Wo Sze  wrote:
> > > >
> > > > If there is no objection, I will merge everything in master to
> > > > branch-0.3 (or re-create the 0.3 branch) tomorrow.  Thanks.
> > > >
> > > > Tsz-Wo
> > > >
> > > > On Fri, Mar 1, 2019 at 6:54 AM Jitendra Pandey 
> > 
> > > wrote:
> > > >>
> > > >> +1
> > > >> There have been many fixes in trunk lately that need to be in 0.3 
> > as
> > > well. Therefore, it makes sense to rebase 0.3 to the current trunk.
> > > >>
> > > >> On 2/28/19, 2:49 PM, "Tsz Wo Sze"  wrote:
> > > >>
> > > >>Hi Marton,
> > > >>
> > > >>For Ozone, it probably needs trunk.  How about we move 
> > everything in
> > > >>trunk to 0.3?
> > > >>
> > > >>Tsz-Wo
> > > >>
> > > >>On Tue, Feb 26, 2019 at 6:59 AM Elek, Marton 
> > > wrote:
> > > >>>
> > > >>> Hi,
> > > >>>
> > > >>> Any comment on this?
> > > >>>
> > > >>> What is the plan with the next release?
> > > >>>
> > > >>> Thanks,
> > > >>> Marton
> > > >>>
> > > >>> On 2/6/19 11:21 AM, Elek, Marton wrote:
> > > >>>> Bumping up this thread.
> > > >>>>
> > > >>>> I would like to use stable ratis release for the next ozone 
> > release.
> > > >>>>
> > > >>>> As I see branch-0.3 contains only RATIS-430.
> > > >>>>
> > > >>>> What is the current plan of releasing 0.3.0?
> > > >>>>
> > > >>>> Can we release branch-0.3 as is?
> > > >>>>
> > > >>>> Do we need to rebase branch-0.3 on top of the latest master?
> > > >>>>
> > > >>>>
> > > >>>> Thanks,
> > > >>>> Marton
> > > >>>>
> > > >>>> On 11/12/18 9:37 PM, Tsz Wo Sze wrote:
> > > >>>>> Hi,
> > > >>>>>
> > > >>>>> We have around 80 commits after 0.2.0 release.  How about we 
> > start
> > > >>>>> preparing Ratis 0.3.0 release?
> > > >>>>>
> > > >>>>> We may create a 0.3.0 branch and change trunk to 0.4.0.  Then, 
> > we can
> > > >>>>> stabilize 0.3.0 before starting a vote.
> > > >>>>>
> > > >>>>> Tsz-Wo
> > > >>>>>
> > > >>
> > > >>
> > > >>
> > > >
> > >
> > >
> >
> >

Re: [DISCUSS] Apache Ratis 0.3.0 release

[Tsz Wo Sze]

I just have re-created branch-0.3.  If you already have branch-0.3
locally, "git pull" should be able to update all the changes.  Thanks.

Tsz-Wo

On Thu, Mar 21, 2019 at 12:47 AM Mukul Kumar Singh
 wrote:
>
> +1,
>
> On 3/20/19, 9:20 PM, "Jitendra Pandey"  wrote:
>
> > I will merge everything in master to branch-0.3 (or re-create the 0.3
> branch).
>
> +1
>
> On Wed, Mar 20, 2019 at 7:58 AM Arpit Agarwal 
> 
> wrote:
>
> > +1 for rebasing 0.3 to trunk.
> >
> >
> > > On Mar 20, 2019, at 2:37 AM, Tsz Wo Sze  wrote:
> > >
> > > If there is no objection, I will merge everything in master to
> > > branch-0.3 (or re-create the 0.3 branch) tomorrow.  Thanks.
> > >
> > > Tsz-Wo
> > >
> > > On Fri, Mar 1, 2019 at 6:54 AM Jitendra Pandey 
> 
> > wrote:
> > >>
> > >> +1
> > >> There have been many fixes in trunk lately that need to be in 0.3 as
> > well. Therefore, it makes sense to rebase 0.3 to the current trunk.
> > >>
> > >> On 2/28/19, 2:49 PM, "Tsz Wo Sze"  wrote:
> > >>
> > >>Hi Marton,
> > >>
> > >>For Ozone, it probably needs trunk.  How about we move everything 
> in
> > >>trunk to 0.3?
> > >>
> > >>Tsz-Wo
> > >>
> > >>On Tue, Feb 26, 2019 at 6:59 AM Elek, Marton 
> > wrote:
> > >>>
> > >>> Hi,
> > >>>
> > >>> Any comment on this?
> > >>>
> > >>> What is the plan with the next release?
> > >>>
> > >>> Thanks,
> > >>> Marton
> > >>>
> > >>> On 2/6/19 11:21 AM, Elek, Marton wrote:
> > >>>> Bumping up this thread.
> > >>>>
> > >>>> I would like to use stable ratis release for the next ozone 
> release.
> > >>>>
> > >>>> As I see branch-0.3 contains only RATIS-430.
> > >>>>
> > >>>> What is the current plan of releasing 0.3.0?
> > >>>>
> > >>>> Can we release branch-0.3 as is?
> > >>>>
> > >>>> Do we need to rebase branch-0.3 on top of the latest master?
> > >>>>
> > >>>>
> > >>>> Thanks,
> > >>>> Marton
> > >>>>
> > >>>> On 11/12/18 9:37 PM, Tsz Wo Sze wrote:
> > >>>>> Hi,
> > >>>>>
> > >>>>> We have around 80 commits after 0.2.0 release.  How about we start
> > >>>>> preparing Ratis 0.3.0 release?
> > >>>>>
> > >>>>> We may create a 0.3.0 branch and change trunk to 0.4.0.  Then, we 
> can
> > >>>>> stabilize 0.3.0 before starting a vote.
> > >>>>>
> > >>>>> Tsz-Wo
> > >>>>>
> > >>
> > >>
> > >>
> > >
> >
> >
>
>

Re: [DISCUSS] Apache Ratis 0.3.0 release

[Tsz Wo Sze]

If there is no objection, I will merge everything in master to
branch-0.3 (or re-create the 0.3 branch) tomorrow.  Thanks.

Tsz-Wo

On Fri, Mar 1, 2019 at 6:54 AM Jitendra Pandey  wrote:
>
> +1
> There have been many fixes in trunk lately that need to be in 0.3 as well. 
> Therefore, it makes sense to rebase 0.3 to the current trunk.
>
> On 2/28/19, 2:49 PM, "Tsz Wo Sze"  wrote:
>
> Hi Marton,
>
> For Ozone, it probably needs trunk.  How about we move everything in
> trunk to 0.3?
>
> Tsz-Wo
>
> On Tue, Feb 26, 2019 at 6:59 AM Elek, Marton  wrote:
> >
> > Hi,
> >
> > Any comment on this?
> >
> > What is the plan with the next release?
> >
> > Thanks,
> > Marton
> >
> > On 2/6/19 11:21 AM, Elek, Marton wrote:
> > > Bumping up this thread.
> > >
> > > I would like to use stable ratis release for the next ozone release.
> > >
> > > As I see branch-0.3 contains only RATIS-430.
> > >
> > > What is the current plan of releasing 0.3.0?
> > >
> > > Can we release branch-0.3 as is?
> > >
> > > Do we need to rebase branch-0.3 on top of the latest master?
> > >
> > >
> > > Thanks,
> > > Marton
> > >
> > > On 11/12/18 9:37 PM, Tsz Wo Sze wrote:
> > >> Hi,
> > >>
> > >> We have around 80 commits after 0.2.0 release.  How about we start
> > >> preparing Ratis 0.3.0 release?
> > >>
> > >> We may create a 0.3.0 branch and change trunk to 0.4.0.  Then, we can
> > >> stabilize 0.3.0 before starting a vote.
> > >>
> > >> Tsz-Wo
> > >>
>
>
>

Re: [DISCUSS] Apache Ratis 0.3.0 release

[Tsz Wo Sze]

Hi Marton,

For Ozone, it probably needs trunk.  How about we move everything in
trunk to 0.3?

Tsz-Wo

On Tue, Feb 26, 2019 at 6:59 AM Elek, Marton  wrote:
>
> Hi,
>
> Any comment on this?
>
> What is the plan with the next release?
>
> Thanks,
> Marton
>
> On 2/6/19 11:21 AM, Elek, Marton wrote:
> > Bumping up this thread.
> >
> > I would like to use stable ratis release for the next ozone release.
> >
> > As I see branch-0.3 contains only RATIS-430.
> >
> > What is the current plan of releasing 0.3.0?
> >
> > Can we release branch-0.3 as is?
> >
> > Do we need to rebase branch-0.3 on top of the latest master?
> >
> >
> > Thanks,
> > Marton
> >
> > On 11/12/18 9:37 PM, Tsz Wo Sze wrote:
> >> Hi,
> >>
> >> We have around 80 commits after 0.2.0 release.  How about we start
> >> preparing Ratis 0.3.0 release?
> >>
> >> We may create a 0.3.0 branch and change trunk to 0.4.0.  Then, we can
> >> stabilize 0.3.0 before starting a vote.
> >>
> >> Tsz-Wo
> >>

Re: CI on pull requests

[Tsz Wo Sze]

It is great, thanks for working on it!
Tsz-Wo

On Thu, Jan 31, 2019 at 6:35 PM Josh Elser  wrote:
>
> For those interested in using Github pull requests for code reviews,
> with the help of Chris T from infra, I got a "check" working which
> spawns a job on the builds.a.o Jenkins server.
>
> https://builds.apache.org/job/PreCommit-RATIS-github-pull-requests/
>
> It doesn't look perfect (some test failures on a dummy commit), but it's
> better than nothing ;)

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

[Tsz Wo Sze]

Yes, the new URL works well.  Thanks!

Tsz-Wo

On Wed, Jan 9, 2019 at 2:00 AM Mingliang Liu  wrote:
>
> Thanks for the migration effort. I update the url locally and it works.
>
> On Tue, Jan 8, 2019 at 9:22 AM Josh Elser  wrote:
>
> > Thanks for updating the builds, Marton!
> >
> > On 1/8/19 3:22 AM, Elek, Marton wrote:
> > > Done by INFRA.
> > >
> > > The new URL is:
> > >
> > > https://gitbox.apache.org/repos/asf/incubator-ratis.git
> > >
> > > I updated the 4 jenkins build here:
> > https://builds.apache.org/view/Ratis/
> > >
> > > m.
> > >
> > > On 1/8/19 12:38 AM, Josh Elser wrote:
> > >> Pending: https://issues.apache.org/jira/browse/INFRA-17580
> > >>
> > >> HTH, folks.
> > >>
> > >> On 1/7/19 7:58 AM, Tsz Wo Sze wrote:
> > >>> That's great, thank you so much, Josh.
> > >>>
> > >>> Tsz-Wo
> > >>>
> > >>> On Mon, Jan 7, 2019 at 5:49 PM Elek, Marton  wrote:
> > >>>>
> > >>>> +1, please, do it.
> > >>>>
> > >>>> Thank you to manage it.
> > >>>>
> > >>>> Marton
> > >>>>
> > >>>> On 1/3/19 9:59 PM, Josh Elser wrote:
> > >>>>> Please shout if there's any dissent over doing this today.
> > >>>>>
> > >>>>> If I don't hear any objections, I'll submit a request on Monday.
> > >>>>>
> > >>>>> On 1/3/19 8:19 AM, Apache Infrastructure Team wrote:
> > >>>>>> Hello, ratis folks.
> > >>>>>> As stated earlier in 2018, all git repositories must be migrated
> > from
> > >>>>>> the git-wip-us.apache.org URL to gitbox.apache.org, as the old
> > service
> > >>>>>> is being decommissioned. Your project is receiving this email
> > because
> > >>>>>> you still have repositories on git-wip-us that needs to be migrated.
> > >>>>>>
> > >>>>>> The following repositories on git-wip-us belong to your project:
> > >>>>>> - incubator-ratis.git
> > >>>>>>
> > >>>>>>
> > >>>>>> We are now entering the mandated (coordinated) move stage of the
> > >>>>>> roadmap,
> > >>>>>> and you are asked to please coordinate migration with the Apache
> > >>>>>> Infrastructure Team before February 7th. All repositories not
> > migrated
> > >>>>>> on February 7th will be mass migrated without warning, and we'd
> > >>>>>> appreciate
> > >>>>>> it if we could work together to avoid a big mess that day :-).
> > >>>>>>
> > >>>>>> Moving to gitbox means you will get full write access on GitHub as
> > >>>>>> well,
> > >>>>>> and be able to close/merge pull requests and much more.
> > >>>>>>
> > >>>>>> To have your repositories moved, please follow these steps:
> > >>>>>>
> > >>>>>> - Ensure consensus on the move (a link to a lists.apache.org thread
> > >>>>>> will
> > >>>>>>  suffice for us as evidence).
> > >>>>>> - Create a JIRA ticket at
> > https://issues.apache.org/jira/browse/INFRA
> > >>>>>>
> > >>>>>> Your migration should only take a few minutes. If you wish to
> > migrate
> > >>>>>> at a specific time of day or date, please do let us know in the
> > >>>>>> ticket.
> > >>>>>>
> > >>>>>> As always, we appreciate your understanding and patience as we move
> > >>>>>> things around and work to provide better services and features for
> > >>>>>> the Apache Family.
> > >>>>>>
> > >>>>>> Should you wish to contact us with feedback or questions, please do
> > so
> > >>>>>> at: us...@infra.apache.org.
> > >>>>>>
> > >>>>>>
> > >>>>>> With regards,
> > >>>>>> Apache Infrastructure
> > >>>>>>
> >
>
>
> --
> L

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

[Tsz Wo Sze]

That's great, thank you so much, Josh.

Tsz-Wo

On Mon, Jan 7, 2019 at 5:49 PM Elek, Marton  wrote:
>
> +1, please, do it.
>
> Thank you to manage it.
>
> Marton
>
> On 1/3/19 9:59 PM, Josh Elser wrote:
> > Please shout if there's any dissent over doing this today.
> >
> > If I don't hear any objections, I'll submit a request on Monday.
> >
> > On 1/3/19 8:19 AM, Apache Infrastructure Team wrote:
> >> Hello, ratis folks.
> >> As stated earlier in 2018, all git repositories must be migrated from
> >> the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
> >> is being decommissioned. Your project is receiving this email because
> >> you still have repositories on git-wip-us that needs to be migrated.
> >>
> >> The following repositories on git-wip-us belong to your project:
> >>   - incubator-ratis.git
> >>
> >>
> >> We are now entering the mandated (coordinated) move stage of the roadmap,
> >> and you are asked to please coordinate migration with the Apache
> >> Infrastructure Team before February 7th. All repositories not migrated
> >> on February 7th will be mass migrated without warning, and we'd
> >> appreciate
> >> it if we could work together to avoid a big mess that day :-).
> >>
> >> Moving to gitbox means you will get full write access on GitHub as well,
> >> and be able to close/merge pull requests and much more.
> >>
> >> To have your repositories moved, please follow these steps:
> >>
> >> - Ensure consensus on the move (a link to a lists.apache.org thread will
> >>suffice for us as evidence).
> >> - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
> >>
> >> Your migration should only take a few minutes. If you wish to migrate
> >> at a specific time of day or date, please do let us know in the ticket.
> >>
> >> As always, we appreciate your understanding and patience as we move
> >> things around and work to provide better services and features for
> >> the Apache Family.
> >>
> >> Should you wish to contact us with feedback or questions, please do so
> >> at: us...@infra.apache.org.
> >>
> >>
> >> With regards,
> >> Apache Infrastructure
> >>

Re: [DISCUSS] Apache Ratis 0.3.0 release

[Tsz Wo Sze]

> ... pushed master version to 0.4.0.

It should be 0.4.0-SNAPSHOT.  I also have pushed ratis-thirdparty
version to 0.2.0-SNAPSHOT.
Tsz-Wo


On Tue, Nov 20, 2018 at 1:29 PM Tsz Wo Sze  wrote:
>
> Thanks everyone for supporting it!  I just have created branch-0.3 and
> pushed master version to 0.4.0.
>
> Tsz-Wo
> On Tue, Nov 20, 2018 at 3:50 AM Elek, Marton  wrote:
> >
> > +1 Very good idea.
> >
> > Marton
> >
> > ps: Would be great to switch to fixed versions in Ozone.
> >
> >
> > On 11/14/18 9:22 PM, Hugo Louro wrote:
> > > +1
> > >
> > > On Wed, Nov 14, 2018 at 12:14 PM Josh Elser  wrote:
> > >
> > >> +1
> > >>
> > >> On 11/12/18 1:29 PM, Jitendra Pandey wrote:
> > >>> That is a good idea. We should try to maintain a release cadence.
> > >>> +1
> > >>>
> > >>> On 11/12/18, 12:37 PM, "Tsz Wo Sze"  wrote:
> > >>>
> > >>>  Hi,
> > >>>
> > >>>  We have around 80 commits after 0.2.0 release.  How about we start
> > >>>  preparing Ratis 0.3.0 release?
> > >>>
> > >>>  We may create a 0.3.0 branch and change trunk to 0.4.0.  Then, we
> > >> can
> > >>>  stabilize 0.3.0 before starting a vote.
> > >>>
> > >>>  Tsz-Wo
> > >>>
> > >>>
> > >>>
> > >>
> > >

Re: [DISCUSS] Apache Ratis 0.3.0 release

[Tsz Wo Sze]

Thanks everyone for supporting it!  I just have created branch-0.3 and
pushed master version to 0.4.0.

Tsz-Wo
On Tue, Nov 20, 2018 at 3:50 AM Elek, Marton  wrote:
>
> +1 Very good idea.
>
> Marton
>
> ps: Would be great to switch to fixed versions in Ozone.
>
>
> On 11/14/18 9:22 PM, Hugo Louro wrote:
> > +1
> >
> > On Wed, Nov 14, 2018 at 12:14 PM Josh Elser  wrote:
> >
> >> +1
> >>
> >> On 11/12/18 1:29 PM, Jitendra Pandey wrote:
> >>> That is a good idea. We should try to maintain a release cadence.
> >>> +1
> >>>
> >>> On 11/12/18, 12:37 PM, "Tsz Wo Sze"  wrote:
> >>>
> >>>  Hi,
> >>>
> >>>  We have around 80 commits after 0.2.0 release.  How about we start
> >>>  preparing Ratis 0.3.0 release?
> >>>
> >>>  We may create a 0.3.0 branch and change trunk to 0.4.0.  Then, we
> >> can
> >>>  stabilize 0.3.0 before starting a vote.
> >>>
> >>>  Tsz-Wo
> >>>
> >>>
> >>>
> >>
> >

[DISCUSS] Apache Ratis 0.3.0 release

[Tsz Wo Sze]

Hi,

We have around 80 commits after 0.2.0 release.  How about we start
preparing Ratis 0.3.0 release?

We may create a 0.3.0 branch and change trunk to 0.4.0.  Then, we can
stabilize 0.3.0 before starting a vote.

Tsz-Wo

Re: [VOTE] Apache Ratis Thirdparty 0.1.0rc1

[Tsz Wo Sze]

+1

- Verified the signature and checksums.
- Checked LICENSE, NOTICE and NOTICE in the gz and the jar files
- Checked file names -- all file in
https://dist.apache.org/repos/dist/dev/incubator/ratis/thirdparty/0.1.0-rc1/
have "incubating".

Thanks a lot, Josh!
Tsz-Wo

On Thu, Nov 1, 2018 at 2:20 AM Josh Elser  wrote:
>
> Hi,
>
> Please vote on the following release candidate to become Apache Ratis
> Thirdparty 0.1.0.
>
> The Apache Ratis Thirdparty project is a collection of all thirdparty
> dependencies that Apache Ratis uses, repackaged for optimal use by
> Ratis. As such, there is very little net-new source code in this project.
>
> Over rc0, this RC does:
>
> * Incubating in the file name
> * make_rc.sh updates
> * Includes a DISCLAIMER in generated jar files
> * renames ratis-thirdparty to ratis-thirdparty-misc (not yet reflected
> in ratis.git)
>
> The source release is present at
> https://dist.apache.org/repos/dist/dev/incubator/ratis/thirdparty/0.1.0-rc1/
>
> SHA512 checksum is on the source tarball: 2B11B643 836E367E C47D0F64
> 7750E1AB DE2C3FDE ECF2C825 5F8292FA D4CF2DB4 04BEB4B6
>   12173754 4C6ACEEE B8534964 C6A4B690 EA9656E2 CAFDB317 FAAB46BA
>
> This source release was created from the Git commit SHA1:
> 896f7b3453e155df96b8ef62b85aa0b92c37d886. For your convenience, there
> is also a GPG-signed tag with the name "ratis-thirdparty-0.1.0rc1" that
> also points at this commit.
>
> This source release was signed with my key: 4677D66C. This is present
> in the KEYS file (dist/dev and dist/release).
>
> The corresponding "binaries" for this release are staged at
> https://repository.apache.org/content/repositories/orgapacheratis-1008/ and
> will be promoted pending successful PPMC and IPMC votes. You can
> update your local ~/.m2/settings.xml to add this as a repository to
> test the build of ratis.git if you choose (appears to work fine for me).
>
> This vote will be open for at least 72hours (until 2018/11/03 19:00:00
> GMT).
>
> --
>
> Here's my +1 (non-binding)
>
> - Josh

Re: [VOTE] Apache Ratis Thirdparty 0.1.0rc0

[Tsz Wo Sze]

> I don't see any value for that, tbh. ...

I agree that no one is going to download and use the binary.  However,
it is an artifact which we can vote for.  It seems ASF requires us to
put this artifact in the distribution directory, which is a
subdirectory of www.apache.org/dist/ according to
http://www.apache.org/legal/release-policy.html#where-do-releases-go

BTW, just found the following from
https://incubator.apache.org/policy/incubation.html#releases
- the release archive MUST contain the word "incubating" in the filename; and
- the release archive MUST contain an Incubation disclaimer (as
described in the previous section), clearly visible in the main
documentation or README file.

We don't have "incubating" in the rc0 filename and DISCLAIMER seems
missing in the binary jars in
https://repository.apache.org/content/repositories/orgapacheratis-1007/

I guess we need a rc1?

Tsz-Wo
On Thu, Oct 11, 2018 at 10:43 PM Josh Elser  wrote:
>
> Thanks for the vote, Nicholas!
>
> On 10/10/18 10:43 PM, Tsz Wo Sze wrote:
>  > - untar and then "mvn install" does work for me.  It won't work if we
>  > run a second "mvn install" without clean.  "mvn install" works again
>  > after "mvn clean".  It seems not a problem.
>
> Will have to investigate what's going on.
>
> > Questions:
> > - Should we post a rc for the binary?
>
> I don't see any value for that, tbh. 99% of people are not going to know
> this even exists and will get it via Maven. In another line of thinking,
> the Maven repository I sent out "is" the binary release :)
>
> > - Now the project name becomes "Apache Ratis Thirdparty Parent" (and
> > the gz file name) instead of "Apache Ratis Thirdparty".  It is a
> > little odd.  How about using "Apache Ratis Thirdparty" for the root
> > module and "Apache Ratis Thirdparty Shaded" for the sub-module?  I am
> > fine if we do the rename later.
>
> More than happy to revisit naming later on :). I wasn't able to come up
> with a good name for our general Ratis dependencies module. "Apache
> Ratis Thirdparty Shaded" is probably the forerunner, but I don't feel
> like it's very descriptive. Need to think about that some more :)

Re: [VOTE] Apache Ratis Thirdparty 0.1.0rc0

[Tsz Wo Sze]

+1

- verified signature/checksum
- verified LICENSE, NOTICE, DISCLAIMER in
ratis-thirdparty-parent-0.1.0-src.tar.gz
- untar and then "mvn install" does work for me.  It won't work if we
run a second "mvn install" without clean.  "mvn install" works again
after "mvn clean".  It seems not a problem.

Questions:
- Should we post a rc for the binary?
- Now the project name becomes "Apache Ratis Thirdparty Parent" (and
the gz file name) instead of "Apache Ratis Thirdparty".  It is a
little odd.  How about using "Apache Ratis Thirdparty" for the root
module and "Apache Ratis Thirdparty Shaded" for the sub-module?  I am
fine if we do the rename later.

Thanks for a the hard works!
Tsz-Wo
On Wed, Oct 10, 2018 at 11:24 AM Josh Elser  wrote:
>
> I've noticed this once and again, but chalked it up to some issue with
> the shade plugin. I'm not quite sure where to start digging in to figure
> out why it happens... will have to start broad :)
>
> On 10/8/18 11:39 PM, Ted Yu wrote:
> > True.
> >
> > Though I wouldn't expect the 'mvn install' to fail :-)
> >
> > On Mon, Oct 8, 2018 at 8:14 PM Sergey Soldatov 
> > wrote:
> >
> >> I have the same result with mvn install. Actually, mvn clean install works
> >> fine.
> >>
> >> Thanks,
> >> Sergey
> >>
> >> On Mon, Oct 8, 2018 at 7:53 PM Ted Yu  wrote:
> >>
> >>> When running 'mvn install', I got:
> >>>
> >>> [ERROR] Failed to execute goal
> >>> org.apache.maven.plugins:maven-shade-plugin:3.1.1:shade (default) on
> >>> project ratis-thirdparty: Error creating shaded jar: duplicate entry:
> >>> META-INF/services/org.apache.ratis.thirdparty.io.grpc.ServerProvider ->
> >>> [Help 1]
> >>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> >>> goal org.apache.maven.plugins:maven-shade-plugin:3.1.1:shade (default) on
> >>> project ratis-thirdparty: Error creating shaded jar: duplicate entry:
> >>> META-INF/services/org.apache.ratis.thirdparty.io.grpc.ServerProvider
> >>>
> >>> Here is my environment:
> >>>
> >>> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
> >>> MaxPermSize=812M; support was removed in 8.0
> >>> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> >>> 2018-06-17T11:33:14-07:00)
> >>> Maven home: /Users/tyu/apache-maven-3.5.4
> >>> Java version: 1.8.0_151, vendor: Oracle Corporation, runtime:
> >>> /Library/Java/JavaVirtualMachines/jdk1.8.0_151.jdk/Contents/Home/jre
> >>> Default locale: en_US, platform encoding: UTF-8
> >>> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
> >>>
> >>> Did I use the correct command ?
> >>>
> >>> Thanks
> >>>
> >>> On Mon, Oct 8, 2018 at 4:29 PM Josh Elser  wrote:
> >>>
>  Hi,
> 
>  Please vote on the following release candidate to become Apache Ratis
>  Thirdparty 0.1.0.
> 
>  The Apache Ratis Thirdparty project is a collection of all thirdparty
>  dependencies that Apache Ratis uses, repackaged for optimal use by
>  Ratis. As such, there is very little net-new source code in this
> >> project.
> 
>  The source release is present at
> 
> 
> >>>
> >> https://dist.apache.org/repos/dist/dev/incubator/ratis/thirdparty/0.1.0-rc0/
> 
>  SHA512 checksum is on the source tarball: A8A11CD5 447CD3AB 2341C878
>  E3DB4AEF 565224E5 FEC599DF 36143EAB 0999437B 767860FE
> 54E3DC2C D4A265D1 E844979E 4D311CDD 97BC7797 CF66219A 3331D9F1
> 
>  This source release was created from the Git commit SHA1:
>  9e525162fcec8650b2d08dfdcbcdaee76231cc08. For your convenience, there
> >> is
>  also a GPG-signed tag with the name "ratis-thirdparty-0.1.0" that also
>  points at this commit.
> 
>  This source release was signed with my key: 4677D66C. This is present
> >> in
>  the KEYS file (dist/dev and dist/release).
> 
>  The corresponding "binaries" for this release are staged at
> 
> >> https://repository.apache.org/content/repositories/orgapacheratis-1007/
>  and will be promoted pending successful PPMC and IPMC votes. You can
>  update your local ~/.m2/settings.xml to add this as a repository to
> >> test
>  the build of ratis.git if you choose (appears to work fine for me).
> 
>  This vote will be open for at least 72hours (until 2018/10/12 00:00:00
>  GMT).
> 
>  - Josh
> 
>  ps: big thanks to Nicholas and Marton who helped out with this release
>  (sorry if I'm forgetting anyone else!)
> 
> >>>
> >>
> >

Re: Rolling RC for ratis-thirdparty

[Tsz Wo Sze]

I just have committed RATIS-340 (Thanks. Josh for reviewing it).   I
think we are ready for a thirdparty release now.
Tsz-Wo
On Fri, Oct 5, 2018 at 4:10 PM Tsz Wo Sze  wrote:
>
> I just have filed https://issues.apache.org/jira/browse/RATIS-340 and
> attached some patches.
> Tsz-Wo
> On Fri, Oct 5, 2018 at 3:53 PM Tsz Wo Sze  wrote:
> >
> > Josh,
> >
> > Thanks for taking care ratis-thridparty.
> >
> > I found two minor problems:
> > - org.apache.hadoop.ipc.protobuf is shaded to
> > org.apache.ratis.shaded.* but not org.apache.ratis.thirdparty.*.
> > - ratis-thridparty needs a README.md.
> >
> > Let me file a JIRA.
> >
> > Tsz-Wo
> >
> > On Fri, Oct 5, 2018 at 2:59 AM Josh Elser  wrote:
> > >
> > > (Finally) Pushed RATIS-335 to pull Hadoop shading into the thirdparty
> > > repo. Pushed a new SNAPSHOT build to asf nexus which should prevent any
> > > build-related errors (if you see something, make sure you rebase/merge
> > > ratis.git on top of master and/or use `mvn -U` to force a SNAPSHOT 
> > > refresh).
> > >
> > > AFAIK, we're good for a thirdparty release and will start working on an
> > > RC. Shout if there's anything you notice that needs to be fixed prior.
> > >
> > > Thanks!

Re: Rolling RC for ratis-thirdparty

[Tsz Wo Sze]

I just have filed https://issues.apache.org/jira/browse/RATIS-340 and
attached some patches.
Tsz-Wo
On Fri, Oct 5, 2018 at 3:53 PM Tsz Wo Sze  wrote:
>
> Josh,
>
> Thanks for taking care ratis-thridparty.
>
> I found two minor problems:
> - org.apache.hadoop.ipc.protobuf is shaded to
> org.apache.ratis.shaded.* but not org.apache.ratis.thirdparty.*.
> - ratis-thridparty needs a README.md.
>
> Let me file a JIRA.
>
> Tsz-Wo
>
> On Fri, Oct 5, 2018 at 2:59 AM Josh Elser  wrote:
> >
> > (Finally) Pushed RATIS-335 to pull Hadoop shading into the thirdparty
> > repo. Pushed a new SNAPSHOT build to asf nexus which should prevent any
> > build-related errors (if you see something, make sure you rebase/merge
> > ratis.git on top of master and/or use `mvn -U` to force a SNAPSHOT refresh).
> >
> > AFAIK, we're good for a thirdparty release and will start working on an
> > RC. Shout if there's anything you notice that needs to be fixed prior.
> >
> > Thanks!

Re: Rolling RC for ratis-thirdparty

[Tsz Wo Sze]

Josh,

Thanks for taking care ratis-thridparty.

I found two minor problems:
- org.apache.hadoop.ipc.protobuf is shaded to
org.apache.ratis.shaded.* but not org.apache.ratis.thirdparty.*.
- ratis-thridparty needs a README.md.

Let me file a JIRA.

Tsz-Wo

On Fri, Oct 5, 2018 at 2:59 AM Josh Elser  wrote:
>
> (Finally) Pushed RATIS-335 to pull Hadoop shading into the thirdparty
> repo. Pushed a new SNAPSHOT build to asf nexus which should prevent any
> build-related errors (if you see something, make sure you rebase/merge
> ratis.git on top of master and/or use `mvn -U` to force a SNAPSHOT refresh).
>
> AFAIK, we're good for a thirdparty release and will start working on an
> RC. Shout if there's anything you notice that needs to be fixed prior.
>
> Thanks!

Re: Heads-up: RATIS-316 landed

[Tsz Wo Sze]

Josh,

Thanks a lot for cleaning up the pom!  It becomes much easier to build ratis.

Tsz-Wo
On Fri, Sep 21, 2018 at 8:19 AM Josh Elser  wrote:
>
> Hi everyone,
>
> Just a quick-heads up that you'll see some changes in master today that
> change how you may do your normal development. Check out RATIS-316 for
> the full story, but let me try to summarize here:
>
> * "Thirdparty" (e.g. protobuf, grpc, netty) dependencies are no long in
> ratis-proto-shaded
> * ratis-proto-shaded is now just ratis-proto, only containing generated code
> * There is a new repository
> https://github.com/apache/incubator-ratis-thirdparty which is solely
> devoted to containing the aforementioned thirdparty dependencies.
> * I've deployed a SNAPSHOT build of that to Nexus -- will be working on
> a release
> * The imports have changed slightly for pb-generated code and our
> packaged thirdparty code. This should all be reflected in BUILDING.md
>
> Please reach out if you have any confusion! This should be the last
> annoying build-related change from me for a while ;)
>
> - Josh

Re: RC1: Call for vote

[Tsz Wo Sze]

+1
I have verified all checksums and signatures and run some manual tests
with the examples.  Everything looks good.  Thanks, Marton!

Tsz-Wo

On Mon, May 21, 2018 at 9:35 AM, Mukul Kumar Singh
 wrote:
> Thanks for creating a new release Marton.
>
> +1
> Tested Ozone with latest ratis and ran data I/O operation using Freon.
>
> Thanks,
> Mukul
>
> On 21/05/18, 8:18 PM, "Elek, Marton"  wrote:
>
> I extend the deadline of the vote. Kindly ask to check the package and
> vote if you have time.
>
> Thanks a lot.
>
> https://dist.apache.org/repos/dist/dev/incubator/ratis/0.2.0/rc1/
>
> Marton
>
> On 05/16/2018 11:50 PM, Elek, Marton wrote:
> >
> > Hi all,
> >
> > I'd like to restart the vote to release Apache Ratis (incubating) 0.2.0
> > as we fixed all the previously discussed issues.
> >
> >
> >
> > This is the second incubator release and it includes more than 120
> > improvements and fixes since the previous 0.1.0-alpha release. This is
> > the first release
> > which includes a binary package with ready to use example project.
> >
> > All distribution packages, including signatures, digests, etc. can be
> > found at:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/ratis/0.2.0/rc1
> >
> > Staged artifacts can be found at:
> >
> > https://repository.apache.org/content/repositories/orgapacheratis-1004
> >
> >
> > This release has been signed with PGP key 0EE79B28, corresponding to
> > e...@apache.org, which is included in the repository's KEYS file
> > (https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS).
> >
> > This key can be found on keyservers, such as:
> >
> > http://pgp.mit.edu/pks/lookup?op=get=0x0EE79B28
> >
> > Or in the apache phonebook:
> >
> > https://people.apache.org/keys/committer/elek.asc
> >
> >
> > The release candidate has been tagged in git with ratis-0.2.0-rc1
> > (bd234f25c29e918ad3db88bfedcc2d6931221a3e)
> >
> > https://github.com/apache/incubator-ratis/releases/tag/ratis-0.2.0-rc1
> >
> >
> >
> > Please review and vote. The vote will be open for at least 72 hours.
> >
> > If the vote passed, the second stage vote will be called on the Apache
> > incubator mailing list to get approval from the Incubator PMC.
> >
> >
> >
> >   # Review/testing
> >
> > You can check the usual requirements of an apache release:
> >
> >   • Signatures
> >   • Checksums
> >   • License and notice files
> >   • Disclaimer file (incubator!)
> >   • Build the project from the source code package (mvn clean install
> > assembly:single -DskipTests=true )
> >   • Licence headers
> >
> > The binary papckage can be smoketested with:
> >
> > ./examples/bin/start-all.sh
> > ./examples/bin/client.sh assign --name a --value 2
> > ./examples/bin/client.sh get --name a
> >
> >
> >
> > Starting with my vote: +1
> >
> > Thanks,
> > Marton
>
>
>

Re: [VOTE] Release of Apache Ratis (incubating) 0.2.0 (rc1)​

[Tsz Wo Sze]

Thanks Marton.

We can generate mds by "gpg --print-mds ".  See also
ratis/dev-support/make_rc.sh

Tsz-Wo

On Fri, May 18, 2018 at 5:49 AM, Elek, Marton  wrote:
> I just found (thanks to RATIS-241) that the previous release provided mds
> files as checksum. So I just added mds files as well (you can see that the
> sha hash is the same).
>
> But as I don't know any easy method to verify the mds files [1] I would link
> the sha-512 from the ratis web page.
>
> Please check the release candidate and vote.
>
> Thanks
> Marton
>
> [1]
> https://superuser.com/questions/1117048/how-to-verify-checksum-in-a-mds-file-format
>
>
>
> On 05/16/2018 11:50 PM, Elek, Marton wrote:
>>
>>
>> Hi all,
>>
>> I'd like to restart the vote to release Apache Ratis (incubating) 0.2.0 as
>> we fixed all the previously discussed issues.
>>
>>
>>
>> This is the second incubator release and it includes more than 120
>> improvements and fixes since the previous 0.1.0-alpha release. This is the
>> first release
>> which includes a binary package with ready to use example project.
>>
>> All distribution packages, including signatures, digests, etc. can be
>> found at:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/ratis/0.2.0/rc1
>>
>> Staged artifacts can be found at:
>>
>> https://repository.apache.org/content/repositories/orgapacheratis-1004
>>
>>
>> This release has been signed with PGP key 0EE79B28, corresponding to
>> e...@apache.org, which is included in the repository's KEYS file
>> (https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS).
>>
>> This key can be found on keyservers, such as:
>>
>> http://pgp.mit.edu/pks/lookup?op=get=0x0EE79B28
>>
>> Or in the apache phonebook:
>>
>> https://people.apache.org/keys/committer/elek.asc
>>
>>
>> The release candidate has been tagged in git with ratis-0.2.0-rc1
>> (bd234f25c29e918ad3db88bfedcc2d6931221a3e)
>>
>> https://github.com/apache/incubator-ratis/releases/tag/ratis-0.2.0-rc1
>>
>>
>>
>> Please review and vote. The vote will be open for at least 72 hours.
>>
>> If the vote passed, the second stage vote will be called on the Apache
>> incubator mailing list to get approval from the Incubator PMC.
>>
>>
>>
>>   # Review/testing
>>
>> You can check the usual requirements of an apache release:
>>
>>   • Signatures
>>   • Checksums
>>   • License and notice files
>>   • Disclaimer file (incubator!)
>>   • Build the project from the source code package (mvn clean install
>> assembly:single -DskipTests=true )
>>   • Licence headers
>>
>> The binary papckage can be smoketested with:
>>
>> ./examples/bin/start-all.sh
>> ./examples/bin/client.sh assign --name a --value 2
>> ./examples/bin/client.sh get --name a
>>
>>
>>
>> Starting with my vote: +1
>>
>> Thanks,
>> Marton

Re: [VOTE] Release of Apache Ratis (incubating) 0.2.0 (rc0)

[Tsz Wo Sze]

Agree.  Let's fix #2 - #5 for now.

I have a comment on the release version: In the previous release, we
called it 0.1.0-alpha.  How about we use 0.2.0-alpha for the next
release?

Tsz-Wo

On Tue, May 8, 2018 at 2:16 PM, Elek, Marton <e...@apache.org> wrote:
>
> Hi,
>
> thank you the test and feedback for all of you.
>
> As a summary. The problems until now:
>
>  1. Unit test failures
>  2. OpenConsensus shading problem: RATIS-237
>  3. Copyright 2017
>  4. Missing information about increasing MVN memory.
>  5. Licence headers in shaded jar files
>
>
>
> 3/4: are not blockers (IMHO)
>
> 2: I think it's a blocker. As some of our unit tests are fragile and
> intermittent (1.) Hadoop Ozone could give us additional confidence about the
> stability of the release. Also we would like to provide a stable Ratis
> version to Ozone, so they should work together.
>
> I would cancel this vote. And initialize a new one with RATIS-237 (+ the
> trival fixes).
>
> 5. I am not sure if it's blocker or not (as LICENSE.txt is ok), but I think
> the shaded sources should not be included in the source distribution. I
> think they are  just external dependencies similar to other maven
> dependencies (just on the source level). I would fix it with removing the
> src/main/java of the shaded project from the src release.
>
> 1. As I mentioned some of the unit tests seem to be fragile (see
> https://builds.apache.org/job/ratis-qbt-master-java8-linux-x86/). I don't
> think it's a blocker (but would be great to fix them long-term).
>
> Summary: I cancel this vote and propose to include the fix of 2,3,4,5 in rc1
> (hopefully very soon).
>
> But this is just my view. Please let me know what do you think...
>
> Thanks a lot,
> Marton
>
>
>
>
>
>
>
>
>
> On 05/08/2018 10:08 PM, Tsz Wo Sze wrote:
>>
>> Thanks Nanda for the explanation.
>>
>> I seem able to fix the io.opencensus shading problem.  Just have
>> posted a patch on RATIS-237.
>>
>> Tsz-Wo
>>
>> On Mon, May 7, 2018 at 8:28 PM, Nandakumar Vadivelu
>> <nvadiv...@hortonworks.com> wrote:
>>>
>>> Hi Tsz-Wo,
>>>
>>> True, there is only one version of opencensus in Ratis. Since we do
>>> shading of io.grpc we end up with new shaded class of ContextUtils (same
>>> fully qualified class name, but the reference of io.grpc inside the class is
>>> modified/relocated), we also have non shaded ContextUtils. Both are referred
>>> through Ratis dependency.
>>>
>>> The below is dependency tree of Ratis:
>>>
>>> [INFO] +-
>>> org.apache.ratis:ratis-proto-shaded:jar:0.1.1-alpha-SNAPSHOT:compile
>>> => Modified opencensus packed with proto-shaded
>>> [INFO] |  +- com.google.auto.value:auto-value-annotations:jar:1.6:compile
>>> [INFO] |  +- com.google.guava:guava:jar:24.1-jre:compile
>>> [INFO] |  |  +- com.google.code.findbugs:jsr305:jar:1.3.9:compile
>>> [INFO] |  |  +-
>>> org.checkerframework:checker-compat-qual:jar:2.0.0:compile
>>> [INFO] |  |  +-
>>> com.google.errorprone:error_prone_annotations:jar:2.1.3:compile
>>> [INFO] |  |  +- com.google.j2objc:j2objc-annotations:jar:1.1:compile
>>> [INFO] |  |  \-
>>> org.codehaus.mojo:animal-sniffer-annotations:jar:1.14:compile
>>> [INFO] |  \- com.squareup:javapoet:jar:1.10.0:compile
>>> [INFO] +- org.apache.ratis:ratis-common:jar:0.1.1-alpha-SNAPSHOT:compile
>>> [INFO] |  +- org.slf4j:slf4j-api:jar:1.7.10:compile
>>> [INFO] |  +- org.slf4j:slf4j-log4j12:jar:1.7.10:compile
>>> [INFO] |  |  \- log4j:log4j:jar:1.2.17:compile
>>> [INFO] |  \- io.dropwizard.metrics:metrics-core:jar:3.2.5:compile
>>> [INFO] +- org.apache.ratis:ratis-client:jar:0.1.1-alpha-SNAPSHOT:compile
>>> [INFO] +- org.apache.ratis:ratis-server:jar:0.1.1-alpha-SNAPSHOT:compile
>>> [INFO] +- org.apache.ratis:ratis-netty:jar:0.1.1-alpha-SNAPSHOT:compile
>>> [INFO] |  \- org.jctools:jctools-core:jar:2.1.2:compile
>>> [INFO] \- org.apache.ratis:ratis-grpc:jar:0.1.1-alpha-SNAPSHOT:compile
>>> [INFO]+- io.opencensus:opencensus-api:jar:0.12.2:compile
>>> => Original jar
>>> [INFO]|  \- io.grpc:grpc-context:jar:1.9.0:compile
>>> [INFO]\-
>>> io.opencensus:opencensus-contrib-grpc-metrics:jar:0.12.2:compile
>>>
>>>
>>> nvadivelu@HW12726 ~/w/t/p/o/t/dependency> javap -classpath
>>> ".:./opencensus-api-0.12.2.jar" io.opencensus.trace.unsafe.ContextUtils
>>> Compiled from "ContextUtils.java"
>>> public final cl

Re: [VOTE] Release of Apache Ratis (incubating) 0.2.0 (rc0)

[Tsz Wo Sze]

Thanks Nanda for the explanation.

I seem able to fix the io.opencensus shading problem.  Just have
posted a patch on RATIS-237.

Tsz-Wo

On Mon, May 7, 2018 at 8:28 PM, Nandakumar Vadivelu
<nvadiv...@hortonworks.com> wrote:
> Hi Tsz-Wo,
>
> True, there is only one version of opencensus in Ratis. Since we do shading 
> of io.grpc we end up with new shaded class of ContextUtils (same fully 
> qualified class name, but the reference of io.grpc inside the class is 
> modified/relocated), we also have non shaded ContextUtils. Both are referred 
> through Ratis dependency.
>
> The below is dependency tree of Ratis:
>
> [INFO] +- 
> org.apache.ratis:ratis-proto-shaded:jar:0.1.1-alpha-SNAPSHOT:compile  
>   => Modified opencensus packed with proto-shaded
> [INFO] |  +- com.google.auto.value:auto-value-annotations:jar:1.6:compile
> [INFO] |  +- com.google.guava:guava:jar:24.1-jre:compile
> [INFO] |  |  +- com.google.code.findbugs:jsr305:jar:1.3.9:compile
> [INFO] |  |  +- org.checkerframework:checker-compat-qual:jar:2.0.0:compile
> [INFO] |  |  +- 
> com.google.errorprone:error_prone_annotations:jar:2.1.3:compile
> [INFO] |  |  +- com.google.j2objc:j2objc-annotations:jar:1.1:compile
> [INFO] |  |  \- org.codehaus.mojo:animal-sniffer-annotations:jar:1.14:compile
> [INFO] |  \- com.squareup:javapoet:jar:1.10.0:compile
> [INFO] +- org.apache.ratis:ratis-common:jar:0.1.1-alpha-SNAPSHOT:compile
> [INFO] |  +- org.slf4j:slf4j-api:jar:1.7.10:compile
> [INFO] |  +- org.slf4j:slf4j-log4j12:jar:1.7.10:compile
> [INFO] |  |  \- log4j:log4j:jar:1.2.17:compile
> [INFO] |  \- io.dropwizard.metrics:metrics-core:jar:3.2.5:compile
> [INFO] +- org.apache.ratis:ratis-client:jar:0.1.1-alpha-SNAPSHOT:compile
> [INFO] +- org.apache.ratis:ratis-server:jar:0.1.1-alpha-SNAPSHOT:compile
> [INFO] +- org.apache.ratis:ratis-netty:jar:0.1.1-alpha-SNAPSHOT:compile
> [INFO] |  \- org.jctools:jctools-core:jar:2.1.2:compile
> [INFO] \- org.apache.ratis:ratis-grpc:jar:0.1.1-alpha-SNAPSHOT:compile
> [INFO]+- io.opencensus:opencensus-api:jar:0.12.2:compile  
>   => Original jar
> [INFO]|  \- io.grpc:grpc-context:jar:1.9.0:compile
> [INFO]\- io.opencensus:opencensus-contrib-grpc-metrics:jar:0.12.2:compile
>
>
> nvadivelu@HW12726 ~/w/t/p/o/t/dependency> javap -classpath 
> ".:./opencensus-api-0.12.2.jar" io.opencensus.trace.unsafe.ContextUtils
> Compiled from "ContextUtils.java"
> public final class io.opencensus.trace.unsafe.ContextUtils {
>   public static final io.grpc.Context$Key 
> CONTEXT_SPAN_KEY;
>   static {};
> }
>
> nvadivelu@HW12726 ~/w/t/p/o/t/dependency> javap -classpath 
> ".:./ratis-proto-shaded-0.1.1-alpha-SNAPSHOT.jar" 
> io.opencensus.trace.unsafe.ContextUtils
> Compiled from "ContextUtils.java"
> public final class io.opencensus.trace.unsafe.ContextUtils {
>   public static final 
> org.apache.ratis.shaded.io.grpc.Context$Key 
> CONTEXT_SPAN_KEY;
>   static {};
> }
>
>
> -Nanda
>
> On 5/8/18, 4:16 AM, "Tsz Wo Sze" <szets...@gmail.com> wrote:
>
> > The problem is because of two different definition of 
> io.opencensus.trace.unsafe.ContextUtils class present in the classpath. The 
> reason for having two different definition of ContextUtils in classpath is 
> due to the fact that we are shading/relocating io.grpc and not io.opencensus.
>
> Nanda, in Ratis, there is only one version (0.12.2) of opencensus.  It
> seems that another version of opencensus is pulled outside Ratis.
>
> Tsz-Wo
>
>
> On Mon, May 7, 2018 at 11:58 AM, Nandakumar Vadivelu
> <nvadiv...@hortonworks.com> wrote:
> > I'm not sure why the file is missing, I can see the attachment in my 
> "sent items".
> >
> > Patch content for reference
> >
> > diff --git a/ratis-grpc/pom.xml b/ratis-grpc/pom.xml
> > index a3c3cc1..ebb73cc 100644
> > --- a/ratis-grpc/pom.xml
> > +++ b/ratis-grpc/pom.xml
> > @@ -85,15 +85,5 @@
> >jctools-core
> >  
> >
> > -
> > -  io.opencensus
> > -  opencensus-api
> > -  ${io.opencensus.version}
> > -
> > -
> > -  io.opencensus
> > -  opencensus-contrib-grpc-metrics
> > -  ${io.opencensus.version}
> > -
> >
> >  
> >
> > I will also create a jira under RATIS
> >
> > -Nanda
> >
> > On 5/8/18, 12:23 AM, "Ted Yu" <yuzhih...@gmail.com> wrote:
&g

Re: [VOTE] Release of Apache Ratis (incubating) 0.2.0 (rc0)

[Tsz Wo Sze]

Marton,

I compared you keys in two locations below
- https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS
- http://pgp.mit.edu/pks/lookup?op=get=on=0x78434EF460D6914B

They somehow look different.  They match until "Zz6JA".  Do you know why?

Tsz-Wo

On Sun, May 6, 2018 at 3:57 AM, Elek, Marton  wrote:
>
> Hi all,
>
> I'd like to call a vote to release Apache Ratis (incubating) 0.2.0.
>
> This is the second incubator release and it includes more than 120
> improvements and fixes since the previous 0.1.0-alpha release. This is the
> first release
> which includes a binary package with ready to use example project.
>
> All distribution packages, including signatures, digests, etc. can be
> found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/ratis/0.2.0/rc0/
>
> Staged artifacts can be found at:
>
> https://repository.apache.org/content/repositories/orgapacheratis-1003/
>
>
> This release has been signed with PGP key 0EE79B28, corresponding to
> e...@apache.org, which is included in the repository's KEYS file
> (https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS).
>
> This key can be found on keyservers, such as:
>
> http://pgp.mit.edu/pks/lookup?op=get=0x0EE79B28
>
> Or in the apache phonebook:
>
> https://people.apache.org/keys/committer/elek.asc
>
>
> The release candidate has been tagged in git with ratis-0.2.0-rc0 (ee4936d)
>
> https://github.com/apache/incubator-ratis/releases/tag/ratis-0.2.0-rc0
>
>
>
> Please review and vote. The vote will be open for at least 72 hours.
>
> If the vote passed, the second stage vote will be called on the Apache
> incubator mailing list to get approval from the Incubator PMC.
>
>
>
>  # Review/testing
>
> You can check the usual requirements of an apache release:
>
>  • Signatures
>  • Checksums
>  • License and notice files
>  • Disclaimer file (incubator!)
>  • Build the project from the source code package (mvn clean install
> assembly:single -DskipTests=true )
>  • Licence headers
>
> The binary papckage can be smoketested with:
>
> ./examples/bin/start-all.sh
> ./examples/bin/client.sh assign --name a --value 2
> ./examples/bin/client.sh get --name a
>
>
>
> Starting with my vote: +1
>
> Thanks,
> Marton

Re: [VOTE] Release of Apache Ratis (incubating) 0.2.0 (rc0)

[Tsz Wo Sze]

> The problem is because of two different definition of 
> io.opencensus.trace.unsafe.ContextUtils class present in the classpath. The 
> reason for having two different definition of ContextUtils in classpath is 
> due to the fact that we are shading/relocating io.grpc and not io.opencensus.

Nanda, in Ratis, there is only one version (0.12.2) of opencensus.  It
seems that another version of opencensus is pulled outside Ratis.

Tsz-Wo


On Mon, May 7, 2018 at 11:58 AM, Nandakumar Vadivelu
 wrote:
> I'm not sure why the file is missing, I can see the attachment in my "sent 
> items".
>
> Patch content for reference
>
> diff --git a/ratis-grpc/pom.xml b/ratis-grpc/pom.xml
> index a3c3cc1..ebb73cc 100644
> --- a/ratis-grpc/pom.xml
> +++ b/ratis-grpc/pom.xml
> @@ -85,15 +85,5 @@
>jctools-core
>  
>
> -
> -  io.opencensus
> -  opencensus-api
> -  ${io.opencensus.version}
> -
> -
> -  io.opencensus
> -  opencensus-contrib-grpc-metrics
> -  ${io.opencensus.version}
> -
>
>  
>
> I will also create a jira under RATIS
>
> -Nanda
>
> On 5/8/18, 12:23 AM, "Ted Yu"  wrote:
>
> I don't see patch attached.
>
> Please create RATIS JIRA and attach there.
>
> Thanks
>
> On Mon, May 7, 2018 at 10:24 AM, Nandakumar Vadivelu <
> nvadiv...@hortonworks.com> wrote:
>
> > Hi All,
> >
> > Below is the exception which we get with Ratis 0.2.0
> >
> > java.lang.NoSuchFieldError: CONTEXT_SPAN_KEY
> >   at org.apache.ratis.shaded.io.grpc.internal.CensusTracingModule$
> > ServerTracer.filterContext(CensusTracingModule.java:340)
> >   at org.apache.ratis.shaded.io.grpc.internal.StatsTraceContext.
> > serverFilterContext(StatsTraceContext.java:121)
> >   at org.apache.ratis.shaded.io.grpc.internal.ServerImpl$
> > ServerTransportListenerImpl.createContext(ServerImpl.java:482)
> >   at org.apache.ratis.shaded.io.grpc.internal.ServerImpl$
> > ServerTransportListenerImpl.streamCreated(ServerImpl.java:416)
> > 
> >
> >
> > The problem is because of two different definition of
> > io.opencensus.trace.unsafe.ContextUtils class present in the classpath.
> > The reason for having two different definition of ContextUtils in 
> classpath
> > is due to the fact that we are shading/relocating io.grpc and not
> > io.opencensus.
> >
> >
> > With shading we are generating the below definition which ends up in
> > ratis-proto-shaded jar
> >
> > package io.opencensus.trace.unsafe;
> >
> > import org.apache.ratis.shaded.io.grpc.Context;
> > import io.opencensus.trace.Span;
> >
> > /**
> >  * Util methods/functionality to interact with the {@link
> > org.apache.ratis.shaded.io.grpc.Context}.
> >  *
> >  * Users must interact with the current Context via the public APIs 
> in
> > {@link
> >  * io.opencensus.trace.Tracer} and avoid usages of the {@link
> > #CONTEXT_SPAN_KEY} directly.
> >  *
> >  * @since 0.5
> >  */
> > public final class ContextUtils {
> >   // No instance of this class.
> >   private ContextUtils() {}
> >
> >   /**
> >* The {@link org.apache.ratis.shaded.io.grpc.Context.Key} used to
> > interact with {@link org.apache.ratis.shaded.io.grpc.Context}.
> >*
> >* @since 0.5
> >*/
> >   public static final Context.Key CONTEXT_SPAN_KEY =
> > Context.key("opencensus-trace-span-key");
> > }
> >
> >
> > Since we have added io.opencensus as direct dependency in ratis-grpc we
> > get the below definition in io.opencensus:opencensus-api:jar
> >
> > package io.opencensus.trace.unsafe;
> >
> > import io.grpc.Context;
> > import io.opencensus.trace.Span;
> >
> > /**
> >  * Util methods/functionality to interact with the {@link 
> io.grpc.Context}.
> >  *
> >  * Users must interact with the current Context via the public APIs 
> in
> > {@link
> >  * io.opencensus.trace.Tracer} and avoid usages of the {@link
> > #CONTEXT_SPAN_KEY} directly.
> >  *
> >  * @since 0.5
> >  */
> > public final class ContextUtils {
> >   // No instance of this class.
> >   private ContextUtils() {}
> >
> >   /**
> >* The {@link io.grpc.Context.Key} used to interact with {@link
> > io.grpc.Context}.
> >*
> >* @since 0.5
> >*/
> >   public static final Context.Key CONTEXT_SPAN_KEY =
> > Context.key("opencensus-trace-span-key");
> > }
> >
> > Both of the jars end up in classpath and ContextUtils is getting loaded
> > from io.opencensus:opencensus-api:jar which is causing the problem.
> >
> > The simple fix would be to remove the dependency of io.opencensus from
> > ratis-grpc/pom.xml (patch for the same is attached in this mail). This 
> is
> > not a 

Re: 0.2.0 release?

[Tsz Wo Sze]

Marton,

Thanks for tracking the issues.  All RATIS-227, RATIS-228 and
RATIS-229 are new resolved and there are no more blockers.  Let's roll
a release?

Tsz-Wo

On Mon, Apr 23, 2018 at 3:46 AM, Marton, Elek <e...@apache.org> wrote:
> Quick update:
>
>
> TLDR; We need RATIS-227/RATIS-228 (and imho RATIS-229) for the 0.2.0
> release.
>
>
>
> Current Blocker/Patch Available jiras:
>
> BLOCKER:
>
> RATIS-227 TestRaftWithGrpc.testBasicAppendEntriesWithAllReplication fails
> --> No patch, yet
>
> RATIS-228 Handle zero size log_inprogress file
> --> Patch available, seems to be ok for me, but not enough experience with
> the file writing. Please review if you have time.
>
> NON-BLOCKER:
>
> RATIS-229 GRpcLogAppender should trigger a heartbeat when appendEntries
> Patch Available -> but "need more testing". Seems to be a real problem which
> should be included, question is open about the implementation.
>
> RATIS-230: Improve gRPC log messages
> Patch Available -> seems to be ok for me, checkstyle issues
>
> RATIS-222 Handle Error exception when Unassigned Variable is tried to get .
> Patch Available --> I think it should be fixed in different location with
> fixing the error handling of the arithmetic state machine
>
> RATIS-218 Optimize heartbeating in Ratis for Grpc protocol
> --> Reviewed, response is pending
>
>
> Marton
>
>
> On 04/17/2018 05:35 AM, Tsz Wo Sze wrote:
>>
>> I agreed that RATIS-227 is a blocker.  Let me ping Kit for fixing it.
>> Tsz-Wo
>>
>> On Tue, Apr 17, 2018 at 4:53 AM, Elek, Marton <e...@apache.org> wrote:
>>>
>>> Fair enough, I modified the priority of RATIS-227 to blocker. Let's see
>>> if
>>> we can get it soon.
>>>
>>> In the meantime I created a preview version of the release:
>>> https://home.apache.org/~elek/ratis-preview (NON OFFICIAL ARTIFACTS!)
>>>
>>> And requested reviews from the incubator mentors. Hopefully we can start
>>> a
>>> vote at the end of this week.
>>>
>>> Marton
>>>
>>>
>>> On 04/16/2018 05:31 PM, Lokesh Jain wrote:
>>>>
>>>>
>>>> I think we can have RATIS-227 in 0.2.0 release as well. There might be a
>>>> possible bug which needs to be fixed.
>>>>
>>>> Thanks
>>>> Lokesh
>>>>
>>>
>

Re: [VOTE#2] Merge RATIS-5 to a new branch and publish the new site

[Tsz Wo Sze]

+1  The web site looks good.  Thanks!
Tsz-Wo

On Thu, Jan 18, 2018 at 12:11 AM, Mukul Kumar Singh
 wrote:
> +1
>
> -Mukul
>
> On 16/01/18, 10:56 AM, "Jitendra Pandey"  wrote:
>
> +1
>
> On 1/15/18, 10:04 AM, "anu engineer"  wrote:
>
> +1
>
> --Anu
>
>
> On Mon, Jan 15, 2018 at 5:00 AM, Marton, Elek  wrote:
>
> > Hi,
> >
> > We got valuable feedback from the incubator mailing list an 
> improved the
> > proposed site according to the apache guidelines.
> >
> > So I start a new Vote to merge it. Please have a final look to the
> > proposed web site and VOTE if you agree to publish it.
> >
> > As a reminder:
> >
> >  * Rendered site is here: https://elek.github.io/ratis-site/
> >  * Source is on the RATIS-5 branch
> >  * both the rendered and source version is uploaded to RATIS-5.
> >
> > This VOTE will open for 5 days and will end of 20th of January.
> >
> > Thanks,
> > Marton
> >
> > FTR. The original vote thread started here: 
> http://mail-archives.apache.or
> > g/mod_mbox/ratis-dev/201712.mbox/browser
> >
> >
> >
>
>
>
>

Re: [DISCUSS] 0.2-alpha release

[Tsz Wo Sze]

That's great if you like to be the release manager. Thanks!

If we want to include binary release, we must update NOTICE.txt to
include all the third-party works bundled in the binary.  See
- http://www.apache.org/legal/release-policy.html#licensing-documentation
- http://apache.org/legal/src-headers.html#notice

Nicholas


On Fri, Dec 15, 2017 at 11:02 PM, Elek, Marton <h...@anzix.net> wrote:
>
> 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 <szets...@gmail.com> 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

Re: ratis web page

[Tsz Wo Sze]

The web site looks really good.  Thanks a lot for all the hard and
beautiful works!
Nicholas

On Sat, Dec 16, 2017 at 3:22 AM, anu engineer <anu.engin...@gmail.com> wrote:
> Since it is a Ratis branch, should we do a formal vote and merge like
> Hadoop?  I have looked at the changes very deeply and I am happy with it,
> but I would like to establish conventions on how to merge code into Ratis.
> Thoughts ?
>
> Thanks
> Anu
>
>
> On Fri, Dec 15, 2017 at 3:09 AM, Elek, Marton <h...@anzix.net> wrote:
>
>> Hi,
>>
>> The final proposed version could be checked here:
>>
>> https://elek.github.io/ratis-site/
>>
>> The source is attached to the jira https://issues.apache.org/jira
>> /browse/RATIS-5
>>
>> Please have a final look and comment.
>>
>> If no more objections, I will commit both the source and rendered version
>> to separated branches (asf-site-source/asf-site) and open an INFRA ticket
>> to use it as the source of http://ratis.incubator.apache.org/
>>
>> Thanks,
>> Marton
>>
>>
>> On 11/18/2017 03:49 PM, Anu Engineer wrote:
>>
>>> Let us move this discussion to the JIRA, https://issues.apache.org/jira
>>> /browse/RATIS-5
>>> That way we will not lose these ideas/work items.
>>>
>>> Thanks
>>> Anu
>>>
>>>
>>> On 11/18/17, 5:18 AM, "Mukul Kumar Singh" <msi...@hortonworks.com> wrote:
>>>
>>>  +1, Excellent idea.
>>>   I was also thinking if we an add pages for some example on how
>>> to setup and use ratis in applications.
>>>   Thanks,
>>>  Mukul
>>>   > On 18-Nov-2017, at 4:12 AM, Hugo Louro <hmclo...@gmail.com>
>>> wrote:
>>>  >
>>>  > +1 - Great idea. I wonder if there are some templates around
>>>  > incubator/Apache projects that you can use that will make it
>>> easier and
>>>  > more consistent with other projects.
>>>  >
>>>  > I am not sure I follow the reason to have this in a google doc.
>>> Why not use
>>>  > html/markdown with Git alone. You can have this in it's own branch
>>> to
>>>  > start, and then when it's ready you can simply create a pull
>>> request.
>>>  >
>>>  > Thanks
>>>  > Hugo
>>>  >
>>>  > On Fri, Nov 17, 2017 at 11:20 AM, Tsz Wo Sze <szets...@gmail.com>
>>> wrote:
>>>  >
>>>  >> Thanks a lot, Marton.  I just have assigned RATIS-5 "Setup
>>> website" to you.
>>>  >> Nicholas
>>>  >>
>>>  >> On Fri, Nov 17, 2017 at 11:10 AM, Jing Zhao <ji...@apache.org>
>>> wrote:
>>>  >>> +1. Thanks Marton!
>>>  >>>
>>>  >>> On Fri, Nov 17, 2017 at 9:43 AM, Anu Engineer <
>>> aengin...@hortonworks.com
>>>  >>>
>>>  >>> wrote:
>>>  >>>
>>>  >>>> +1, great idea. I would like to work with you on this.
>>>  >>>>
>>>  >>>> Thanks
>>>  >>>> Anu
>>>  >>>>
>>>  >>>> On 11/17/17, 12:55 AM, "Elek, Marton" <h...@anzix.net> wrote:
>>>  >>>>
>>>  >>>>Hi,
>>>  >>>>
>>>  >>>>Is there any plan for ratis webpage? I didn't find any Jira.
>>>  >>>>
>>>  >>>>My proposal is the following:
>>>  >>>>
>>>  >>>>1. I can create a draft site similar to my hadoop site
>>> proposal:
>>>  >>>>https://hadoop.anzix.net/
>>>  >>>>
>>>  >>>>2. I can collect the content from ratis presentations.
>>>  >>>>
>>>  >>>>3. I can copy the content to a google docs to make it easier
>>> to
>>>  >>>>fix/improve the content together.
>>>  >>>>
>>>  >>>>4. I will copy back the content to the html/markdown files
>>> and we
>>>  >> can
>>>  >>>>commit it to the git repo using a separated branch.
>>>  >>>>
>>>  >>>>I propose to do a simple page (what is ratis?) as a first
>>> step and
>>>  >>>> after
>>>  >>>>that we can extend with more detailed/version specific
>>> documentation
>>>  >>>>(such like a getting started guide...)
>>>  >>>>
>>>  >>>>Any thoughts?
>>>  >>>>
>>>  >>>>Thanks,
>>>  >>>>Marton
>>>  >>>>
>>>  >>>>
>>>  >>>>
>>>  >>>>
>>>  >>
>>>
>>>
>>

Re: Infra request for jira workflow + Yetus

[Tsz Wo Sze]

That's great.  Thanks!
Nicholas

On Thu, Oct 26, 2017 at 6:15 PM, Enis Söztutar  wrote:
> FYI, I created:  https://issues.apache.org/jira/browse/INFRA-15384
>
> Enis

[DISCUSS] 0.2-alpha release

[Tsz Wo Sze]

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

Re: [VOTE] Apache Ratis incubating Release 0.1.0-alpha rc0

[Tsz Wo Sze]

With four +1's and no -1, the VOTE is passed.

+1 from Jing, Jitendra, Jakob and me.

I will start another vote for the IPMC.

Thanks everyone!
Tsz-Wo

On Fri, May 5, 2017 at 3:19 PM, Tsz Wo Sze <szets...@gmail.com> wrote:
> Just a friendly reminder that the VOTE will be closed soon.  Please
> cast your vote if you haven't.  Thanks.
> Tsz-Wo
>
> On Tue, May 2, 2017 at 7:51 PM, Tsz Wo Sze <szets...@gmail.com> wrote:
>> Hi Apache Ratis PPMC,
>>
>> I am calling a vote for Apache Ratis incubating Release 0.1.0-alpha rc0.
>>
>> The git tag to be voted upon:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-ratis.git;a=shortlog;h=refs/tags/ratis-0.1.0-alpha
>>
>> The git commit hash:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-ratis.git;a=commit;h=52c4b6412df7daba82445db289f7b41e2216b4a6
>>
>> The source tarball can be found at:
>> https://dist.apache.org/repos/dist/dev/incubator/ratis/0.1.0-alpha/rc0/
>>
>> The fingerprint of key to sign release artifacts:
>> 2C33 A9CB 66AE AD59 3183  B01B 7843 4EF4 60D6 914B
>>
>> Release artifacts are signed with one of the keys available at:
>> https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS
>>
>> This vote will remain open for at least 72 hours.
>> Please vote on releasing this RC.
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>> Obviously, I am +1.
>>
>> Regards,
>> Tsz-Wo

Re: [VOTE] Apache Ratis incubating Release 0.1.0-alpha rc0

[Tsz Wo Sze]

Just a friendly reminder that the VOTE will be closed soon.  Please
cast your vote if you haven't.  Thanks.
Tsz-Wo

On Tue, May 2, 2017 at 7:51 PM, Tsz Wo Sze <szets...@gmail.com> wrote:
> Hi Apache Ratis PPMC,
>
> I am calling a vote for Apache Ratis incubating Release 0.1.0-alpha rc0.
>
> The git tag to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-ratis.git;a=shortlog;h=refs/tags/ratis-0.1.0-alpha
>
> The git commit hash:
> https://git-wip-us.apache.org/repos/asf?p=incubator-ratis.git;a=commit;h=52c4b6412df7daba82445db289f7b41e2216b4a6
>
> The source tarball can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/ratis/0.1.0-alpha/rc0/
>
> The fingerprint of key to sign release artifacts:
> 2C33 A9CB 66AE AD59 3183  B01B 7843 4EF4 60D6 914B
>
> Release artifacts are signed with one of the keys available at:
> https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS
>
> This vote will remain open for at least 72 hours.
> Please vote on releasing this RC.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Obviously, I am +1.
>
> Regards,
> Tsz-Wo

Re: [VOTE] Apache Ratis incubating Release 0.1.0-alpha rc0

[Tsz Wo Sze]

Jakob,

Thanks for the comments.  For the unit tests, Jing just have filed
RATIS-85 for fixing them.

For "mvn package", I just have tried it but it did not fail by RAT
without a header for dependency-reduced-pom.xml.  Are you sure that
the command is "mvn package"?  Anyway, you might have noticed that
dependency-reduced-pom.xml is a generated file so that it does not
need a license header.

Tsz-Wo



On Wed, May 3, 2017 at 12:26 PM, Jakob Homan <jgho...@gmail.com> wrote:
> +1 (binding)
>
> * Verified sigs on tar ball.
> * Disclaimer/License/Notice look good
> * Headers look good
>
> Concerns:
> * Unit tests hang/fail.  TestNotLeaderExceptionWithHadoopRpc fails
> immediately and then TestRaftReconfigurationWithHadoopRpc hangs for at
> least five minutes (canceled after that).  Any reason these shouldn't
> succeed?
> * mvn package fails:
> ratis-0.1.0-alpha/ratis-proto-shaded/dependency-reduced-pom.xml gets
> caught up by RAT without a header.
>
> These nits can be addressed in the next release.
>
> -Jakob
>
>
> On 3 May 2017 at 11:40, Jitendra Pandey <jiten...@hortonworks.com> wrote:
>> Downloaded the tar ball, verified the signatures.
>>
>> +1
>>
>> On 5/3/17, 11:29 AM, "Jing Zhao" <ji...@apache.org> wrote:
>>
>> +1. Thanks for driving this, Nicholas!
>>
>> On Tue, May 2, 2017 at 7:51 PM, Tsz Wo Sze <szets...@gmail.com> wrote:
>>
>> > Hi Apache Ratis PPMC,
>> >
>> > I am calling a vote for Apache Ratis incubating Release 0.1.0-alpha 
>> rc0.
>> >
>> > The git tag to be voted upon:
>> > https://git-wip-us.apache.org/repos/asf?p=incubator-ratis.
>> > git;a=shortlog;h=refs/tags/ratis-0.1.0-alpha
>> >
>> > The git commit hash:
>> > 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-ratis.git;a=commit;h=
>> > 52c4b6412df7daba82445db289f7b41e2216b4a6
>> >
>> > The source tarball can be found at:
>> > https://dist.apache.org/repos/dist/dev/incubator/ratis/0.1.0-alpha/rc0/
>> >
>> > The fingerprint of key to sign release artifacts:
>> > 2C33 A9CB 66AE AD59 3183  B01B 7843 4EF4 60D6 914B
>> >
>> > Release artifacts are signed with one of the keys available at:
>> > https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS
>> >
>> > This vote will remain open for at least 72 hours.
>> > Please vote on releasing this RC.
>> >
>> > [ ] +1 approve
>> > [ ] +0 no opinion
>> > [ ] -1 disapprove (and reason why)
>> >
>> > Obviously, I am +1.
>> >
>> > Regards,
>> > Tsz-Wo
>> >
>>
>>

[VOTE] Apache Ratis incubating Release 0.1.0-alpha rc0

[Tsz Wo Sze]

Hi Apache Ratis PPMC,

I am calling a vote for Apache Ratis incubating Release 0.1.0-alpha rc0.

The git tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=incubator-ratis.git;a=shortlog;h=refs/tags/ratis-0.1.0-alpha

The git commit hash:
https://git-wip-us.apache.org/repos/asf?p=incubator-ratis.git;a=commit;h=52c4b6412df7daba82445db289f7b41e2216b4a6

The source tarball can be found at:
https://dist.apache.org/repos/dist/dev/incubator/ratis/0.1.0-alpha/rc0/

The fingerprint of key to sign release artifacts:
2C33 A9CB 66AE AD59 3183  B01B 7843 4EF4 60D6 914B

Release artifacts are signed with one of the keys available at:
https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS

This vote will remain open for at least 72 hours.
Please vote on releasing this RC.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Obviously, I am +1.

Regards,
Tsz-Wo

Re: Maven Build

[Tsz Wo Sze]

Hi Karl,

No, we have not yet decided how to distribute the site.  The pom files
were initially copied from Hadoop/HBase.  Please free feel to suggest
any changes.

BTW, thanks a lot for your contributions on Ratis maven build!

Tsz-Wo

On Thu, Apr 13, 2017 at 7:15 PM, Karl Heinz Marbaise  wrote:
> Hi,
>
> I've got a question concerning the usage of wagon-ssh ..
>
> within the pom files it looks like you are using wagon provider to
> distribute the site via wagon-ssh ...
>
> have you already decided to distribute the site via wagon-ssh ?
>
> Kind regards
> Karl Heinz Marbaise

Re: Do shading as a last step?

[Tsz Wo Sze]

I am open to change the shading procedure but I like to understand the
motivation.  First of all, what is the problem we try to solve?  Is it
to avoid the imports from org.apache.ratis.shaded packages in our
source code?

#3 sounds like a good idea.  But why we need to kick out ratis-hadoop?
 I mean why it can't be post-shaded?

BTW, let's create a JIRA for discussion.  It usually is easier to follow.

Nicholas

On Sat, Apr 1, 2017 at 8:38 AM, Enis Söztutar  wrote:
> Hugo and I were discussing a case were the shading should happen at the
> last step, rather than what we do today.
>
> I think there are 3 possible strategies of shading that one can do:
>  (1) pre-shade some of your dependencies, so that your other dependencies
> can work. This what we do today, we shade PB+ GRPC, etc so that Hadoop can
> work.
>  (2) pre-shade some of your dependencies' transitive dependencies so that
> you depend on already-shaded artifacts. This will be like having maven
> artifacts of shaded-hadoop so that hadoop itself does not bring in any more
> dependency. If hadoop has shaded artifacts, or we do shading of hadoop's
> dependencies in another repository, we won't need to pre-shade PB, etc.
>  (3) post-shade. This means that in the code itself we do not depend on
> shaded packages anymore, but do the shading as a different module so that
> we publish shaded artifacts. This allows the downstreamers to be able to
> consume ratis, while allowing ratis source code to be saner.
>
> Obviously for doing (3), we need to kick out ratis-hadoop module to the
> hadoop project. Thinking about it, I think ratis-hadoop does not belong in
> Ratis itself anyway. What do you guys think about moving the code over to
> Hadoop, and getting rid of the hadoop dependency to end this shading
> madness?
>
> Enis

Re: [DISCUSS] 0.1-alpha release

[Tsz Wo Sze]

How about the versioning?  Should we start with 0.1-alpha or
0.1.0-alpha?  The latter seems better.

Tsz-Wo

On Wed, Mar 22, 2017 at 9:42 PM, Jitendra Pandey <jnpan...@gmail.com> wrote:
> +1
>
> On Wed, Mar 22, 2017 at 5:32 PM, Enis Söztutar <enis@gmail.com> wrote:
>
>> Sounds good. But we have to get the licenses and the rest of release
>> process in line (tarballs, etc). Should be doable.
>>
>> Enis
>>
>> On Wed, Mar 22, 2017 at 5:12 PM, Anu Engineer <aengin...@hortonworks.com>
>> wrote:
>>
>> > +1, good idea. Early use in SCM will give some real world usage via
>> CBlock
>> > and Ozone.
>> > --Anu
>> >
>> >
>> > On 3/22/17, 4:10 PM, "Tsz Wo Sze" <szets...@gmail.com> wrote:
>> >
>> > >Hi,
>> > >
>> > >I propose to release 0.1-alpha so that the downstream projects can
>> > >start integrating ratis.  One example is HDFS-11519.
>> > >
>> > >The release is in alpha quality with no guarantee on stability.  We
>> > >should add such warning in the README.  What do you think?
>> > >
>> > >Tsz-Wo
>> > >
>> >
>> >
>>

Re: incubator-ratis git commit: Update version to 0.11-SNAPSHOT.

[Tsz Wo Sze]

No problem.  I will start an email thread for our release plan.
Nicholas

On Tue, Mar 21, 2017 at 6:45 PM, Enis Söztutar <enis@gmail.com> wrote:
> Thanks.
>
> Enis
>
> On Tue, Mar 21, 2017 at 6:24 PM, Tsz Wo Sze <szets...@gmail.com> wrote:
>>
>> Sure, let's revert the commit for now.  We should discuss our release
>> plan and versioning.
>>
>> Nicholas
>>
>> On Tue, Mar 21, 2017 at 6:14 PM, Enis Söztutar <enis@gmail.com> wrote:
>> > You mean in the apache snapshots repo? Can't you delete the previous
>> > snapshot from there. Not sure why it will conflict since snapshot
>> > deployment is a standard for maven.
>> >
>> > We want the first release of ratis to be 0.1, not 0.11, so I will say we
>> > have to undo this.
>> >
>> > Enis
>> >
>> > On Tue, Mar 21, 2017 at 6:11 PM, Tsz Wo Sze <szets...@gmail.com> wrote:
>> >
>> >> I tried to deploy the current code (with shaded guava and netty) to
>> >> maven.  However, it conflicts with the existing 0.1-SNAPSHOT jar in
>> >> repo.  Therefore, I updated the rates version.
>> >>
>> >> Nicholas
>> >>
>> >> On Tue, Mar 21, 2017 at 5:57 PM, Enis Söztutar <enis@gmail.com>
>> >> wrote:
>> >> > Nicolas, why are we doing this?
>> >> >
>> >> > Enis
>> >> >
>> >> > On Tue, Mar 21, 2017 at 5:56 PM, <szets...@apache.org> wrote:
>> >> >
>> >> >> Repository: incubator-ratis
>> >> >> Updated Branches:
>> >> >>   refs/heads/master 183c64d51 -> ebe62d254
>> >> >>
>> >> >>
>> >> >> Update version to 0.11-SNAPSHOT.
>> >> >>
>> >> >>
>> >> >> Project: http://git-wip-us.apache.org/repos/asf/incubator-ratis/repo
>> >> >> Commit: http://git-wip-us.apache.org/repos/asf/incubator-ratis/
>> >> >> commit/ebe62d25
>> >> >> Tree: http://git-wip-us.apache.org/repos/asf/incubator-ratis/
>> >> tree/ebe62d25
>> >> >> Diff: http://git-wip-us.apache.org/repos/asf/incubator-ratis/
>> >> diff/ebe62d25
>> >> >>
>> >> >> Branch: refs/heads/master
>> >> >> Commit: ebe62d25411ac62e74b49b14e4ad6535f29eb70b
>> >> >> Parents: 183c64d
>> >> >> Author: Tsz-Wo Nicholas Sze <szets...@hortonworks.com>
>> >> >> Authored: Tue Mar 21 17:56:19 2017 -0700
>> >> >> Committer: Tsz-Wo Nicholas Sze <szets...@hortonworks.com>
>> >> >> Committed: Tue Mar 21 17:56:19 2017 -0700
>> >> >>
>> >> >>
>> >> >> --
>> >> >>  pom.xml | 2 +-
>> >> >>  ratis-assembly/pom.xml  | 4 ++--
>> >> >>  ratis-client/pom.xml| 4 ++--
>> >> >>  ratis-common/pom.xml| 4 ++--
>> >> >>  ratis-examples/pom.xml  | 4 ++--
>> >> >>  ratis-grpc/pom.xml  | 4 ++--
>> >> >>  ratis-hadoop-shaded/pom.xml | 4 ++--
>> >> >>  ratis-hadoop/pom.xml| 4 ++--
>> >> >>  ratis-netty/pom.xml | 4 ++--
>> >> >>  ratis-proto-shaded/pom.xml  | 4 ++--
>> >> >>  ratis-server/pom.xml| 4 ++--
>> >> >>  11 files changed, 21 insertions(+), 21 deletions(-)
>> >> >>
>> >> >> --
>> >> >>
>> >> >>
>> >> >> http://git-wip-us.apache.org/repos/asf/incubator-ratis/
>> >> >> blob/ebe62d25/pom.xml
>> >> >>
>> >> >> --
>> >> >> diff --git a/pom.xml b/pom.xml
>> >> >> index 7e0869f..6258acf 100644
>> >> >> --- a/pom.xml
>> >> >> +++ b/pom.xml
>> >> >> @@ -27,7 +27,7 @@
>> >> >>
>> >> >>ratis
>> >> >>org.apache.ratis
>> >> >> -  0.1-SNAPSHOT
>> >> >> +  0.11-SNAPSHOT
>> >> >>Ratis
>> >> >>pom
>> >> >>
>> >> >>
>> >> >> http://git-wip-

Re: incubator-ratis git commit: Update version to 0.11-SNAPSHOT.

[Tsz Wo Sze]

Sure, let's revert the commit for now.  We should discuss our release
plan and versioning.

Nicholas

On Tue, Mar 21, 2017 at 6:14 PM, Enis Söztutar <enis@gmail.com> wrote:
> You mean in the apache snapshots repo? Can't you delete the previous
> snapshot from there. Not sure why it will conflict since snapshot
> deployment is a standard for maven.
>
> We want the first release of ratis to be 0.1, not 0.11, so I will say we
> have to undo this.
>
> Enis
>
> On Tue, Mar 21, 2017 at 6:11 PM, Tsz Wo Sze <szets...@gmail.com> wrote:
>
>> I tried to deploy the current code (with shaded guava and netty) to
>> maven.  However, it conflicts with the existing 0.1-SNAPSHOT jar in
>> repo.  Therefore, I updated the rates version.
>>
>> Nicholas
>>
>> On Tue, Mar 21, 2017 at 5:57 PM, Enis Söztutar <enis@gmail.com> wrote:
>> > Nicolas, why are we doing this?
>> >
>> > Enis
>> >
>> > On Tue, Mar 21, 2017 at 5:56 PM, <szets...@apache.org> wrote:
>> >
>> >> Repository: incubator-ratis
>> >> Updated Branches:
>> >>   refs/heads/master 183c64d51 -> ebe62d254
>> >>
>> >>
>> >> Update version to 0.11-SNAPSHOT.
>> >>
>> >>
>> >> Project: http://git-wip-us.apache.org/repos/asf/incubator-ratis/repo
>> >> Commit: http://git-wip-us.apache.org/repos/asf/incubator-ratis/
>> >> commit/ebe62d25
>> >> Tree: http://git-wip-us.apache.org/repos/asf/incubator-ratis/
>> tree/ebe62d25
>> >> Diff: http://git-wip-us.apache.org/repos/asf/incubator-ratis/
>> diff/ebe62d25
>> >>
>> >> Branch: refs/heads/master
>> >> Commit: ebe62d25411ac62e74b49b14e4ad6535f29eb70b
>> >> Parents: 183c64d
>> >> Author: Tsz-Wo Nicholas Sze <szets...@hortonworks.com>
>> >> Authored: Tue Mar 21 17:56:19 2017 -0700
>> >> Committer: Tsz-Wo Nicholas Sze <szets...@hortonworks.com>
>> >> Committed: Tue Mar 21 17:56:19 2017 -0700
>> >>
>> >> --
>> >>  pom.xml | 2 +-
>> >>  ratis-assembly/pom.xml  | 4 ++--
>> >>  ratis-client/pom.xml| 4 ++--
>> >>  ratis-common/pom.xml| 4 ++--
>> >>  ratis-examples/pom.xml  | 4 ++--
>> >>  ratis-grpc/pom.xml  | 4 ++--
>> >>  ratis-hadoop-shaded/pom.xml | 4 ++--
>> >>  ratis-hadoop/pom.xml| 4 ++--
>> >>  ratis-netty/pom.xml | 4 ++--
>> >>  ratis-proto-shaded/pom.xml  | 4 ++--
>> >>  ratis-server/pom.xml| 4 ++--
>> >>  11 files changed, 21 insertions(+), 21 deletions(-)
>> >> --
>> >>
>> >>
>> >> http://git-wip-us.apache.org/repos/asf/incubator-ratis/
>> >> blob/ebe62d25/pom.xml
>> >> --
>> >> diff --git a/pom.xml b/pom.xml
>> >> index 7e0869f..6258acf 100644
>> >> --- a/pom.xml
>> >> +++ b/pom.xml
>> >> @@ -27,7 +27,7 @@
>> >>
>> >>ratis
>> >>org.apache.ratis
>> >> -  0.1-SNAPSHOT
>> >> +  0.11-SNAPSHOT
>> >>Ratis
>> >>pom
>> >>
>> >>
>> >> http://git-wip-us.apache.org/repos/asf/incubator-ratis/
>> >> blob/ebe62d25/ratis-assembly/pom.xml
>> >> --
>> >> diff --git a/ratis-assembly/pom.xml b/ratis-assembly/pom.xml
>> >> index 638b091..7b0b71d 100644
>> >> --- a/ratis-assembly/pom.xml
>> >> +++ b/ratis-assembly/pom.xml
>> >> @@ -19,14 +19,14 @@
>> >>
>> >>  ratis
>> >>  org.apache.ratis
>> >> -0.1-SNAPSHOT
>> >> +0.11-SNAPSHOT
>> >>  ..
>> >>
>> >>
>> >>ratis-assembly
>> >>org.apache.ratis
>> >>Ratis Project Assembly
>> >> -  0.1-SNAPSHOT
>> >> +  0.11-SNAPSHOT
>> >>
>> >>pom
>> >>
>> >>
>> >> http://git-wip-us.apache.org/repos/asf/incubator-ratis/
>> >> blob/ebe62d25/ratis-client/pom.xml
>> >> --
>