+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?
> >
> >
+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,
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
+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
> > 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,
> > > &g
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
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
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
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
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
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
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
e.
> > 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:
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:
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 re
elease-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:
&g
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:
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
> wro
.@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 (m
uggest 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 b
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, "gi
gt;
> > 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.
&
re, 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,
t; > 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 8
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/view/Ratis/
> > >
> > > m.
> > >
> > > On 1/8/19 12:38 AM, Josh Elser wrote:
> > >> Pending: https://issues.apache.org/jira/browse/INFRA-17580
> > >>
> > >> HTH, folks.
> > >>
> > >&g
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
> ... 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 ma
1/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 cad
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
+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
ess 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 inst
+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
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
>
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.i
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
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
+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
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
tps://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. Plea
ntext$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"
> pub
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,
> 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.
ed 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
>
>
+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"
t;
> 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
/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. Yo
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
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
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
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
>> 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, T
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:
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
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
> > +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,
>>
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:
>>
>> Sur
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
59 matches
Mail list logo