Any combination of repository tweaks are valid as long as it's clear
what people are voting on. The signatures/etc. are helpful mechanisms
to ensure nobody is confused, but it's possible to get carried away.
You don't need to follow a specific incantation to generate a valid
release, as long as the
On 10/14/2011 03:44 PM, Alan D. Cabrera wrote:
> That's fine. What do others in the community think about this? Were
> they counting on a release of Maven artifacts as well? If that's
> what is everyone's understanding then the release should be good on
> this front.
My expectation was that mav
Chris,
>> In this case, the tarball unpacks to "kafka-0.7.0-incubating-candidate-3",
>> which is kind of unfortunate. Might as well clean that up.
I agree. In this case, we'd need to rename the directory as well,
which would change the MD5, so I guess that needs another vote.
Going forward, we
> The *contents* will contain the "-candidate-3". Not sure why the project
> would want that especially since you intend to rename the tag. Also, when
> you rename the tag there's no way to tell from the proposal that's being
> voted on that this is what happened.
As long as the signature and
On Oct 14, 2011, at 1:08 PM, Neha Narkhede wrote:
> Alan,
>
>>> Were you going to rebuild the tgz so that it did not have the candidate-3
>>> bit in its path? What about the rename of the tag? If you change any of
>>> these you need to restart the vote since this email is the record of what'
Alan,
>> Were you going to rebuild the tgz so that it did not have the candidate-3
>> bit in its path? What about the rename of the tag? If you change any of
>> these you need to restart the vote since this email is the record of what's
>> been voted on.
We intended to let people vote on the
On Oct 14, 2011, at 11:51 AM, Neha Narkhede wrote:
>>> To recap, all the artifacts that are going to be published as part of the
>>> release have to be provided for review. Artifacts cannot be published
>>> after the fact even though they may be built from a tag.
>
> So since KAFKA-133 is not
>> To recap, all the artifacts that are going to be published as part of the
>> release have to be provided for review. Artifacts cannot be published after
>> the fact even though they may be built from a tag.
So since KAFKA-133 is not yet resolved and will take quite some sbt
specific work, we
Hi,
This is the third candidate for the first incubator release for Apache
Kafka, version 0.7.0-incubating. This fixes ALL rat failures and also
adds a standard .rat-excludes
files along with rat scripts to Kafka.
It fixes the following issues:
http://people.apache.org/~nehanarkhede/kafka-0.7.0-i
