+1
Checked:
1. sha512 --> ok
2. signature --> ok
3. can be built from source --> ok
4. DISCLAIMER --> ok
5. LICENCE/NOTICE --> ok
Marton
How about the next release of Ratis be a GA release?
What does it mean exactly to be a GA? I checked the previous
announcements and didn't find any notice that it's beta/alpha right now,
or not suggested for production. It already seems to be GA ;-)
If we would like to communicate that
+1
1. Checked the signature
2. Checked sha512
3. Can be compiled from the source
4. Compared with the tag/commit: it's the same.
5. DISCLAIMER is included
6. Name contains the incubating
Marton
> The version in pom.xml of source tarball have SNAPSHOT in their name.
Yes, the source package seems to be created based on the previous
commit, not the one which was mentioned in the vote thread (and
referenced by tag and commit hash)
I think we need a new vote.
By the way: for the vote
I rebased my previous patch RATIS-697 which enables github based PR
checks and branch builds very similar to Ozone. Currently the test is
running but it's very close to a ready state.
Hopefully it will help to use github pull requests safely.
An example run is here:
(As Mukul is out during the next few days / weeks I'm going to help him
to finish this release.)
The 72 hours are passed and we got 4 + 1 binding + non-binding votes
without any -1/0
The vote is PASSED. I will start the IPMC vote, soon.
Thank you for all the votes and the verification.
+1
- built from the source
- checked the signature
- checked the source package (no binary, DISCLAIMER, NOTICE, LICENSE)
Notice has an older copyright (2018) but it's not a blocker IMHO.
Marton
On 11/4/19 12:53 AM, Ankit Singhal wrote:
+1
-- Rat check -Ok
-- Verified signature and
Hi,
As Anu mentioned in the Ozone meeting minutes we discussed about a
possible more frequent release cadence (for Ozone and Ratis).
At the last ApacheCon NA I learned that Apache Beam follows a time based
relase cadence, they cut the branch after a specified amount of time.
Which means
We can change this strange behaviour.
It turned out that it's possible to use just one branch which contains
both the source and rendered version (see the hadoop site) Would you
prefer this approach?
It would be even better to generate the side during the deploy time.
AFAIK the apache infra
"Season of Docs is a new Google program focussed on helping to improve
the quality of documentation in open source software."
In short: Google pay for technical writers to improve/create
documentation of Open source projects.
See the wiki page for more information:
+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
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.
>
>
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
t;
> 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.
>>>
+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
+1 (non-binding)
Checked:
* Signature: OK
* Checksum: OK
* DISCLAIMER/LICENSE/NOTICE: OK
* can build from the source: OK
I also patched the Hadoop/Ozone trunk to use 0.2.0 from the staged
repository, created a full build and executed the full smoketest suite.
All passed.
Looks good to me,
+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
Hi,
Is there any plan to restart this vote? Or is there any blocker?
Thanks,
Marton
On 10/12/18 9:02 PM, Josh Elser wrote:
> This vote failed. Will be rolling an rc1.
>
> On 10/8/18 7:29 PM, Josh Elser wrote:
>> Hi,
>>
>> Please vote on the following release candidate to become Apache
Thanks to all who verified and voted!
The vote is passed with 6 [+1] and without [-1] or [0] votes.
I will create the 2nd level vote for the IPMC members today.
Thanks again the testing: Jitendra, Tsz-Wo, Hanisha, Lokesh, Karl
Marton
ps: I created RATIS-262 for the compilation warnings.
As you know the Incubator level vote of the release is failed due to a
licensing issue.
The issue is fixed and the license problem is solved, it's in Patch
Available state:
https://issues.apache.org/jira/browse/RATIS-249
After it's merged we can start a new vote thread.
Marton
ps: I
Thanks to all who verified and voted!
The vote is passed with 6 [+1] and without [-1] or [0] votes.
I added the missing apache prefix to the artifact names. As it could be
done without modifying the packages or signatures I don't think that we
need any more rc.
I will create the new vote
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
se 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 t
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
he.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 <e...@apache.org> wrote:
Hi all,
I'd like to
/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 <e...@apache.org> wrote:
Hi all,
I'd like to call a
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 enou
Hi,
I would like to restart the discussion about a ratis release.
1. It's hard to find the right time to release as thanks to the
continuous testing with hdfs/ozone we always have some minor
issues/improvements.
I would suggest to do a release as soon as possible and do more frequent
Thank you very much your votes.
The Vote is passed with:
* 7 of +1 vote (thx Anu, Jitendra, Mukul, Tsz-Wo, Lokesh, Shashikant,
Arpit)
* and without -1 vote.
I will merge the source code and the rendered version to the proposed
branches and open the infra ticket to publish the site.
Hi,
We created an initial version of the Ratis website. And currently there
is a vote[1] thread on the ratis dev mailing list to publish it.
This is not a release, but we would like to get as many feedback as
possible, so we kindly ask you to check it and let us now:
* if you see any
reat work. Let’s merge the awesome website.
On 12/22/17, 7:06 AM, "Elek, Marton" <h...@anzix.net> wrote:
Hi,
RATIS-5 feature branch contains the proposed site for
ratis.incubator.apache.org.
The final patch is uploaded to the RATIS-5 issue [1]
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 wou
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
33 matches
Mail list logo
