tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yingda Chen <ydc...@gmail.com>
Subject Re: Design doc for new feature?
Date Thu, 04 Oct 2018 22:19:40 GMT
Sounds good and Thanks Jon.  We have signed up for the dev mailing list,
and will be creating new JIRAs shortly. Lets go from there.

In the mean time, could you please add the following two accounts to the
contributors list first (we may have more folks join later as well)?



On Fri, Oct 5, 2018 at 4:40 AM Jonathan Eagles <jeagles@gmail.com> wrote:

> Welcome and thank you for reaching out, Yingda.
> Here is a sample of the process. Feel free to create a new JIRA for each
> feature. You can attach a design doc to the JIRA and request for comments
> on the dev list. After design discussions, usually the design takes one of
> two paths. For smaller projects, subtasks are added to the JIRA(umbrella)
> and are added in pieces. For larger projects, a feature branch is created
> and sub-jiras are committed directly to the feature branch and later merged
> back to the main line.
> As far as google doc link versus other formats, I feel this is ok as it
> does not require certain software to read and contribute to the design
> discussion. However, versioning and history of changes are part of a
> separate application as opposed to being stand alone in the JIRA. I'm ok
> with google doc as well as PDF.
> Please have a look at
> https://cwiki.apache.org/confluence/display/TEZ/How+to+Contribute+to+Tez
> for
> some process.
> Get signed up for tez development and let me know what apache jira account
> (others welcome as well) to add to the contributors list, so that you are
> able to assign jiras to yourself.
> Regards,
> Jon Eagles
> Tez PMC Chair
> On Thu, Oct 4, 2018 at 2:48 PM Yingda Chen <ydchen@gmail.com> wrote:
> > Hi all,
> >
> > We are interested in contributing a few new features to Tez and some of
> > these new features should ideally be preceded with design doc and
> > discussions.
> >
> >  Is JIRA (possibly with external Google Doc link) sufficient for that?
> >
> > Thanks all,
> > -Yingda
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message