>> 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 can pass on that for this release. We can start publishing to Maven after the next release. Seems like we are unblocked on voting for this RC then. Lets start the vote, the deadline is still Oct 18th, 6pm Thanks, Neha On Fri, Oct 14, 2011 at 11:37 AM, Alan D. Cabrera <l...@toolazydogs.com> wrote: > > On Oct 14, 2011, at 11:21 AM, Neha Narkhede wrote: > >> Alan, >> >> Thanks for looking into this. >> >>> The binary tgz should not be offered to assist in the review unless you're >>> going to publish it as well, i.e. provide it as a download. Signing it >>> will only make people think you're going to publish it. Not a showstopper. >>> Something to consider next time. >> >> Yes. We intend to publish the tgz too. That helps users run the >> quickstart and unit tests on a release quickly. I checked some other >> incubator projects and top-level Apache projects. They seemed to do >> the same. > > Yes, that's fine. Your statement "binaries are provided for convenience" is > what confused me. When a vote occurs all the artifacts and their signatures > that will be published should be provided for review. > >> >>> IIRC, the actual artifacts that get published to maven should also be >>> available to review. >>> http://www.apache.org/dev/publishing-maven-artifacts.html >> >> We actually haven't yet resolved >> https://issues.apache.org/jira/browse/KAFKA-133. From what you had >> mentioned, our understanding was that you have to wait for at least >> one release to be able to publish to a Maven repo. Do you think this >> blocks us ? > > If it's the intention of the project to publish Maven artifacts as part of > this release then they need to be provided following the guidelines outlined > in http://www.apache.org/dev/publishing-maven-artifacts.html. This means > that KAFKA-133 needs to be resolved before the vote. Maven artifacts cannot > be published after the fact even though they may be built from a tag. > > 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. > >>> Is kafka-0.7.0-incubating-candidate-3 the intended final tag? If not maybe >>> it should just be kafka-0.7.0-incubating. Once this goes out you can never >>> change it. >> >> I'm thinking that since RC3 and the release tag is the same, we can >> add the kafka-0.7.0-incubating tag and delete the >> kafka-0.7.0-incubating-candidate-3 tag. > > Simply moving the tag should be fine unless you want to pick up more stuff > from trunk. > > > Regards, > Alan > >> >> Let us know if this sounds good. >> >> Thanks, >> Neha >> >> On Thu, Oct 13, 2011 at 9:26 PM, Alan D. Cabrera <l...@toolazydogs.com> >> wrote: >>> The binary tgz should not be offered to assist in the review unless you're >>> going to publish it as well, i.e. provide it as a download. Signing it >>> will only make people think you're going to publish it. Not a showstopper. >>> Something to consider next time. >>> >>> IIRC, the actual artifacts that get published to maven should also be >>> available to review. >>> http://www.apache.org/dev/publishing-maven-artifacts.html >>> >>> Is kafka-0.7.0-incubating-candidate-3 the intended final tag? If not maybe >>> it should just be kafka-0.7.0-incubating. Once this goes out you can never >>> change it. >>> >>> >>> Regards, >>> Alan >>> >>> On Oct 13, 2011, at 6:54 PM, Neha Narkhede wrote: >>> >>>> 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-incubating-candidate-3/RELEASE-NOTES.html >>>> >>>> *** Please download, test and vote by noon Oct, 18th, 6 pm >>>> >>>> Note that we are voting upon the source (tag), binaries are provided >>>> for convenience. >>>> >>>> Source and binary files: >>>> http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-3/ >>>> >>>> The tag to be voted upon: >>>> http://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.0-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 >>>> >>>> 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 >>> >>> > >
