tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bikas Saha <bi...@hortonworks.com>
Subject RE: Looking ahead to 0.6
Date Tue, 18 Nov 2014 19:05:41 GMT
Thanks Hitesh. That's a good way to share and increase visibility.

Assuming that everyone is implicitly agreeing with the plan below :) I
will go ahead and roll the remaining bug fixes into 0.5.3.

Committers, please ensure that branch-0.5 has the changes you want and
vice versa does not have changes that may have been inadvertently
committed during a merge by someone else :)

Thanks!
Bikas

-----Original Message-----
From: Hitesh Shah [mailto:hitesh@apache.org]
Sent: Friday, November 14, 2014 2:46 PM
To: dev@tez.apache.org
Subject: Re: Looking ahead to 0.6

I created a https://cwiki.apache.org/confluence/display/TEZ/Roadmap wiki
with some very minimal information based on what I perceive 0.6.0.

We can use this to track what high level features we want to target in
upcoming releases.

thanks
- Hitesh


On Nov 13, 2014, at 4:03 PM, Bikas Saha <bikas@hortonworks.com> wrote:

> Folks,
>
>
>
> The TEZ-8 branch is progressing nicely on the UI front. Since it a
> highly requested feature it would make sense to rally the next release
> (0.6) around this feature and other tooling developments. To that end
> we could try to make a 0.6 release soon after TEZ-8 gets merged into
> trunk. This will provide users with a proper Tez release to play
> around with the UI. We can then iterate on the UI in 0.6 train of
releases based on user feedback.
>
>
>
> In order to focus on the 0.6 release, we should probably stop further
> work on the 0.5 release. 0.5 was the API stability release with a lot
> of code change and we have worked through the ensuing bugs and missing
> artifacts via 0.5.1 and 0.5.2. I propose that we wrap up any remaining
> jiras for
> 0.5.3 and merge them to branch-0.5 soon. Then do a 0.5.3 release and
> move on to 0.6.
>
>
>
> If the above sounds good, the folks should mark jiras for 0.5.3 where
> applicable. Also, if any changes from master should go to branch-0.5
> then please merge them. Conversely, if anything has made its way to
> branch-0.5 and should not be there then please revert that change.
>
>
>
> Thoughts
>
> Bikas
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or
> entity to which it is addressed and may contain information that is
> confidential, privileged and exempt from disclosure under applicable
> law. If the reader of this message is not the intended recipient, you
> are hereby notified that any printing, copying, dissemination,
> distribution, disclosure or forwarding of this communication is
> strictly prohibited. If you have received this communication in error,
> please contact the sender immediately and delete it from your system.
Thank You.

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Mime
View raw message