falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Srikanth Sundarrajan <srik...@hotmail.com>
Subject RE: Democratizing Release Notes
Date Tue, 30 Aug 2016 11:38:57 GMT
Agreed. This improvement can further make the release process smoother. Should definitely help
in maintaining release cadence.
RegardsSrikanth Sundarrajan

> From: sandysmdl@gmail.com
> Date: Tue, 30 Aug 2016 14:19:44 +0530
> Subject: Re: Democratizing Release Notes
> To: dev@falcon.apache.org
> 
> +1. Agree with Pallavi and Ajay. Only important updates should be go into
> release notes so that the list is not huge and easily readable.
> 
> On Tue, Aug 30, 2016 at 2:16 PM, Pallavi Rao <pallavi.rao@inmobi.com> wrote:
> 
> > This is nice!
> >
> > Don't think we can mandate that field as not all JIRAs will need an entry
> > in Release Notes. Examples are falcon regression test suite updates, UT
> > changes, documentation updates, bugs reported that turn out to be usage
> > issues.
> >
> > On Tue, Aug 30, 2016 at 2:09 PM, Srikanth Sundarrajan <sriksun@hotmail.com
> > >
> > wrote:
> >
> > > +1. Would it help if we made the release notes field mandatory for
> > marking
> > > the jira closed ?
> > > RegardsSrikanth Sundarrajan
> > >
> > > > From: ajayyadava@apache.org
> > > > Date: Tue, 30 Aug 2016 08:35:50 +0000
> > > > Subject: Democratizing Release Notes
> > > > To: dev@falcon.apache.org
> > > >
> > > > Hello everyone,
> > > >
> > > > Continuing on our effort to automating change log and release notes, I
> > am
> > > > happy to share with you that we now have the ability to automatically
> > > > generate release notes through Apache Yetus.
> > > >
> > > > *How does it work?*
> > > > We have introduced a new field in JIRA - Release Notes. Every
> > contributor
> > > > needs to add release notes for their important / backward-incompatible
> > > > changes / new features. Later, RMs can generate release notes using
> > > Apache
> > > > Yetus. Many projects like Hadoop etc. have already been doing it this
> > > way.
> > > > We have also been using Apache Yetus to generate the release notes
> > > >
> > > > *Why?*
> > > > Generating release notes had been one tedious task which the
> > RMs(Release
> > > > Managers) had to do manually at the end of the release by going through
> > > all
> > > > JIRAs and writing notes for them. Often, RM may not even be the best
> > > person
> > > > to write release notes for the feature.
> > > >
> > > > *Note to Contributors*
> > > > Please add release notes for any important / backward-incompatible
> > > changes
> > > > / new features that you add.
> > > >
> > > > *Note to Committers*
> > > > Please don't commit PRs for important / backward-incompatible changes
/
> > > new
> > > > features without release notes.
> > > >
> > > > I will update the "how to release" wiki with the steps for RMs, In the
> > > > meantime, you can consult the documentation for Apache Yetus here
> > > > <https://yetus.apache.org/documentation/0.3.0/>
> > > >
> > > > Regards
> > > > Ajay Yadava
> > >
> > >
> >
> > --
> > _____________________________________________________________
> > The information contained in this communication is intended solely for the
> > use of the individual or entity to whom it is addressed and others
> > authorized to receive it. It may contain confidential or legally privileged
> > information. If you are not the intended recipient you are hereby notified
> > that any disclosure, copying, distribution or taking any action in reliance
> > on the contents of this information is strictly prohibited and may be
> > unlawful. If you have received this communication in error, please notify
> > us immediately by responding to this email and then delete it from your
> > system. The firm is neither liable for the proper and complete transmission
> > of the information contained in this communication nor for any delay in its
> > receipt.
> >
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message