ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Judes Sarmiento <jsarmie...@pivotal.io>
Subject Re: [DISCUSS] Development Process for New Major Features
Date Fri, 05 Sep 2014 16:53:46 GMT
+1

Thanks Yusaku


On Thu, Sep 4, 2014 at 8:24 PM, Siddharth Wagle <swagle@hortonworks.com>
wrote:

> +1, sounds good to me Yusaku.
>
>
> On Thu, Sep 4, 2014 at 7:35 PM, Yusaku Sako <yusaku@hortonworks.com>
> wrote:
>
> > Hi all Ambari Developers,
> >
> > In order to close the gap between the core developers of Ambari (who
> > typically have high-bandwidth communication amongst each other) and
> > the community in general of what's actually happening in Ambari as far
> > as new feature development goes, Ambari PMC has come up with the
> > following proposal on a new process that all Ambari developers are to
> > follow:
> >
> > Goals:
> > * Make it clear to the community of new feature development happening
> > at a high level
> > * Make it easier to correlate features with JIRAs
> > * Make it easier to track progress for features in development
> > * Make it easier to understand estimated release schedule for features
> > in development
> >
> > Process:
> > * Create a JIRA of type "Epic" for the new feature in Apache Ambari JIRA
> > * Add the feature to the Features + Roadmap wiki and link it to the Epic
> > created
> > * The Epic should contain a high-level description that is easy to
> > understand
> > * The Epic should also contain the initial, detailed design (this can
> > be in the form of a shared Google Doc for ease of collaboration, Word
> > doc, pdf, etc)
> > * Once the initial design is posted, announce to the dev mailing list
> > to elicit feedback.  It is recommended to ask for review feedback to
> > be given by a certain date so that the review process does not drag
> > on.
> > * Iterate on the design based on community feedback.  Incorporate
> > multiple review cycles as needed.
> > * Once the design is finalized, break it down into Tasks that are
> > linked to the Epic
> > * (Nice to have) Once the Tasks are defined, schedule them into
> > sprints using the Agile Board so that it's easy to see who is working
> > on what/when, what tasks remain but unassigned so the community can
> > pick up work from the backlog, etc.
> >
> > If anyone has any feedback on this process, please discuss on this
> thread.
> > We'll keep the discussion open for the next 72 hours.
> >
> > This is also documented as a wiki [1]
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/display/AMBARI/Development+Process+for+New+Major+Features
> >
> > Thanks,
> > Yusaku
> >
> > --
> > 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
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message