Hi, Jihoon,
Thanks for the running the release. +1 from me.
Jun
On Tue, Jun 25, 2019 at 10:59 AM Julian Hyde wrote:
> Forwarding my vote from the dev list:
>
> +1 (binding)
>
> I am grateful for Sebb’s thorough review but I don’t see anything that
> blocks the release (e.g. the commit hash is
Thanks for running the release.
The link
https://repository.apache.org/content/repositories/orgapachedruid-1005/ seems
broken. Hopefully that's just a staging issue.
Other than that. +1
Jun
On Wed, May 15, 2019 at 6:55 PM Clint Wylie wrote:
> Hi IPMC,
>
> The Apache Druid community has voted
Could you remove Kafka from the incubator report since it already graduated
to a top level project last Nov?
Thanks,
Jun
On Mon, Apr 1, 2013 at 9:01 PM, Dave Fisher wrote:
> Hi,
>
> Sorry, I just realized I had replied in private and this is a comment for
> general@.
>
> Regards,
> Dave
>
> On
+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 t
Joe,
Since this is still fresh in your mind, could you write a short description
of the release process (probably under developer on the site) including
copying the artifact to the dist directory?
Also, are you still able to do svn up under /www/
incubator.apache.org/content/kafka? It complains t
Alan,
I found the list of jars that you published during the 0.7.0 release. The
new jars in the 0.7.1 release are the following:
commons-cli: AL2
commons-el: AL2
commons-net: AL2
commons-io: AL2
commons-compress: AL2
core: Eclipse Public License 1.0
hsqldb: BSD
jasper-compiler: AL2
jasper-runtime:
27;s not true. There are a significant number of new jars.
> >>
> >>> That was deemed acceptable and so without a
> >>> lot of new directives, which don't seem to be clear here, so should
> >>> this one.
> >>>
> >>> Bind
ding).
>
> That's not true. There are a significant number of new jars.
>
> > That was deemed acceptable and so without a
> > lot of new directives, which don't seem to be clear here, so should
> > this one.
> >
> > Binding +1 on RC3.
> >
> &g
Alan,
I compared all dependent jars in 0.7.1 with 0.7.0. Other than upgrades, the
only added jar in 0.7.1 is the following.
./core/lib_managed/scala_2.8.0/compile/snappy-java-1.0.4.1.jar
Snappy is on Apache License 2.0. So, our licenses should be covered.
Thanks,
Jun
On Thu, Jun 21, 2012 at 9
+1 on the release.
Run quickstart and unit tests. All good.
Thanks,
Jun
On Wed, 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
>
> htt
Kevan,
I agree that to the benefit of users, it would be reasonable for Apache
projects to include license/notice for all dependant jars (directly or
indirectly) in a release. However, this has to be done automatically by
tools, not manually by human beings. IMO, without such tools, it's unfair
(a
Joe,
It looks like that we need to create a new RC. Could you pick up kafka-366?
It just adds a new jmx.
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.
>
>
tifacts 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,
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
Ran quick start, unit tests and rat tests.
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.a
Could someone help take a look at this? This should be pretty simple. We
really want to proceed with the voting of the first release of Kafka.
Thanks,
Jun
On Fri, Dec 9, 2011 at 3:51 PM, Neha Narkhede wrote:
> Folks,
>
> Thanks for giving feedback on the LICENSE and NOTICE file issues. We've
>
Does Apache has tools (like rat) to extract all the needed license? Digging
out the license manually is both labour intensive and error prone.
Thanks,
Jun
On Thu, Dec 1, 2011 at 1:05 PM, Kevan Miller wrote:
>
> On Dec 1, 2011, at 12:55 PM, Neha Narkhede wrote:
>
> >>> As it stands, either the
27, 2011 at 7:13 PM, Jun Rao wrote:
> > Dear Apache members,
> >
> > Over the past 2 months, the Kafka Apache incubator project has been
> trying
> > to release its very first version in Apache. After 7 RCs, we are still
> not
> > done. Part of this is because m
Dear Apache members,
Over the past 2 months, the Kafka Apache incubator project has been trying
to release its very first version in Apache. After 7 RCs, we are still not
done. Part of this is because most of us are new to the Apache release
process and are learning things along the way. However,
,
Jun
On Tue, Nov 15, 2011 at 7:27 AM, sebb wrote:
> On 15 November 2011 15:05, Jun Rao wrote:
> > The distribution does include source code in it. Are you saying that we
> > should have a separate source distribution with no jars in it?
>
> Yes, that is the normal way
The distribution does include source code in it. Are you saying that we
should have a separate source distribution with no jars in it?
Thanks,
Jun
On Mon, Nov 14, 2011 at 5:37 PM, sebb wrote:
> On 14 November 2011 19:52, Neha Narkhede wrote:
> > Hi,
> >
> > Kafka community is excited to share
Hi,
To celebrate the introduction of Kafka to Apache incubator, we plan to
design an internal T-shirt at LinkedIn. Is it legal to put the Apache logo
(red feather) on the T-shirt?
Thanks,
Jun
Hi, Everyone,
The 72 hour lazy consensus period has elapsed and the vote has passed.
By my tally, we have:
* 9 +1's from IPMC Members
* 9 +1's from other folks
* no -1 votes, and no 0 votes.
Binding votes (9):
Chris Mattmann
Nigel Daley
Alan D. Cabrera
Mohammad Nour El-Din
Chris Douglas
Bertrand
this goal, we use GitHub issue tracking and branching facilities,
as well as maintaining a public mailing list via Google Groups.
=== Core Developers ===
Kafka is currently being developed by four engineers at LinkedIn: Neha
Narkhede, Jun Rao, Jakob Homan and Jay Kreps. Jun has experience within
Apach
Hi, Joe,
I'd expect people to contribute as any open source project : try/test the
code, discuss on the mailing list, create/comment on the jira, submit/review
patches, and become a committer.
Thanks,
Jun
On Tue, Jun 28, 2011 at 9:18 AM, Joe Key wrote:
> Excellent! I have already voted on th
Ioannis,
That's fine. I just want to point out that Kafka does/will have some
difference from ActiveMQ given (1) its simple storage format; (2) how it
uses Zookeeper for distributed coordination; (3) the future replication work
http://linkedin.jira.com/browse/KAFKA-23 . Let us know if you become
i
Thanks Shalin, Phillip. Welcome aboard, Phillip.
Jun
On Fri, Jun 24, 2011 at 6:34 AM, Phillip Rhodes
wrote:
> On Fri, Jun 24, 2011 at 8:51 AM, Shalin Shekhar Mangar <
> shalinman...@gmail.com> wrote:
>
> > On Wed, Jun 22, 2011 at 9:47 PM, Jun Rao wrote:
> > > H
Thanks for the comments, Ioannis. Will refine the proposal. Welcome aboard!
Jun
On Fri, Jun 24, 2011 at 1:00 AM, Ioannis Canellos wrote:
> Great!
>
> Here is my + 1
>
> I have a comment to add. ActiveMQ does provide means for persisting the
> messages, so you might want to clarify or rephrase t
Thanks, Tommaso, Chris and Mattmann.
Jun
On Thu, Jun 23, 2011 at 8:07 AM, Tommaso Teofili
wrote:
> Wow, very nice proposal guys!
> Tommaso
>
> 2011/6/22 Jun Rao
>
> > Hi,
> >
> > I would like to propose Kafka to be an Apache Incubator project. Kafka
> is
&g
T and Python.
To further this goal, we use GitHub issue tracking and branching facilities,
as well as maintaining a public mailing list via Google Groups.
=== Core Developers ===
Kafka is currently being developed by four engineers at LinkedIn: Neha
Narkhede, Jun Rao, Jakob Homan and Jay Kreps.
30 matches
Mail list logo