You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by Neha Narkhede <ne...@gmail.com> on 2011/10/17 19:45:06 UTC
[VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Hi,
This is the fourth candidate for the first incubator release for
Apache Kafka, version 0.7.0-incubating.
There are *no* code changes since candidate 3. This candidate is
published to follow the updated release
process for Kafka.
It fixes the following issues:
http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/RELEASE-NOTES.html
*** Please download, test and vote by Oct, 20th, 10 am
Note that we are voting upon the source (revision), binaries are
provided for convenience.
Source and binary files:
http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/
The SVN revision to be voted upon:
https://svn.apache.org/repos/asf/incubator/kafka/0.7@1185297
Kafka's KEYS file containing PGP keys we use to sign the release:
http://svn.apache.org/repos/asf/incubator/kafka/KEYS
Note that the Incubator PMC needs to vote upon the release after a
successful PPMC vote before
any release can be made official.
Thanks,
Neha
Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by Chris Douglas <cd...@apache.org>.
+1
Ran tests, MD5/signature match. Assuming RAT still passes with 0
failures per KAFKA-143. Assuming licenses are all approved, per
KAFKA-142.
I did get one test failure:
[info] Test Starting: testLoadBalance(kafka.zk.ZKLoadBalanceTest)
[error] Test Failed: testLoadBalance(kafka.zk.ZKLoadBalanceTest)
junit.framework.AssertionFailedError: expected:<5> but was:<2>
[snip]
at kafka.zk.ZKLoadBalanceTest.checkSetEqual(ZKLoadBalanceTest.scala:121)
at kafka.zk.ZKLoadBalanceTest.testLoadBalance(ZKLoadBalanceTest.scala:89)
-C
On Mon, Oct 17, 2011 at 10:45 AM, Neha Narkhede <ne...@gmail.com> wrote:
> Hi,
>
> This is the fourth candidate for the first incubator release for
> Apache Kafka, version 0.7.0-incubating.
> There are *no* code changes since candidate 3. This candidate is
> published to follow the updated release
> process for Kafka.
>
> It fixes the following issues:
> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/RELEASE-NOTES.html
>
> *** Please download, test and vote by Oct, 20th, 10 am
>
> Note that we are voting upon the source (revision), binaries are
> provided for convenience.
>
> Source and binary files:
> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/
>
> The SVN revision to be voted upon:
> https://svn.apache.org/repos/asf/incubator/kafka/0.7@1185297
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>
> Note that the Incubator PMC needs to vote upon the release after a
> successful PPMC vote before
> any release can be made official.
>
> Thanks,
> Neha
>
Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by Neha Narkhede <ne...@gmail.com>.
>> I did get one test failure:
[info] Test Starting: testLoadBalance(kafka.zk.ZKLoadBalanceTest)
[error] Test Failed: testLoadBalance(kafka.zk.ZKLoadBalanceTest)
junit.framework.AssertionFailedError: expected:<5> but was:<2>
[snip]
at kafka.zk.ZKLoadBalanceTest.checkSetEqual(ZKLoadBalanceTest.scala:121)
at kafka.zk.ZKLoadBalanceTest.testLoadBalance(ZKLoadBalanceTest.scala:89)
As Jun had mentioned earlier, we still do have some time dependent
unit tests that tend
to fail on some boxes. We want to clean it up soon.
Thanks,
Neha
On Mon, Oct 17, 2011 at 2:08 PM, Neha Narkhede <ne...@gmail.com> wrote:
>>> Why would the project be stuck with it? The repository can always berearranged, right?
>
> Yeah, that was overlooked by me while creating the branch. We thought
> that we will
> just rearrange the repo after the vote to fix the /branches/0.7 path.
>
> Thanks for the clarification Chris !
>
> -Neha
>
> On Mon, Oct 17, 2011 at 1:32 PM, Chris Douglas <cd...@apache.org> wrote:
>> On Mon, Oct 17, 2011 at 11:39 AM, Alan D. Cabrera <ad...@toolazydogs.com> wrote:
>>>> 5. Specify the NEW svn revision to be voted upon. For example,
>>>> http://svn.apache.org/repos/asf/incubator/kafka/trunk@r1181186
>>>
>>> Shouldn't 0.7 be in branches or tags? Once the vote goes through the project will be stuck with kafka/0.7. Is this what you guys want?
>>
>> Why would the project be stuck with it? The repository can always be
>> rearranged, right?
>>
>> For integration with SVN tools, using the
>> ROOT/{branches,tags}/$version layout is probably worthwhile. If it's a
>> branch, just move it into place. -C
>>
>
Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by Neha Narkhede <ne...@gmail.com>.
>> Why would the project be stuck with it? The repository can always berearranged, right?
Yeah, that was overlooked by me while creating the branch. We thought
that we will
just rearrange the repo after the vote to fix the /branches/0.7 path.
Thanks for the clarification Chris !
-Neha
On Mon, Oct 17, 2011 at 1:32 PM, Chris Douglas <cd...@apache.org> wrote:
> On Mon, Oct 17, 2011 at 11:39 AM, Alan D. Cabrera <ad...@toolazydogs.com> wrote:
>>> 5. Specify the NEW svn revision to be voted upon. For example,
>>> http://svn.apache.org/repos/asf/incubator/kafka/trunk@r1181186
>>
>> Shouldn't 0.7 be in branches or tags? Once the vote goes through the project will be stuck with kafka/0.7. Is this what you guys want?
>
> Why would the project be stuck with it? The repository can always be
> rearranged, right?
>
> For integration with SVN tools, using the
> ROOT/{branches,tags}/$version layout is probably worthwhile. If it's a
> branch, just move it into place. -C
>
Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
On Oct 17, 2011, at 3:48 PM, Chris Douglas wrote:
> On Mon, Oct 17, 2011 at 2:13 PM, Alan D. Cabrera <li...@toolazydogs.com> wrote:
>>> Why would the project be stuck with it? The repository can always be
>>> rearranged, right?
>>
>> That's not my understanding but I could be wrong. I do not agree with your reply to Neha where you state the project can rename the tag after the vote. If a project publicly votes on a tag then the project is stuck with it. This is something that I know many IPMC members, including Noel, feel strongly about. Again, I could be wrong.
>
> If you couldn't rename the tag, then an RC candidate that passes a
> vote would need a separate vote to give it a sane name in the
> repository, or one couldn't run two concurrent votes for the same
> version.
>
> Binding a vote to a tag is elegant, presumably so the vote in the mail
> archive can refer to a fixed point in the repository. It's not a
> requirement, though. The MD5/signature, creating branches, creating
> tags etc. are all to ensure that voters are clear about what they're
> approving. Without these, it's too easy to get confused, or fail to
> detect that the artifact approved by the PMC doesn't match what is
> pushed to mirrors. It's good practice.
>
> Asserting that the repository is fixed by the vote is pedantic. It's
> not *good* for it to churn, but the whole purpose of "approving" a
> release is for the PMC to certify that its content is property
> licensed, approved by the majority of the PMC, and that it was
> developed in concert with Apache's policies. A tag makes that easier
> to ensure, but it's neither necessary nor sufficient. -C
A good outline about important points of a release.
However, even Neha states that the placement of the 0.7 tag was a mistake. Fits and starts for release votes appear in most projects and especially so for podlings attempting to get their first release out.
To be frank, if there was a discussion about what to release and how to go about it before rushing to a vote, we wouldn't be at candidate 4 of this release.
Regards,
Alan
Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by Chris Douglas <cd...@apache.org>.
On Mon, Oct 17, 2011 at 2:13 PM, Alan D. Cabrera <li...@toolazydogs.com> wrote:
>> Why would the project be stuck with it? The repository can always be
>> rearranged, right?
>
> That's not my understanding but I could be wrong. I do not agree with your reply to Neha where you state the project can rename the tag after the vote. If a project publicly votes on a tag then the project is stuck with it. This is something that I know many IPMC members, including Noel, feel strongly about. Again, I could be wrong.
If you couldn't rename the tag, then an RC candidate that passes a
vote would need a separate vote to give it a sane name in the
repository, or one couldn't run two concurrent votes for the same
version.
Binding a vote to a tag is elegant, presumably so the vote in the mail
archive can refer to a fixed point in the repository. It's not a
requirement, though. The MD5/signature, creating branches, creating
tags etc. are all to ensure that voters are clear about what they're
approving. Without these, it's too easy to get confused, or fail to
detect that the artifact approved by the PMC doesn't match what is
pushed to mirrors. It's good practice.
Asserting that the repository is fixed by the vote is pedantic. It's
not *good* for it to churn, but the whole purpose of "approving" a
release is for the PMC to certify that its content is property
licensed, approved by the majority of the PMC, and that it was
developed in concert with Apache's policies. A tag makes that easier
to ensure, but it's neither necessary nor sufficient. -C
Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
On Oct 17, 2011, at 1:32 PM, Chris Douglas wrote:
> On Mon, Oct 17, 2011 at 11:39 AM, Alan D. Cabrera <ad...@toolazydogs.com> wrote:
>>> 5. Specify the NEW svn revision to be voted upon. For example,
>>> http://svn.apache.org/repos/asf/incubator/kafka/trunk@r1181186
>>
>> Shouldn't 0.7 be in branches or tags? Once the vote goes through the project will be stuck with kafka/0.7. Is this what you guys want?
>
> Why would the project be stuck with it? The repository can always be
> rearranged, right?
That's not my understanding but I could be wrong. I do not agree with your reply to Neha where you state the project can rename the tag after the vote. If a project publicly votes on a tag then the project is stuck with it. This is something that I know many IPMC members, including Noel, feel strongly about. Again, I could be wrong.
I'd like to take a bit of time out to point out that much of what I post is not hard gospel and I am by no means the final arbiter. As my wife is quick to point out, I frequently recall things incorrectly.
Regards,
Alan
Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by Chris Douglas <cd...@apache.org>.
On Mon, Oct 17, 2011 at 11:39 AM, Alan D. Cabrera <ad...@toolazydogs.com> wrote:
>> 5. Specify the NEW svn revision to be voted upon. For example,
>> http://svn.apache.org/repos/asf/incubator/kafka/trunk@r1181186
>
> Shouldn't 0.7 be in branches or tags? Once the vote goes through the project will be stuck with kafka/0.7. Is this what you guys want?
Why would the project be stuck with it? The repository can always be
rearranged, right?
For integration with SVN tools, using the
ROOT/{branches,tags}/$version layout is probably worthwhile. If it's a
branch, just move it into place. -C
Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by "Alan D. Cabrera" <ad...@toolazydogs.com>.
On Oct 18, 2011, at 10:26 AM, Jun Rao wrote:
> Alan,
>
> As for the release binaries, many other Apache projects (e.g., Zookeeper,
> Cassandra, Hadoop) do the same. Since everything is available after the
> download, it's easy for users to try it out. We can remove the unnecessary
> .class files.
It's up to you guys. I didn't see a discussion as to what the project feels should go into it and so I inquired.
> As for whether to vote off trunk or a branch, most other Apache projects
> vote off a branch. This may not be really needed for Kafka at this point.
> However, I think it's easier to track changes, especially if we want to have
> a bug fix release off 0.7. We will create the branch under /branches.
Up to you guys. As above, I didn't see a discussion by the project as to how it wants to perform releases. This is one of the things that the Incubator is all about, getting use to public discussion and consensus building. As mentioned by Chris in an earlier post, it's a good idea to bind a vote to a tag; don't be afraid to trash tags until the final vote passes. Again, it's up to you guys.
Regards,
Alan
>
> Jun
>
> On Mon, Oct 17, 2011 at 11:39 AM, Alan D. Cabrera <ad...@toolazydogs.com>wrote:
>
>>
>> On Oct 17, 2011, at 10:45 AM, Neha Narkhede wrote:
>>
>>> Hi,
>>>
>>> This is the fourth candidate for the first incubator release for
>>> Apache Kafka, version 0.7.0-incubating.
>>> There are *no* code changes since candidate 3. This candidate is
>>> published to follow the updated release
>>> process for Kafka.
>>>
>>> It fixes the following issues:
>>>
>> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/RELEASE-NOTES.html
>>>
>>> *** Please download, test and vote by Oct, 20th, 10 am
>>>
>>> Note that we are voting upon the source (revision), binaries are
>>> provided for convenience.
>>
>> Since this is a _source_ release I'm not sure there should be binaries,
>> e.g. kafka-*.jar, *.class, files in the distribution. The d/l is 50M. Up
>> to you guys.
>>
>>> Source and binary files:
>>>
>> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/
>>>
>>> The SVN revision to be voted upon:
>>> https://svn.apache.org/repos/asf/incubator/kafka/0.7@1185297
>>
>> I thought the plan was to vote off of trunk, e.g.
>>
>>> 5. Specify the NEW svn revision to be voted upon. For example,
>>> http://svn.apache.org/repos/asf/incubator/kafka/trunk@r1181186
>>
>> Shouldn't 0.7 be in branches or tags? Once the vote goes through the
>> project will be stuck with kafka/0.7. Is this what you guys want?
>>
>>
>> Regards,
>> Alan
>>
>>
Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by Jun Rao <ju...@gmail.com>.
Alan,
As for the release binaries, many other Apache projects (e.g., Zookeeper,
Cassandra, Hadoop) do the same. Since everything is available after the
download, it's easy for users to try it out. We can remove the unnecessary
.class files.
As for whether to vote off trunk or a branch, most other Apache projects
vote off a branch. This may not be really needed for Kafka at this point.
However, I think it's easier to track changes, especially if we want to have
a bug fix release off 0.7. We will create the branch under /branches.
Jun
On Mon, Oct 17, 2011 at 11:39 AM, Alan D. Cabrera <ad...@toolazydogs.com>wrote:
>
> On Oct 17, 2011, at 10:45 AM, Neha Narkhede wrote:
>
> > Hi,
> >
> > This is the fourth candidate for the first incubator release for
> > Apache Kafka, version 0.7.0-incubating.
> > There are *no* code changes since candidate 3. This candidate is
> > published to follow the updated release
> > process for Kafka.
> >
> > It fixes the following issues:
> >
> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/RELEASE-NOTES.html
> >
> > *** Please download, test and vote by Oct, 20th, 10 am
> >
> > Note that we are voting upon the source (revision), binaries are
> > provided for convenience.
>
> Since this is a _source_ release I'm not sure there should be binaries,
> e.g. kafka-*.jar, *.class, files in the distribution. The d/l is 50M. Up
> to you guys.
>
> > Source and binary files:
> >
> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/
> >
> > The SVN revision to be voted upon:
> > https://svn.apache.org/repos/asf/incubator/kafka/0.7@1185297
>
> I thought the plan was to vote off of trunk, e.g.
>
> > 5. Specify the NEW svn revision to be voted upon. For example,
> > http://svn.apache.org/repos/asf/incubator/kafka/trunk@r1181186
>
> Shouldn't 0.7 be in branches or tags? Once the vote goes through the
> project will be stuck with kafka/0.7. Is this what you guys want?
>
>
> Regards,
> Alan
>
>
Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by "Alan D. Cabrera" <ad...@toolazydogs.com>.
On Oct 17, 2011, at 10:45 AM, Neha Narkhede wrote:
> Hi,
>
> This is the fourth candidate for the first incubator release for
> Apache Kafka, version 0.7.0-incubating.
> There are *no* code changes since candidate 3. This candidate is
> published to follow the updated release
> process for Kafka.
>
> It fixes the following issues:
> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/RELEASE-NOTES.html
>
> *** Please download, test and vote by Oct, 20th, 10 am
>
> Note that we are voting upon the source (revision), binaries are
> provided for convenience.
Since this is a _source_ release I'm not sure there should be binaries, e.g. kafka-*.jar, *.class, files in the distribution. The d/l is 50M. Up to you guys.
> Source and binary files:
> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/
>
> The SVN revision to be voted upon:
> https://svn.apache.org/repos/asf/incubator/kafka/0.7@1185297
I thought the plan was to vote off of trunk, e.g.
> 5. Specify the NEW svn revision to be voted upon. For example,
> http://svn.apache.org/repos/asf/incubator/kafka/trunk@r1181186
Shouldn't 0.7 be in branches or tags? Once the vote goes through the project will be stuck with kafka/0.7. Is this what you guys want?
Regards,
Alan
Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by Neha Narkhede <ne...@gmail.com>.
And this one too - https://issues.apache.org/jira/browse/KAFKA-161
So -1, from me as well.
Thanks,
Neha
On Tue, Oct 18, 2011 at 2:52 PM, Jun Rao <ju...@gmail.com> wrote:
> The new issue is this one: https://issues.apache.org/jira/browse/KAFKA-160
>
> ---------- Forwarded message ----------
> From: Jun Rao <ju...@gmail.com>
> Date: Tue, Oct 18, 2011 at 2:52 PM
> Subject: Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
> To: kafka-dev@incubator.apache.org
>
>
> The new issue that we found seems like a blocker to me. So I am -1 on the
> vote.
>
> Jun
>
>
> On Mon, Oct 17, 2011 at 10:45 AM, Neha Narkhede <ne...@gmail.com>wrote:
>
>> Hi,
>>
>> This is the fourth candidate for the first incubator release for
>> Apache Kafka, version 0.7.0-incubating.
>> There are *no* code changes since candidate 3. This candidate is
>> published to follow the updated release
>> process for Kafka.
>>
>> It fixes the following issues:
>>
>> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/RELEASE-NOTES.html
>>
>> *** Please download, test and vote by Oct, 20th, 10 am
>>
>> Note that we are voting upon the source (revision), binaries are
>> provided for convenience.
>>
>> Source and binary files:
>> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/
>>
>> The SVN revision to be voted upon:
>> https://svn.apache.org/repos/asf/incubator/kafka/0.7@1185297
>>
>> Kafka's KEYS file containing PGP keys we use to sign the release:
>> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>>
>> Note that the Incubator PMC needs to vote upon the release after a
>> successful PPMC vote before
>> any release can be made official.
>>
>> Thanks,
>> Neha
>>
>
Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by Neha Narkhede <ne...@gmail.com>.
And this one too - https://issues.apache.org/jira/browse/KAFKA-161
So -1, from me as well.
Thanks,
Neha
On Tue, Oct 18, 2011 at 2:52 PM, Jun Rao <ju...@gmail.com> wrote:
> The new issue is this one: https://issues.apache.org/jira/browse/KAFKA-160
>
> ---------- Forwarded message ----------
> From: Jun Rao <ju...@gmail.com>
> Date: Tue, Oct 18, 2011 at 2:52 PM
> Subject: Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
> To: kafka-dev@incubator.apache.org
>
>
> The new issue that we found seems like a blocker to me. So I am -1 on the
> vote.
>
> Jun
>
>
> On Mon, Oct 17, 2011 at 10:45 AM, Neha Narkhede <ne...@gmail.com>wrote:
>
>> Hi,
>>
>> This is the fourth candidate for the first incubator release for
>> Apache Kafka, version 0.7.0-incubating.
>> There are *no* code changes since candidate 3. This candidate is
>> published to follow the updated release
>> process for Kafka.
>>
>> It fixes the following issues:
>>
>> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/RELEASE-NOTES.html
>>
>> *** Please download, test and vote by Oct, 20th, 10 am
>>
>> Note that we are voting upon the source (revision), binaries are
>> provided for convenience.
>>
>> Source and binary files:
>> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/
>>
>> The SVN revision to be voted upon:
>> https://svn.apache.org/repos/asf/incubator/kafka/0.7@1185297
>>
>> Kafka's KEYS file containing PGP keys we use to sign the release:
>> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>>
>> Note that the Incubator PMC needs to vote upon the release after a
>> successful PPMC vote before
>> any release can be made official.
>>
>> Thanks,
>> Neha
>>
>
Fwd: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by Jun Rao <ju...@gmail.com>.
The new issue is this one: https://issues.apache.org/jira/browse/KAFKA-160
---------- Forwarded message ----------
From: Jun Rao <ju...@gmail.com>
Date: Tue, Oct 18, 2011 at 2:52 PM
Subject: Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
To: kafka-dev@incubator.apache.org
The new issue that we found seems like a blocker to me. So I am -1 on the
vote.
Jun
On Mon, Oct 17, 2011 at 10:45 AM, Neha Narkhede <ne...@gmail.com>wrote:
> Hi,
>
> This is the fourth candidate for the first incubator release for
> Apache Kafka, version 0.7.0-incubating.
> There are *no* code changes since candidate 3. This candidate is
> published to follow the updated release
> process for Kafka.
>
> It fixes the following issues:
>
> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/RELEASE-NOTES.html
>
> *** Please download, test and vote by Oct, 20th, 10 am
>
> Note that we are voting upon the source (revision), binaries are
> provided for convenience.
>
> Source and binary files:
> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/
>
> The SVN revision to be voted upon:
> https://svn.apache.org/repos/asf/incubator/kafka/0.7@1185297
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>
> Note that the Incubator PMC needs to vote upon the release after a
> successful PPMC vote before
> any release can be made official.
>
> Thanks,
> Neha
>
Fwd: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by Jun Rao <ju...@gmail.com>.
The new issue is this one: https://issues.apache.org/jira/browse/KAFKA-160
---------- Forwarded message ----------
From: Jun Rao <ju...@gmail.com>
Date: Tue, Oct 18, 2011 at 2:52 PM
Subject: Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
To: kafka-dev@incubator.apache.org
The new issue that we found seems like a blocker to me. So I am -1 on the
vote.
Jun
On Mon, Oct 17, 2011 at 10:45 AM, Neha Narkhede <ne...@gmail.com>wrote:
> Hi,
>
> This is the fourth candidate for the first incubator release for
> Apache Kafka, version 0.7.0-incubating.
> There are *no* code changes since candidate 3. This candidate is
> published to follow the updated release
> process for Kafka.
>
> It fixes the following issues:
>
> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/RELEASE-NOTES.html
>
> *** Please download, test and vote by Oct, 20th, 10 am
>
> Note that we are voting upon the source (revision), binaries are
> provided for convenience.
>
> Source and binary files:
> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/
>
> The SVN revision to be voted upon:
> https://svn.apache.org/repos/asf/incubator/kafka/0.7@1185297
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>
> Note that the Incubator PMC needs to vote upon the release after a
> successful PPMC vote before
> any release can be made official.
>
> Thanks,
> Neha
>
Re: [VOTE] Release Kafka 0.7.0-incubating (candidate 4)
Posted by Jun Rao <ju...@gmail.com>.
The new issue that we found seems like a blocker to me. So I am -1 on the
vote.
Jun
On Mon, Oct 17, 2011 at 10:45 AM, Neha Narkhede <ne...@gmail.com>wrote:
> Hi,
>
> This is the fourth candidate for the first incubator release for
> Apache Kafka, version 0.7.0-incubating.
> There are *no* code changes since candidate 3. This candidate is
> published to follow the updated release
> process for Kafka.
>
> It fixes the following issues:
>
> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/RELEASE-NOTES.html
>
> *** Please download, test and vote by Oct, 20th, 10 am
>
> Note that we are voting upon the source (revision), binaries are
> provided for convenience.
>
> Source and binary files:
> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-4/
>
> The SVN revision to be voted upon:
> https://svn.apache.org/repos/asf/incubator/kafka/0.7@1185297
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/kafka/KEYS
>
> Note that the Incubator PMC needs to vote upon the release after a
> successful PPMC vote before
> any release can be made official.
>
> Thanks,
> Neha
>