Do we want to-do a 0.7.2 release and/or propose a freeze date for 0.8 ?

I am working on a new product that has 0.7.1 in it don't mind even
pushing 0.7.2 into or 0.8  and releasing both in succession.

//joestein

Joe,

Since 0.7.1, we have fixed 3-4 issues in trunk. The most critical fix is
probably the one that prevents wrong topic name from corrupting log and ZK
data structure. As for 0.8, I think we can start letting people trying the
code from mid to end of Oct. Depending on the result of that, we can decide
on a release date of 0.8.

For now, what we can probably do is to release 0.7.2 from trunk. After
that, we can move trunk to an 0.7 branch and make 0.8 trunk. What do people
feel?

Thanks,

Jun

On Thu, Sep 13, 2012 at 10:15 AM, Joe Stein <[EMAIL PROTECTED]> wrote:

> Do we want to-do a 0.7.2 release and/or propose a freeze date for 0.8 ?
>
> I am working on a new product that has 0.7.1 in it don't mind even
> pushing 0.7.2 into or 0.8  and releasing both in succession.
>
> //joestein
>

>
> Since 0.7.1, we have fixed 3-4 issues in trunk. The most critical fix is
> probably the one that prevents wrong topic name from corrupting log and ZK
> data structure. As for 0.8, I think we can start letting people trying the
> code from mid to end of Oct. Depending on the result of that, we can decide
> on a release date of 0.8.
>

So ideally we should target all blockers in 0.8 to be done well before
mid-October. Just added a "blockers" section on
https://cwiki.apache.org/confluence/display/KAFKA/Kafka+replication+development
There
are > 30 right now so I think we
should be try to defer major code clean up (which we tend to do a lot in
our patches) to follow-up jiras.
> For now, what we can probably do is to release 0.7.2 from trunk. After
> that, we can move trunk to an 0.7 branch and make 0.8 trunk. What do people
> feel?
>

Sounds good to me.

Thanks,

Joel
> On Thu, Sep 13, 2012 at 10:15 AM, Joe Stein <[EMAIL PROTECTED]> wrote:
>
> > Do we want to-do a 0.7.2 release and/or propose a freeze date for 0.8 ?
> >
> > I am working on a new product that has 0.7.1 in it don't mind even
> > pushing 0.7.2 into or 0.8  and releasing both in succession.
> >
> > //joestein
> >
>

On 2012-09-13 13:15, Joe Stein wrote:
> I am working on a new product that has 0.7.1 in it don't mind even
> pushing 0.7.2 into or 0.8  and releasing both in succession.

Do yo want help with the mechanics of the release itself?

On a tangentially related note with regards to branches I think the git
migration (INFRA-5111) is now able to get some attention from the
infrastructure folks.

On Thu, Sep 13, 2012 at 10:35 PM, Chris Burroughs <[EMAIL PROTECTED]
> wrote:

> On 2012-09-13 13:15, Joe Stein wrote:
> > I am working on a new product that has 0.7.1 in it don't mind even
> > pushing 0.7.2 into or 0.8  and releasing both in succession.
>
> Do yo want help with the mechanics of the release itself?
>

That would be cool, I am still tardy in posting my notes to the release
JIRA ticket from 0.7.1 for changes to the docs, will do that soon.
>
> On a tangentially related note with regards to branches I think the git
> migration (INFRA-5111) is now able to get some attention from the
> infrastructure folks.
>

awesome, maybe we modify the docs for the 0.7.2 release to be all git based
then
--

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/