Re: Require projects to have solid API docs
The Apache Kafka javadoc and scala doc are published with source and binaries https://archive.apache.org/dist/kafka/0.8.2.2/ and they can be generated from source. There is no javadoc for both producer and consumer (yet but you can generate from trunk for 0.9) because the new java consumer has been in development with testing underway now. If you want to consume from Kafka (as stable) using the project client you have to use the Scala consumer. There is a lot of documentation especially around the API http://kafka.apache.org/documentation.html#api with lots of good links if any issues github PR are accepted now. For more kafka questions feel free to reach out to the community http://kafka.apache.org/contact.html. Thanks! ~ Joe Stein ~ Joe Stein On Sun, Oct 11, 2015 at 11:59 AM, Andrew Pennebaker < andrew.penneba...@gmail.com> wrote: > In the future, could Apache Incubator require projects to maintain better > API documentation before graduation? In particular, Kafka has rather sparse > documentation in v0.8. The Javadocs appear to be randomly hosted on this or > that professor webpage, and no Kafka javadoc has documentation for > *both* Consumers > and Producers. > > -- > Cheers, > Andrew >
Re: [VOTE] Accept Myriad into the Apache Incubator
+1 (non-binding) ~ Joe Stein On Sun, Feb 22, 2015 at 4:04 PM, John D. Ament wrote: > Just curious - why 7 days instead of the standard 72 hour window. > > Either way, +1, good luck with incubation. > > John > > On Sun Feb 22 2015 at 12:35:57 AM Adam Bordelon > wrote: > > > Hello friends, > > > > After receiving a positive response on the discussion thread, and even a > > new Mentor (Luciano), I would like to call a VOTE to accept Myriad into > the > > Apache Incubator. I will end the vote after 7 days. > > > > https://wiki.apache.org/incubator/MyriadProposal?action=recall&rev=7 > > > > [ ] +1 Accept Myriad into the Incubator > > [ ] +0 Don’t care. > > [ ] -1 Don’t accept Myriad into the Incubator because.. > > > > I am clearly a +1. > > > > Thanks, > > -Adam- > > me@apache > > >
Re: [VOTE] Accept DataFu into the Incubator
+1 (non-binding) Awesome! Happy New Year!!! - Joe Stein On Dec 31, 2013, at 3:48 PM, Roman Shaposhnik wrote: > On Tue, Dec 31, 2013 at 12:39 PM, Jakob Homan wrote: >> Incubator- >> >> Following the discussion earlier, I'm calling a vote to accept DataFu as a >> new Incubator project. >> >> The proposal draft is available at: >> https://wiki.apache.org/incubator/DataFuProposal, and is also included >> below. >> >> Vote is open for at least 96h and closes at the earliest on 4 Jan 13:00 >> PDT. I'm letting the vote run an extra day as we're in the holiday season. >> >> [ ] +1 accept DataFu in the Incubator >> [ ] +/-0 >> [ ] -1 because... >> >> Here's my binding +1. > > +1 (binding) > > Thanks, > Roman. > > - > 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: [VOTE] Accept Twill for Incubation
+1 (non-binding) On Thu, Nov 7, 2013 at 7:16 PM, Edward J. Yoon wrote: > +1 (non-binding) > > On Fri, Nov 8, 2013 at 7:37 AM, Alejandro Abdelnur > wrote: > > +1 > > > > > > On Thu, Nov 7, 2013 at 2:19 PM, Roman Shaposhnik wrote: > > > >> On Thu, Nov 7, 2013 at 1:04 PM, Andreas Neumann > wrote: > >> > The discussion about the Weave proposal has calmed. As the outcome of > the > >> > discussion, we have chosen a new name for the project, Twill. I would > >> like > >> > to call a vote for Twill to become an incubated project. > >> > > >> > The proposal is pasted below, and also available at: > >> > https://wiki.apache.org/incubator/TwillProposal > >> > > >> > Let's keep this vote open for three business days, closing the voting > on > >> > Tuesday 11/12. > >> > > >> > [ ] +1 Accept Twill into the Incubator > >> > [ ] +0 Don't care. > >> > [ ] -1 Don't accept Twill because... > >> > >> +1 (binding) > >> > >> Thanks, > >> Roman. > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > >> > > > > > > -- > > Alejandro > > > > -- > Best Regards, Edward J. Yoon > @eddieyoon > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Accept Storm into the Incubator
+1 (non-binding) /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> / On Thu, Sep 12, 2013 at 3:19 PM, Doug Cutting wrote: > Discussion about the Storm proposal has subsided, issues raised now > seemingly resolved. > > I'd like to call a vote to accept Storm as a new Incubator podling. > > The proposal is included below and is also at: > > https://wiki.apache.org/incubator/StormProposal > > Let's keep the vote open for four working days, until 18 September. > > [ ] +1 Accept Storm into the Incubator > [ ] +0 Don't care. > [ ] -1 Don't accept Storm because... > > Doug > > > = Storm Proposal = > > == Abstract == > > Storm is a distributed, fault-tolerant, and high-performance realtime > computation system that provides strong guarantees on the processing > of data. > > == Proposal == > > Storm is a distributed real-time computation system. Similar to how > Hadoop provides a set of general primitives for doing batch > processing, Storm provides a set of general primitives for doing > real-time computation. Its use cases span stream processing, > distributed RPC, continuous computation, and more. Storm has become a > preferred technology for near-realtime big-data processing by many > organizations worldwide (see a partial list at > https://github.com/nathanmarz/storm/wiki/Powered-By). As an open > source project, Storm’s developer community has grown rapidly to 46 > members. > > == Background == > > The past decade has seen a revolution in data processing. MapReduce, > Hadoop, and related technologies have made it possible to store and > process data at scales previously unthinkable. Unfortunately, these > data processing technologies are not realtime systems, nor are they > meant to be. The lack of a "Hadoop of realtime" has become the biggest > hole in the data processing ecosystem. Storm fills that hole. > > Storm was initially developed and deployed at BackType in 2011. After > 7 months of development BackType was acquired by Twitter in July 2011. > Storm was open sourced in September 2011. > > Storm has been under continuous development on its Github repository > since being open-sourced. It has undergone four major releases (0.5, > 0.6, 0.7, 0.8) and many minor ones. > > > == Rationale == > > Storm is a general platform for low-latency big-data processing. It is > complementary to the existing Apache projects, such as Hadoop. Many > applications are actually exploring using both Hadoop and Storm for > big-data processing. Bringing Storm into Apache is very beneficial to > both Apache community and Storm community. > > The rapid growth of Storm community is empowered by open source. We > believe the Apache foundation is a great fit as the long-term home for > Storm, as it provides an established process for community-driven > development and decision making by consensus. This is exactly the > model we want for future Storm development. > > == Initial Goals == > >* Move the existing codebase to Apache >* Integrate with the Apache development process >* Ensure all dependencies are compliant with Apache License version 2.0 >* Incremental development and releases per Apache guidelines > > == Current Status == > > Storm has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many > minor ones. Storm 0.9 is about to be released. Storm is being used in > production by over 50 organizations. Storm codebase is currently > hosted at github.com, which will seed the Apache git repository. > > === Meritocracy === > > We plan to invest in supporting a meritocracy. We will discuss the > requirements in an open forum. Several companies have already > expressed interest in this project, and we intend to invite additional > developers to participate. We will encourage and monitor community > participation so that privileges can be extended to those that > contribute. > > === Community === > > The need for a low-latency big-data processing platform in the open > source is tremendous. Storm is currently being used by at least 50 > organizations worldwide (see > https://github.com/nathanmarz/storm/wiki/Powered-By), and is the most > starred Java project on Github. By bringing Storm into Apache, we > believe that the community will grow even bigger. > > === Core Developers === > > Storm was started by Nathan Marz at BackType, and now has developers > from Yahoo!, Microsoft, Alibaba, Infochimps, and many other companies. > > === Alignmen
Re: [PROPOSAL] Storm for Apache Incubator
sounds great +1 to include storm-kafka under a contrib folder of the Apache Storm project & for other modules (moving forward) based on community members showing initiative in working on and maintaing them On Wed, Sep 4, 2013 at 10:23 PM, Nathan Marz wrote: > I think that storm-kafka would make sense as a contrib module since it's > widely used. I'm not sure what to do with the other storm-contrib modules. > I figure the less code that's part of the initial repo the better, because > there will be less contribution/legal issues to sort out. How about this - > we plan to include storm-kafka under a contrib folder of the Apache Storm > project (just because a lot of people depend on it), and we can pull other > storm-contrib modules in if community members show initiative in working on > and maintaining them? > > If that all sounds good I'll update the proposal accordingly. > > > On Sep 4, 2013, at 6:41 PM, Joe Stein wrote: > > > What does this mean for storm contribs ( > > https://github.com/nathanmarz/storm-contrib)? (spouts & bolts) e.g The > > Apache Kafka spout already it is hard to know which to use and which is > > best for 0.7.X and 0.8.X-betaX... Is the Apache Storm project going to > > help corral that or is it only for Storm core as the proposal implies > with > > only the storm code base https://github.com/nathanmarz/storm being part > of > > the project? > > > > A lot of traffic on the existing user list is about spouts (e.g. the > Kafka > > Spout) and I was not sure if that would still be talked about or funneled > > somewhere else or what the thoughts/plans where for the parts built > within > > Storm that are existing now? > > > > /*** > > Joe Stein > > Founder, Principal Consultant > > Big Data Open Source Security LLC > > http://www.stealth.ly > > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > > / > > > > > > On Wed, Sep 4, 2013 at 4:34 PM, Nathan Marz > wrote: > > > >> We definitely need a storm-user list as the existing google groups > mailing > >> list for Storm is quite active. So we'll need to transition that over. I > >> agree on adding a storm-commits list and added it to the proposal. > >> > >> > >> On Wed, Sep 4, 2013 at 11:50 AM, Henry Saputra >>> wrote: > >> > >>> Excited about Storm coming to Apache. Small comment about the mailing > >> list, > >>> you may want to propose having: > >>> * storm-dev > >>> * storm-commits > >>> * storm-private (with moderated subscriptions) > >>> > >>> instead for starting into incubator. > >>> > >>> However, Storm has been a well known open source project, maybe it does > >>> valid to have storm-user from the beginning. But I think you may need > >>> storm-commits > >>> list to separate commits log from dev discussions. > >>> Mentors can chime in about this. > >>> > >>> Thanks, > >>> > >>> Henry > >>> > >>> > >>> > >>> On Wed, Sep 4, 2013 at 1:07 AM, Nathan Marz > >> wrote: > >>> > >>>> Hi everyone, > >>>> > >>>> I'd like to propose Storm to be an Apache Incubator project. After > much > >>>> thought I believe this is the right next step for the project, and I > >> look > >>>> forward to hearing everyone's thoughts and feedback! > >>>> > >>>> Here's a link to the proposal: > >>>> https://wiki.apache.org/incubator/StormProposal > >>>> > >>>> The proposal is also pasted below. > >>>> > >>>> -Nathan > >>>> > >>>> > >>>> = Storm Proposal = > >>>> > >>>> == Abstract == > >>>> > >>>> Storm is a distributed, fault-tolerant, and high-performance realtime > >>>> computation system that provides strong guarantees on the processing > of > >>>> data. > >>>> > >>>> == Proposal == > >>>> > >>>> Storm is a distributed real-time computation system. Similar to how > >>> Hadoop > >>>> provides a set of general primitives for doing batch processing, Storm > >>>> provides a set of general primitives for doing real-time
Re: [PROPOSAL] Storm for Apache Incubator
What does this mean for storm contribs ( https://github.com/nathanmarz/storm-contrib)? (spouts & bolts) e.g The Apache Kafka spout already it is hard to know which to use and which is best for 0.7.X and 0.8.X-betaX... Is the Apache Storm project going to help corral that or is it only for Storm core as the proposal implies with only the storm code base https://github.com/nathanmarz/storm being part of the project? A lot of traffic on the existing user list is about spouts (e.g. the Kafka Spout) and I was not sure if that would still be talked about or funneled somewhere else or what the thoughts/plans where for the parts built within Storm that are existing now? /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> / On Wed, Sep 4, 2013 at 4:34 PM, Nathan Marz wrote: > We definitely need a storm-user list as the existing google groups mailing > list for Storm is quite active. So we'll need to transition that over. I > agree on adding a storm-commits list and added it to the proposal. > > > On Wed, Sep 4, 2013 at 11:50 AM, Henry Saputra >wrote: > > > Excited about Storm coming to Apache. Small comment about the mailing > list, > > you may want to propose having: > > * storm-dev > > * storm-commits > > * storm-private (with moderated subscriptions) > > > > instead for starting into incubator. > > > > However, Storm has been a well known open source project, maybe it does > > valid to have storm-user from the beginning. But I think you may need > > storm-commits > > list to separate commits log from dev discussions. > > Mentors can chime in about this. > > > > Thanks, > > > > Henry > > > > > > > > On Wed, Sep 4, 2013 at 1:07 AM, Nathan Marz > wrote: > > > > > Hi everyone, > > > > > > I'd like to propose Storm to be an Apache Incubator project. After much > > > thought I believe this is the right next step for the project, and I > look > > > forward to hearing everyone's thoughts and feedback! > > > > > > Here's a link to the proposal: > > > https://wiki.apache.org/incubator/StormProposal > > > > > > The proposal is also pasted below. > > > > > > -Nathan > > > > > > > > > = Storm Proposal = > > > > > > == Abstract == > > > > > > Storm is a distributed, fault-tolerant, and high-performance realtime > > > computation system that provides strong guarantees on the processing of > > > data. > > > > > > == Proposal == > > > > > > Storm is a distributed real-time computation system. Similar to how > > Hadoop > > > provides a set of general primitives for doing batch processing, Storm > > > provides a set of general primitives for doing real-time computation. > Its > > > use cases span stream processing, distributed RPC, continuous > > computation, > > > and more. Storm has become a preferred technology for near-realtime > > > big-data processing by many organizations worldwide (see a partial list > > at > > > https://github.com/nathanmarz/storm/wiki/Powered-By). As an open > source > > > project, Storm’s developer community has grown rapidly to 46 members. > > > > > > == Background == > > > > > > The past decade has seen a revolution in data processing. MapReduce, > > > Hadoop, and related technologies have made it possible to store and > > process > > > data at scales previously unthinkable. Unfortunately, these data > > processing > > > technologies are not realtime systems, nor are they meant to be. The > lack > > > of a "Hadoop of realtime" has become the biggest hole in the data > > > processing ecosystem. Storm fills that hole. > > > > > > Storm was initially developed and deployed at BackType in 2011. After 7 > > > months of development BackType was acquired by Twitter in July 2011. > > Storm > > > was open sourced in September 2011. > > > > > > Storm has been under continuous development on its Github repository > > since > > > being open-sourced. It has undergone four major releases (0.5, 0.6, > 0.7, > > > 0.8) and many minor ones. > > > > > > == Rationale == > > > > > > Storm is a general platform for low-latency big-data processing. It is > > > complementa
Re: [VOTE] Accept Samza into the Incubator
+1 (non-binding) /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly <http://www.stealth.ly> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> / On Fri, Jul 26, 2013 at 8:37 PM, Srikanth Sundarrajan wrote: > +1 (non-binding) > > > > From: jgho...@gmail.com > > Date: Fri, 26 Jul 2013 12:52:49 -0700 > > Subject: [VOTE] Accept Samza into the Incubator > > To: general@incubator.apache.org > > > > Incubator- > > > > Following the discussion earlier this week, I'm calling a vote to accept > > Samza as a new Incubator project. > > > > The proposal draft is available at: > > https://wiki.apache.org/incubator/SamzaProposal, > > and is also included below. It is identical as what was proposed in the > > discussion except for removing the user list, per Marvin's suggestion. > > > > Vote is open for at least 96h and closes at the earliest on 30 July 13:00 > > PDT. I'm letting the vote run an extra day as we're bookending the > weekend > > and I want to give everybody a reasonable workweek margin. > > > > [ ] +1 accept Samza in the Incubator > > [ ] +/-0 > > [ ] -1 because... > > > > Here's my binding +1 > > > > -Jakob > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [ANNOUNCE] Eric Tschetter is a new committer for Apache Curator
Yeah! Congrats Eric!!! A fantastic library and great addition to keeping it awesome! On Sat, Jun 15, 2013 at 4:47 PM, Jordan Zimmerman wrote: > The Project Management Committee (PMC) for Apache Curator has asked Eric > Tschetter to become a committer and we are pleased to announce that he has > accepted. > > Eric Tschetter is the lead architect of Druid, Metamarkets' distributed, > in-memory database. He held senior engineering positions at Ning and > LinkedIn before joining Metamarkets. At LinkedIn, Eric productized > LinkedIn's PYMK with Hadoop. He holds bachelors degrees in Computer Science > and Japanese from the University of Texas at Austin, and a M.S. from the > University of Tokyo in Computer Science. Eric has made significant > contributions to Curator and will be a valued member of the team. > > -Jordan > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- /* Joe Stein http://www.linkedin.com/in/charmalloc Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> */
Re: [DISCUSS] [PROPOSAL] Hadoop Development Tools
> > used as the base for the tools. > > > > == Known Risks == > > > > === Orphaned Products === > > > > === Inexperience with Open Source === > > Adam Berry has experience of the Eclipse open source community, and has > > been building familiarity with the Apache processes through patches to > the > > existing source. > > > > === Reliance on Salaried Developers === > > Hadoop Development Tools will be developed with a mix of salaried and > > volunteer time. > > > > === Relationships with Other Apache Projects === > > Hadoop Development Tools is closely related to Apache Hadoop. > > > > === An Excessive Fascination with the Apache Brand === > > Given the success of Hadoop and associated projects, Apache is the > > natural place for the Hadoop Development Tools. Chris Mattman suggested > the > > Apache Incubator as appropriate on the Hadoop general mailing list > > following the success that MRUnit had taking the path from Hadoop contrib > > to an Apache top level project. > > > > == Documentation == > > Documentation for the current tools can be found at > > http://wiki.apache.org/hadoop/EclipsePlugIn > > > > == Initial Source == > > > > > http://svn.apache.org/repos/asf/hadoop/common/trunk/hadoop-mapreduce-project/src/contrib/eclipse-plugin/ > > > > == Source and Intellectual Property Submission Plan == > > The source, and any suggested initial patches, are already hosted either > > in Apache’s Subversion or JIRA. > > > > == External Dependencies == > > Eclipse Platform > > Eclipse Java Development Tools > > > > == Cryptography == > > Hadoop Development Tools likely does not fall into this area. > > > > == Required Resources == > > === Mailing lists === > > * hdt-dev > > * hdt-commits > > * hdt-user > > > > === Subversion Directory === > > * https://svn.apache.org/repos/asf/incubator/hdt > > > > === Issue Tracking === > > * JIRA Hadoop Development Tools (HDT) > > > > === Other Resources === > > * Jenkins/Hudson for builds and test running. > > > > == Initial Committers == > > * Adam Berry (amberry at yahoo-inc dot com) > > * Jeffrey Zemerick (jeffrrey at mtnfog dot com) > > > > == Affiliations == > > * Adam Berry - Yahoo! > > * Jeffrey Zemerick - Mountain Fog > > > > == Sponsors == > > === Champion === > > Chris Douglas > > > > === Nominated Mentors === > > Chris Douglas > > Chris Mattman > > > > === Sponsoring Entity === > > Incubator PMC > > > -- /* Joe Stein http://www.linkedin.com/in/charmalloc Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> */
Re: [VOTE] Release Kafka 0.7.2-incubating (Candidate 5)
[3] +1 (binding) Alan, Jakob, Chris [1] +1 (non-binding) Jun [1] 0 (binding) Owen) [0] -1 the vote passes IPMC and with the PPMC vote already passsed [3] +1 (binding) Jun, Neha, Chris [1] +1 (non-binding) Joel [0] 0 [0] -1 0.7.2 is ready to ship i will push the release to the origin server and update our download site and then send an anounce on the anouncement list Owen, I updated my pgp key @ id.apache.org and have an email out to folks in the trust chain I know to sign my pgp key which i put in my home dir... If I don't hear back from anyone by strata/hadoop world i will bug people in person =8^) thanks everyone On Wed, Oct 10, 2012 at 1:18 PM, Owen O'Malley wrote: > On Sun, Oct 7, 2012 at 10:17 AM, Joe Stein wrote: > > I would like to keep the vote open for another few days to give the IPMC > members time to review and vote, thanks. > > Joe, >Could you update your gpg key: > * set it in id.apache.org > * get someone who knows you to sign it. > > WIthout a signed key that is on id.apache.org, I'm -0 (binding) on the > release. I did verify the md5 checksum. > > -- Owen > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- /* Joe Stein http://www.linkedin.com/in/charmalloc Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> */
Re: [VOTE] Release Kafka 0.7.2-incubating (Candidate 5)
I would like to keep the vote open for another few days to give the IPMC members time to review and vote, thanks. On Oct 5, 2012, at 4:07 PM, Jun Rao wrote: > +1 > > Thanks, > > Jun > > On Wed, Oct 3, 2012 at 8:40 AM, Joe Stein wrote: > >> Hello, >> >> Kafka Incubator has passed the vote for 0.7.2 RC5 >> http://www.mail-archive.com/kafka-dev@incubator.apache.org/msg04980.html >> >> I would like to call a vote now from the IPMC. >> >> This is the fifth candidate for the third incubator release for Apache >> Kafka, version 0.7.2-incubating. >> >> This release fixes the following issues >> >> http://people.apache.org/~joestein/kafka-0.7.2-incubating-candidate-5/RELEASE-NOTES.html >> >> *** Please download, test and vote by Saturday October, 6th, 9am PDT *** >> >> Release artifacts to be voted upon: >> https://people.apache.org/~joestein/kafka-0.7.2-incubating-candidate-5/ >> >> The tag (off the 0.7.2 branch) for release artifacts: >> >> https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.2-incubating-candidate-5 >> >> Kafka's KEYS file containing PGP keys we use to sign the release: >> https://svn.apache.org/repos/asf/incubator/kafka/KEYS >> >> /* >> Joe Stein >> http://www.linkedin.com/in/charmalloc >> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> >> */ >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Kafka 0.7.2-incubating (Candidate 5)
Hello, Kafka Incubator has passed the vote for 0.7.2 RC5 http://www.mail-archive.com/kafka-dev@incubator.apache.org/msg04980.html I would like to call a vote now from the IPMC. This is the fifth candidate for the third incubator release for Apache Kafka, version 0.7.2-incubating. This release fixes the following issues http://people.apache.org/~joestein/kafka-0.7.2-incubating-candidate-5/RELEASE-NOTES.html *** Please download, test and vote by Saturday October, 6th, 9am PDT *** Release artifacts to be voted upon: https://people.apache.org/~joestein/kafka-0.7.2-incubating-candidate-5/ The tag (off the 0.7.2 branch) for release artifacts: https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.2-incubating-candidate-5 Kafka's KEYS file containing PGP keys we use to sign the release: https://svn.apache.org/repos/asf/incubator/kafka/KEYS /* Joe Stein http://www.linkedin.com/in/charmalloc Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> */
[ANNOUNCEMENT] Apache Kafka 0.7.1-incubating Released
Hi. The Apache Kafka team is pleased to announce the release of Kafka 0.7.1-incubating. This is the second incubating release of Apache Kafka, a distributed publish-subscribe messaging system. You can download the release from: http://incubator.apache.org/kafka/downloads.html The full change log is available here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311720&version=12319140 We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://incubator.apache.org/kafka/ /* * The Apache Kafka Team */
[RESULT] [VOTE] Release Kafka 0.7.1-incubating (Candidate 3)
Incubating mailing list http://www.mail-archive.com/general@incubator.apache.org/msg35486.html Kafka mailing list http://www.mail-archive.com/kafka-dev@incubator.apache.org/msg03268.html Chris Douglas (PPMC/IPMC) = +1 Kevan Miller (IPMC) = -1 Jun Rao (PPMC) = +1 Jakob Homan (PPMC/IPMC) = +1 The vote passes with at least 3 x +1 and majority +1 votes. We will be updating the site and sending an announcement of the Apache Kafka 0.7.1 release as next steps. /* Joe Stein http://www.linkedin.com/in/charmalloc Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> */
Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 3)
1) snappy-java-1.0.4.1.jar is required when setting Snappy as a compression codec which is pulled from maven from ./sbt update and is Apache License 2.0 http://code.google.com/p/snappy-java/ 2) ZooKeeper client jar upgraded from 3.3.3 to 3.3.4 On Thu, Jun 21, 2012 at 2:32 PM, Chris Douglas wrote: > Did these dependencies change between 0.7.0 and 0.7.1? -C > > On Wed, Jun 20, 2012 at 10:36 PM, Alan D. Cabrera > wrote: > > > > On Jun 20, 2012, at 9:19 AM, Joe Stein wrote: > > > >> Hello, > >> > >> This is the third candidate for the second incubator release for Apache > >> Kafka, version 0.7.1-incubating. > >> > >> This release fixes the following issues > >> > http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html > >> > >> Release artifacts: > >> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3 > >> > >> The tag to be voted upon (off the 0.7.1 branch): > >> > https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/ > >> > >> Kafka's KEYS file containing PGP keys we use to sign the release: > >> http://svn.apache.org/repos/asf/incubator/kafka/KEYS > >> > >> The vote will be open for 72 hours (longer if needed). > > > > > > I need help checking these jars. What I recommend is that we update > NOTICE in trunk as we attribute licenses to the jars below. This way we > still vet the jars, update the NOTICE/LICENSE file in trunk for the next > release, and not force Joe to cut a new release to include the updated > NOTICE/LICENSE file. > > > > This will make subsequent releases go much easier. > > > > BTW, the keys and signatures are fine. Tests pass. > > > > (linkedin)[acabrera-mn:kafka-0.7.1-incubating 525]$ find . -name "*.jar" > > ./contrib/hadoop-consumer/lib/piggybank.jar > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/ant-1.6.5.jar > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/asm-3.2.jar > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/avro-1.3.2.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-cli-1.2.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-codec-1.4.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-el-1.0.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-httpclient-3.1.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-lang-2.5.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-logging-1.1.1.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-net-1.4.1.jar > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/core-3.1.1.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hadoop-core-0.20.2.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/hsqldb-1.8.0.10.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-core-asl-1.4.2.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jackson-mapper-asl-1.4.2.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-compiler-5.5.12.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jasper-runtime-5.5.12.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jets3t-0.7.1.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jetty-6.1.14.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jetty-util-6.1.14.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/joda-time-1.6.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jsp-2.1-6.1.14.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jsp-api-2.1-6.1.14.jar > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/kfs-0.3.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/log4j-1.2.15.jar > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/oro-2.0.8.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/paranamer-2.2.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/paranamer-ant-2.2.jar > > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/paranamer-generator-2.2.jar > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/pig-0.8.0.jar > > ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/c
[VOTE] Release Kafka 0.7.1-incubating (Candidate 3)
Hello, This is the third candidate for the second incubator release for Apache Kafka, version 0.7.1-incubating. This release fixes the following issues http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3/RELEASE-NOTES.html Release artifacts: http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-3 The tag to be voted upon (off the 0.7.1 branch): https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-3/ Kafka's KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/kafka/KEYS The vote will be open for 72 hours (longer if needed). /* Joe Stein http://www.linkedin.com/in/charmalloc Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> */
Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 2)
I uploaded a md5 checksum http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/ to go along with the detached signature that was generated already starting the kafka server is in the quick start http://incubator.apache.org/kafka/quickstart.html looking at Cassandra and Hadoop source distributions both have jars in them too, so not sure the issue you are raising others might have a better understanding or I am missing something you are trying to point out I would like to keep the RC2 voting open for another few days to see if this release passes (as folks have not had time to review) or we can get to what issues we need to have resolved that can be done for RC3 for a new vote either with objective to getting 0.7.1 released. current votes: +1 [1] +0 [0] -1 [0] from the PPMC and +1 [0] +0 [0] -1 [0] from the IPMC please let me know if there is something different we want or should have been doing here or that I can be or should be doing differently. thanks! On Mon, Jun 18, 2012 at 4:53 PM, Kevan Miller wrote: > Things that I've noted: > > I don't see a checksum for your release in > http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/ -- > your release manager will need to generate a checksum for the release. > > It would be nice if your archive extracted into an > apache-kafka-0.7.1-incubating directory (or similar name rather than .), > but that's minor. > > I see the following binary files in your source distribution: > > ./clients/csharp/lib/nunit/2.5.9/nunit.framework.dll > ./contrib/hadoop-consumer/lib/pig-0.8.0-core.jar > ./contrib/hadoop-consumer/lib/piggybank.jar > ./contrib/hadoop-producer/lib/pig-0.8.0-core.jar > ./contrib/hadoop-producer/lib/piggybank.jar > ./lib/sbt-launch.jar > > If I understand correctly, this does not meet a definition of an open > source release (which is what an apache release is…). It looks like this is > how your last release was packaged, also… I don't know if this is a > blocking issue (for an incubator release), but I think you need to work on > resolving this (i.e. remove binaries from your source)… > > IIUC, your LICENSE/NOTICE files are documenting your "source" (including > the above jars). Do you document the LICENSE/NOTICE of your binaries? I > built kafka and see that a number jars are pulled in… I have no idea what > the LICENSING for these artifacts is… and whether or not they conform to > ASF standards (I did not review them all). Your project needs to document > them. > > FYI, I couldn't figure out from the documentation how to start a server > after I built kafka. > > --kevan > > On Jun 18, 2012, at 1:14 PM, Jun Rao wrote: > > > Any other voters? > > > > Thanks, > > > > Jun > > > > On Thu, Jun 14, 2012 at 11:42 AM, Joe Stein wrote: > > > >> Hello, > >> > >> This is the second candidate for the second incubator release for Apache > >> Kafka, version 0.7.1-incubating. > >> > >> This release fixes the following issues > >> > >> > http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/RELEASE-NOTES.html > >> > >> RC2 fixes the issue identified in RC1 => > >> https://issues.apache.org/jira/browse/KAFKA-365 change copyright in > NOTICE > >> to 2012 > >> > >> *** Please download, test and vote by Monday June, 18th, 12pm PDT > >> > >> Release artifacts: > >> http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/ > >> > >> The tag to be voted upon (off the 0.7.1 branch): > >> > >> > https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-2 > >> > >> Kafka's KEYS file containing PGP keys we use to sign the release: > >> http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS > >> > >> /* > >> Joe Stein > >> http://www.linkedin.com/in/charmalloc > >> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > >> */ > >> > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- /* Joe Stein http://www.linkedin.com/in/charmalloc Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> */
[VOTE] Release Kafka 0.7.1-incubating (Candidate 2)
Hello, This is the second candidate for the second incubator release for Apache Kafka, version 0.7.1-incubating. This release fixes the following issues http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/RELEASE-NOTES.html RC2 fixes the issue identified in RC1 => https://issues.apache.org/jira/browse/KAFKA-365 change copyright in NOTICE to 2012 *** Please download, test and vote by Monday June, 18th, 12pm PDT Release artifacts: http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-2/ The tag to be voted upon (off the 0.7.1 branch): https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-2 Kafka's KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS /* Joe Stein http://www.linkedin.com/in/charmalloc Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> */
Re: [VOTE] Release Kafka 0.7.1-incubating (Candidate 1)
Vote cancelled I will roll RC2 with a fix for this issue ( https://issues.apache.org/jira/browse/KAFKA-365) within it thanks! On Thu, Jun 14, 2012 at 12:45 PM, sebb wrote: > On 14 June 2012 17:34, Joe Stein wrote: > > Hello, > > > > This is the first candidate for the second incubator release for > > Apache Kafka, version 0.7.1-incubating. > > > > This release fixes the following issues > > > http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-1/RELEASE-NOTES.html > > > > *** Please download, test and vote by Monday June, 18th, 12pm PDT > > > > Release artifacts: > > http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-1/ > > > > The tag to be voted upon (off the 0.7.1 branch): > > > https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-1 > > NOTICE says: > > Copyright 2011 > > > > > Kafka's KEYS file containing PGP keys we use to sign the release: > > http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS > > > > /* > > Joe Stein > > http://www.linkedin.com/in/charmalloc > > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > > */ > > --------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- /* Joe Stein http://www.linkedin.com/in/charmalloc Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> */
[VOTE] Release Kafka 0.7.1-incubating (Candidate 1)
Hello, This is the first candidate for the second incubator release for Apache Kafka, version 0.7.1-incubating. This release fixes the following issues http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-1/RELEASE-NOTES.html *** Please download, test and vote by Monday June, 18th, 12pm PDT Release artifacts: http://people.apache.org/~joestein/kafka-0.7.1-incubating-candidate-1/ The tag to be voted upon (off the 0.7.1 branch): https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.1-incubating-candidate-1 Kafka's KEYS file containing PGP keys we use to sign the release: http://svn.apache.org/repos/asf/incubator/kafka/trunk/KEYS /* Joe Stein http://www.linkedin.com/in/charmalloc Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> */
