Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # dev >> RC3 status

Copy link to this message
Re: RC3 status
Alan, that makes sense.

Let me suggest we do a 0.7.2 release later in July.  I will volunteer to
manage that release also.

I would suggest having https://issues.apache.org/jira/browse/KAFKA-134 in
the release ( a lot of people , including myself, would like to see the
latest SBT and a clean 2.9.1 build ) at a minimum along with anything else
that we put into trunk by the time we cut 0.7.2 along with making sure we
have a binary release along with the source release.  We will have to (I
will open a JIRA for this too) make sure we document the dependencies that
are transitive that are going to show up in that binary distribution (which
will be like 50MB) .  I would be happy to take that on also but will have
some questions will move that convo to the ticket once created.

On Mon, Jun 25, 2012 at 10:51 AM, Alan D. Cabrera <[EMAIL PROTECTED]>wrote:

> On Jun 25, 2012, at 7:36 AM, Joe Stein wrote:
> > I looked into the Maven Repositories (read through our existing JIRA on
> it
> > which seem to be a Sonays issues)
> >
> > Any reason to not use Apache's Maven Repo?
> > http://www.apache.org/dev/publishing-maven-artifacts.html ?  I will
> open a
> > infrastructure ticket on this later today and see about getting this
> > through the next set of flaming rings.
> As I mentioned in the other email, I think that the artifacts needed to be
> voted upon along w/ the source.  That's what's usually done.  My
> understanding is that there would be a record that jars with specific
> signatures and hashes were vetted and voted upon.
> Regards,
> Alan

Joe Stein
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>