tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bikas Saha <bi...@hortonworks.com>
Subject RE: [DISCUSS] Creating a branch for TEZ-8
Date Thu, 18 Sep 2014 22:28:05 GMT
We don’t really have a concept of branch committers. But we are following
review then commit for non-trivial changes on master. On an earlier branch
we had followed commit then review to move fast. Maybe we could follow that
on this branch too since essentially we are branching to iterate quickly
without destabilizing master.

Bikas

-----Original Message-----
From: Jonathan Eagles [mailto:jeagles@gmail.com]
Sent: Thursday, September 18, 2014 3:08 PM
To: dev@tez.apache.org
Subject: Re: [DISCUSS] Creating a branch for TEZ-8

As a question of process for feature branches, do JIRAs being checked into
feature branches require +1 from committers, +1 from branch committers, or
no +1 at all?

On Mon, Sep 15, 2014 at 3:04 PM, Jonathan Eagles <jeagles@gmail.com> wrote:

> I am complete agreement with Bikas over the hindrance to users over
> the lack of a Tez UI. One of the focuses of the 0.5.0 release was the
> improvement to developers and the stabilization of APIs. Likewise, I
> would like to suggest one of the charters for the 0.6.0 release be the
> improvement to users and adopters -- addressing hindrances to tez:
> lack of a Tez UI with documentation to install, build, deploy, and
> configure this setup.
>
> To that end I propose we scope TEZ-8 such that it fits the 0.6.0
> release date and also that it becomes a blocker to that release. I can
> do a writeup of how to enable Tez UI as it works today so that the
> motivated user can use it in the current form.
>
> jeagles
>

-- 
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