At this point we have all the planned feature work for the first milestone of the Tez UI feature checked into the TEZ-8 branch. At this point, I agree with you it is time to propose to merge these changes back into master. I will start a VOTE thread shortly to get that process moving forward.
On Thu, Dec 4, 2014 at 3:22 PM, Bikas Saha <bi...@hortonworks.com> wrote: > @Jonathan and other folks active on TEZ-8. Do you guys think its close > being merged back to master and then cut into a 0.6.0 release? When do you > think we would be ready for that? > > Related, perhaps one of the active members of TEZ-8 should take over as > Release Manager for 0.6 line since its going to be a UI dominated release > and you can make better judgment calls about when to make patch releases > on that line. > > Thanks > Bikas > > -----Original Message----- > From: Hitesh Shah [mailto:hit...@apache.org] > Sent: Tuesday, November 18, 2014 2:58 PM > To: dev@tez.apache.org > Subject: Re: Looking ahead to 0.6 > > Looks like we have a minimal list setup for 0.6. Would be good to kick off > a discuss thread for 0.6.x and 0.7.x in general. > > Also, @Bikas, I am assuming you will be looking for a volunteer to take > over as the release manager for 0.6.x line ( unless you would like to > continue doing the releases )? > > - Hitesh > > On Nov 18, 2014, at 8:05 PM, Bikas Saha <bi...@hortonworks.com> wrote: > >> 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:hit...@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 <bi...@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. > > -- > 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.