Re: Please invite me to the slack
Apache has made a change where we can invite other people without apache email IDs into slack. Here is a link for joining the Ratis Slack group. Please try this out and see if this works for you. As Arpit said, we mostly use @apache ID so your mileage may vary. https://slack.com/share/IRFQWNZMK/qhFgm54CX454UhWHi84qqiIa/enQtODY1ODQ2NzgxNzMzLTVlNjM3NDdiMGNmNzg4OTFiZDc0N2Y2MGYzOWIxNmE4ODczNDg2YzM3ZjJkODEyOGU1YmQ0MzNhYmIyYzMzNmY Thanks Anu On Mon, Dec 9, 2019 at 9:20 AM Arpit Agarwal wrote: > Resending with your email ID included. > > > On Dec 9, 2019, at 9:19 AM, Arpit Agarwal wrote: > > > > Hello, if you don’t have an @apache.org email address you may need to > file an INFRA ticket to get an invite. I am not able to add you with your @ > qq.com email ID. > > > >> On Dec 9, 2019, at 2:40 AM, mrly <1210746...@qq.com> wrote: > >> > >> Please invite me to the discussion of ratis on slack.com > > > >
Re: [DISCUSS] 0.5.0 release
+1, for the release. Thanks for driving this. -- Anu On Tue, Oct 29, 2019 at 12:22 PM Tsz Wo Sze wrote: > 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 > > > > >> > > > > > > > >
Meeting notes from the Ozone/Ratis Community meeting
During ApacheCon, Las Vegas, I was encouraged to share these meeting notes in the apache mailing lists. So please forgive me for the weekly spam. I had presumed that people know of this weekly sync-ups and hence not been posting notes to the mailing list. Please take a look at older meeting notes in the wiki if you are interested. https://cwiki.apache.org/confluence/display/HADOOP/2019-09-23+Meeting+notes Thanks Anu
Re: [VOTE] Apache Ratis incubating Release 0.4.0 rc0
+1. 1. Verified Signatures on Bin and Src Tarballs. 2. Verified DISCLAIMER, LICENSE, and NOTICE in src. 3. Ran the examples using examples/bin (nit the help on start-all can be improved a bit) 4. Verified that the new Release Manager Keys are visible and verifiable at https://www.apache.org/dist/incubator/ratis/KEYS Thanks Anu On Tue, Jul 23, 2019 at 10:52 AM Mukul Kumar Singh wrote: > Hi Apache Ratis PPMC, > > I am calling a vote for Apache Ratis incubating Release 0.4.0 rc0. > This is with respect to the discuss mail thread > < > 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-rc0 > > The git commit hash: > > https://gitbox.apache.org/repos/asf?p=incubator-ratis.git;a=commit;h=d4f5c9ded9ea4dc1a8acbec9a5e24f5e2f3bc6b6 > > The source and binary tarballs can be found > at:http://people.apache.org/~msingh/0.4.0-rc0/ > > The fingerprint of key to sign release artifacts: > 45B0 13F6 29C6 89CC 6EE3 77B0 8D43 C3D9 A8F1 02BD > > 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) > > Starting with my +1. > > Regards, > Mukul Kumar Singh >
Re: [DISCUSS] Apache Ratis 0.4.0 release
Hi Ankit, Would love to take that in; however, we also would love to do an Ozone release too. For the Ozone release, we cannot depend on the snap-shot releases of Ratis; that is the primary motivator for this Ratis release. We have been fixing issues in the Ratis path and testing with Ozone; and at this point of time we have all known issues fixed. I see that these patches have been out for 20 days; do you have time line for getting these committed? if these can be committed in next few days or if it is Major bug, yes we can take them. Otherwise; I would really love to go on with the Ozone release. How about we send out the Ratis RC candidate by end of this week? and if these 2 JIRAs are in, we will take them. Does that sound like a plan? Thanks Anu On Mon, Jul 1, 2019 at 11:40 AM Ankit Singhal wrote: > can we wait for these two pull request to be merged(they are almost near to > review completion):- > https://github.com/apache/incubator-ratis/pull/25 > https://github.com/apache/incubator-ratis/pull/26 > > > > On Mon, Jul 1, 2019 at 10:27 AM anu engineer > wrote: > > > +1, Thanks for the quick response. > > > > --Anu > > > > > > On Mon, Jul 1, 2019 at 10:17 AM Arpit Agarwal > > > > wrote: > > > > > +1 for starting the 0.4.0 release. We’ve had numerous useful bug-fixes > > and > > > improvements since the last release. > > > > > > Has anyone volunteered to be the RM? > > > > > > > > > > On Jul 1, 2019, at 10:15 AM, Mukul Kumar Singh < > > mksingh.apa...@gmail.com> > > > wrote: > > > > > > > > Hi, > > > > > > > > It has been a while since our last Ratis release. > > > > We have around 50 commits after our latest 0.3.0 release. > > > > > > > > How about we start the process for a new Ratis release (0.4.0). > > > > We can create a new 0.4.0 branch and change trunk to 0.5.0. > > > > > > > > Thanks, > > > > Mukul > > > > > > > > >
Re: [DISCUSS] Apache Ratis 0.4.0 release
+1, Thanks for the quick response. --Anu On Mon, Jul 1, 2019 at 10:17 AM Arpit Agarwal wrote: > +1 for starting the 0.4.0 release. We’ve had numerous useful bug-fixes and > improvements since the last release. > > Has anyone volunteered to be the RM? > > > > On Jul 1, 2019, at 10:15 AM, Mukul Kumar Singh > wrote: > > > > Hi, > > > > It has been a while since our last Ratis release. > > We have around 50 commits after our latest 0.3.0 release. > > > > How about we start the process for a new Ratis release (0.4.0). > > We can create a new 0.4.0 branch and change trunk to 0.5.0. > > > > Thanks, > > Mukul > >
Re: Season of Docs 2019 (?), mentor is needed
I will gladly participate, Let us add ozone too to that list. Improving documentation is really important --Anu On Thu, Apr 18, 2019 at 7:31 AM Elek, Marton wrote: > > "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: > > https://cwiki.apache.org/confluence/display/COMDEV/Season+of+Docs+2019 > > (or the comdev list). > > 1. I propose to participate in the program with Ratis to create the > initial set of the documentation. > > Please let me know what do you think. > > 2. If you agree, I need somebody as a second mentor, as two mentors are > required by the program. > > Thanks a lot, > Marton > >
Re: [VOTE] Apache Ratis incubating Release 0.3.0 rc2
+1. 1. Verified the Signature. 2. Verified the Checksums. 3. Build from Sources. --Anu On Wed, Apr 10, 2019 at 10:04 AM Jitendra Pandey wrote: > +1 > > Verified checksums > Built from source > Ran filestore loadgen. > > On 4/9/19, 12: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&a=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 > > > >
Re: [VOTE] Apache Ratis incubating Release 0.3.0 rc1
+1, Thanks for the RC1. -- Verified Checksums for Bin and Src. -- Build the artifacts from the src tarball. --Anu On Wed, Apr 3, 2019 at 11:16 PM Tsz Wo Sze wrote: > 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&a=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
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&a=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 Thirdparty 0.1.0rc0
Would it be possible to do a full Ratis snap-shot release? So, we can just consume all the changes with a single update on ozone side. Sorry, I am just being a little selfish here, but it makes ozone’s life little easier. Otherwise we will have to follow up with another release. --Anu On 10/11/18, 11:44 AM, "Josh Elser" wrote: Hey Anu, No need for me to wait around. This is just for the new thirdparty repo -- not a release of ratis itself :) On 10/11/18 2:31 PM, Anu Engineer wrote: > Hi Josh, > > Can you please include Ratis-348?, it fixes a critical issue for Ozone. You might have to wait until the end of day to roll the build. > > Thanks > Anu > > > On 10/11/18, 11:26 AM, "Josh Elser" wrote: > > The only thing that the ASF releases is source code, therefore the > policy you're quoting isn't relevant. There is no requirement to vote on > binary artifacts that are created from that source release. The > obligation on us is to verify that anything else the source release > creates follows ASF licensing like the source release does (e.g. our > JARs contain appropriate L&N files). > > You are right about incubating in the filename though -- totally forgot > about that requirement. Let me roll an rc1 with that. > > Thanks for catching that! > > On 10/11/18 11:23 AM, Tsz Wo Sze wrote: > >> 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
Hi Josh, Can you please include Ratis-348?, it fixes a critical issue for Ozone. You might have to wait until the end of day to roll the build. Thanks Anu On 10/11/18, 11:26 AM, "Josh Elser" wrote: The only thing that the ASF releases is source code, therefore the policy you're quoting isn't relevant. There is no requirement to vote on binary artifacts that are created from that source release. The obligation on us is to verify that anything else the source release creates follows ASF licensing like the source release does (e.g. our JARs contain appropriate L&N files). You are right about incubating in the filename though -- totally forgot about that requirement. Let me roll an rc1 with that. Thanks for catching that! On 10/11/18 11:23 AM, Tsz Wo Sze wrote: >> 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: Replicated-List example
For Ozone, it is very useful to get Replicated-Map completed and hosted as first-class object inside RATIS. That would allow Ozone/HDDS to take dependency on Replicated Map. Right now, it seems to be an internal Ratis only object. Thanks Anu On 8/6/18, 3:15 PM, "Josh Elser" wrote: In the spirit of the Replicated-Map (RATIS-51), I tried my hand at making a simple StateMachine that could give some basic List-like functionality. Client/test: https://github.com/joshelser/incubator-ratis/blob/rlist/ratis-replicated-list/src/test/java/org/apache/ratis/rlist/RListTest.java StateMachine: https://github.com/joshelser/incubator-ratis/blob/rlist/ratis-replicated-list/src/main/java/org/apache/ratis/rlist/RListStateMachine.java Is something like this useful for new developers in the core codebase? I was pretty much copy-pasting stuff from other examples (arithmetic, filestore, rmap), so I am worried that I might contribute to "death by example" :) Let me know what you think of it and if you see any problems with it. My unit test passes, but that's the only amount of testing I've done with it! I tried to leave comments for myself (and others), but there's some more I want to start digging into now to better understand it all. - Josh
Re: Versions after 0.2.0
>1.) I didn't create 0.2 branch, yet. If anybody see the demand to create >some lightweight bugfix release 0.2.1, please say so. +1, let us shoot for 0.3.0-alpha release; we can always open a 0.2.0 branch later if needed. >2.) Can somebody with Jira admin privilege please create version 0.3.0 >in Jira? Done, I have marked 0.2.0 as released, and opened a new release 0.3.0-alpha. Thanks for the releasing Ratis 0.2.0-alpha. Thanks Anu On 7/15/18, 12:09 AM, "Elek, Marton" wrote: Hi, Ratis 0.2.0 is released, the ratis-0.2.0-rc2 tag is tagged with ratis-0.2.0. I changed the pom version to 0.3.0-SNAPSHOT (on top of the ratis-0.2.0 commit) and merged back the changes to the master. With this approach the 0.2.0 tag is a parent of any new commit and 'git describe' works well. 1.) I didn't create 0.2 branch, yet. If anybody see the demand to create some lightweight bugfix release 0.2.1, please say so. I prefer to create more frequent releases instead. (Unless Ozone requires a bugfix release ASAP). 2.) Can somebody with Jira admin privilege please create version 0.3.0 in Jira? Thanks a lot, Marton
Re: [DISCUSS] Distributed Log "LogService" proposal
+1, This would be extremely useful for Ozone too. Thanks Anu On 7/13/18, 1:26 PM, "Lokesh Jain" wrote: +1 Thanks Lokesh > On 14-Jul-2018, at 1:55 AM, Jitendra Pandey wrote: > > +1 > > On 7/13/18, 1:22 PM, "Josh Elser" wrote: > >Hi all, > >I'd like to share a document that I've been working on for many months >with Jitendra about building a distributed-log "recipe" on top of Ratis. > > https://docs.google.com/document/d/1Su5py_T5Ytfh9RoTTX2s20KbSJwBHVxbO7ge5ORqbCk/edit?usp=sharing > >The primary use case is for Apache HBase, replacing its HDFS-backed >write-ahead log construct with something a bit more flexible. Our hope >is that by building a distributed log with Ratis, HBase could observe >similar levels of performance as we do with HDFS and better enable our >flexibility to run on "dynamic" cloud IaaS platforms. > >At the bottom of that document, you'll find a high level breakdown of >work items for both Ratis as well as HBase. My hope is that both of >these will be able to be worked on concurrently. Furthermore, while >HBase is a primary "customer" for the work, I hope that you would find a >DistributedLog recipe for Ratis (what we've been calling the >"LogService") generally reusable for the Ratis community. > >Please let me know what you think (either on the mailing list or via >comments on the google-doc). Thanks! > >- Josh > > >
Re: [DISCUSS] version of next release (was Re: [VOTE] Release of Apache Ratis (incubating) 0.2.0 (rc0))
+1, on 0.2.0. The major consumer of Ratis (HDDS/Ozone) will take it with or without –alpha ( --Anu On 5/14/18, 2:24 PM, "Elek, Marton" wrote: All the issues are fixed now (Thanks Nanda, Tsz-Wo, Mukul) The only open question is the version of the release (alpha vs non-alpha). I think there are two kind of alpha releases: 1. Alpha as defined in the semantic versioning specification (https://semver.org/). Here the alpha is a pre-release version of the final release (0.2.0-alpha should be followed by an 0.2.0). This is the schema what is used by hadoop before hadoop 3.0 release. 2. The other alpha is just a label on every release to mark the current releases as not "production-ready". As I understood ratis had this kind of alpha label (there was a 0.1.0-alpha but not 0.1.0). I prefer to follow the semantic versioning. And I can't see the benefit to release both 0.2.0 and 0.2.0-alpha. I think the current version is stable enough to get a final number and the 0 as the major version makes it clear that the project is in an early phase. So I would use 0.2.0 as the next verison number (but not strongly against 0.2.0-alpha if this your preference). What do you think? Thanks, Marton On 05/08/2018 11:45 PM, Tsz Wo Sze wrote: > 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 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 >>> 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] |
Re: [VOTE] Release of Apache Ratis (incubating) 0.2.0 (rc0)
+1 on cancelling the vote and flowing thru with new vote one these issues are
fixed.
From ozone perspective, we can take the Ratis bits and run a full cluster level
test and provide feedback on the next RC.
Thanks
Anu
On 5/8/18, 2:16 PM, "Elek, Marton" 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
> 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 {
>>p
Re: [VOTE#2] Merge RATIS-5 to a new branch and publish the new site
+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: [VOTE] Merge RATIS-5 to a new branch and publish the new site
Based on the feedback from the incubator thread, let us cancel this vote. We will fix all the issues and restart a vote by end of the week. --Anu On 12/30/17, 2:42 PM, "Elek, Marton" wrote: Thank you very much the feedback until now. I extend the deadline of the vote with one week (5th of January) * According to the current activity on the apache mailing lists, most of the people are still on holiday. I would like to be sure that everybody had the opportunity to check/vote. * I will call for review on incubator-general as well (thx the idea Tsz-Wo). Thanks again, Marton On 12/28/2017 08:31 AM, Tsz Wo Sze wrote: > +1 the web site looks good. > > Question: should we ask someone in Incubation to review the website > since Incubation has a guideline for website. > - http://incubator.apache.org/guides/sites.html > > Tsz-Wo > > > On Thu, Dec 28, 2017 at 2:08 PM, Mukul Kumar Singh > wrote: >> The rendered website looks great. +1 from me as well. >> >> >> On 23/12/17, 1:34 AM, "Jitendra Pandey" wrote: >> >> +1, Great work. Let’s merge the awesome website. >> >> On 12/22/17, 7:06 AM, "Elek, Marton" 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] >> >> This is the initial version which is created according to the Apache >> policies [2]. It uses hugo (a single binary site generator) and uses >> bootstrap based styles and contains a minimal set of content to start. >> >> This is a formal vote request to merge RATIS-5 patch (squashed version >> of RATIS-5 branch) to a new branch (asf-site-source) and commit the >> rendered version to another branch (asf-site). (I will ask apache infra >> to use asf-site branch as the source of the website and create jenkins >> job to regenerate site in case of source change). >> >> Please check the site and vote. Rendered version is also attached to >> ratis-rendered.tar.gz and can be checked at >> https://elek.github.io/ratis-site/ together with the source) but please >> also check the rendering process if you can (just call hugo from the >> ratis-site directory and check the results in the public folder) >> >> Unfortunatelly this vote is opened just a few days before christmas so >> it will close no earlier than one week from today (29/12), to be sure >> everybody had the opportunity to check it and vote. >> >> Thanks, >> Marton >> >> [1] >> https://issues.apache.org/jira/secure/attachment/12902272/RATIS-5.003.patch >> >> [2] >> https://issues.apache.org/jira/browse/RATIS-5?focusedCommentId=16275030&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16275030 >> >> >> >> >> >>
Re: ratis website proposal
Thank you for the feedback. We will add the source release as well as the direct link to the binary only download. Our mentors are involved and this site is at the voting stage in the Ratis Dev List. We wanted to get wider feedback before committing this. Thanks Anu On 1/2/18, 10:03 AM, "Dave Fisher" wrote: Hi - At Apache we provide source code as releases as our primary purpose. The Ratis project must provide a download to your source release using the download.cgi method approved by Infrastructure. [1] You should also provide a download of the binary archives that is not dependent on Maven. Not every potential developer will be using Maven also they may not have direct access to Maven Central. Are your mentors engaged in providing advice? Regards, Dave [1] http://www.apache.org/dev/release-download-pages.html > On Jan 2, 2018, at 9:35 AM, Elek, Marton wrote: > > > 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 violations of the Apache/incubator policies. > > * or if you have any kind of suggestions/comments. > > > The proposed site is available from here: > > https://elek.github.io/ratis-site/ > > > Or you can check the source and generate it yourself: > > https://issues.apache.org/jira/browse/RATIS-5 > > Thanks a lot, > Marton > > ps: Please note that this is an initial version. Additional, more-detailed documentation will be added soon. > > [1]: https://mail-archives.apache.org/mod_mbox/incubator-ratis-dev/201712.mbox/%3C493056ac-5cff-a4b6-4b30-2ba3065b9e18%40anzix.net%3E > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
Re: ratis website proposal
Thanks for the comments, we will address this feedback --Anu On 1/2/18, 9:59 AM, "sebb" wrote: On 2 January 2018 at 17:35, Elek, Marton wrote: > > 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 violations of the Apache/incubator policies. > > * or if you have any kind of suggestions/comments. > > > The proposed site is available from here: > > https://elek.github.io/ratis-site/ [The final site must be published from http://ratis.incubator.apache.org/] Some initial feedback on the content: The download section does not have a link to the source, KEYS, sigs, hashes. The first/main mention of other Apache projects such as Hadoop must use the form "Apache Hadoop". The words "java" and "slack" are normally capitalised. The incubation disclaimer is missing. The acronym RAFT means nothing to me; it would help if the main/first usage was something like "RAFT (Real Actual Factual Truth)" - or whatever it means. Also it might help to describe the sort of applications for which Ratis is intended. > > Or you can check the source and generate it yourself: > > https://issues.apache.org/jira/browse/RATIS-5 > > Thanks a lot, > Marton > > ps: Please note that this is an initial version. Additional, more-detailed > documentation will be added soon. > > [1]: > https://mail-archives.apache.org/mod_mbox/incubator-ratis-dev/201712.mbox/%3C493056ac-5cff-a4b6-4b30-2ba3065b9e18%40anzix.net%3E > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Subscription request
Please send a mail to 1. dev-subscr...@ratis.incubator.apache.org for dev list 2. user-subscr...@ratis.incubator.apache.org for user list. Thanks Anu On 12/19/17, 11:41 PM, "Nandakumar Vadivelu" wrote:
Re: ratis web page
Perfect will do that. I will post a merge vote thread soon. Need to cross-check the payload before the merge is posted. --Anu On Mon, Dec 18, 2017 at 9:24 AM, Jitendra Pandey wrote: > Lets start a merge vote that will run for 3 days, so that this gets > committed later this week. > > On Mon, Dec 18, 2017 at 4:21 AM, Tsz Wo Sze wrote: > > > 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 > > 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 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" > > 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" > 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: ratis web page
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 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" 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 >> 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 >> 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 >> 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" 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: ratis web page
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" 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 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 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 wrote: >>> +1. Thanks Marton! >>> >>> On Fri, Nov 17, 2017 at 9:43 AM, Anu Engineer >> >>> wrote: >>> >>>> +1, great idea. I would like to work with you on this. >>>> >>>> Thanks >>>> Anu >>>> >>>> On 11/17/17, 12:55 AM, "Elek, Marton" 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: ratis web page
+1, great idea. I would like to work with you on this. Thanks Anu On 11/17/17, 12:55 AM, "Elek, Marton" 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: [DISCUSS] 0.2-alpha release
+1, Ozone would love to get the latest Ratis bits. Thanks Anu On 10/10/17, 8:15 PM, "Tsz Wo Sze" 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: [DISCUSS] 0.1-alpha release
+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" 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 >
