cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <agri...@chromium.org>
Subject Re: RELEASENOTES.md and coho
Date Wed, 11 Dec 2013 15:10:19 GMT
I'll write them for Android if it's annoying for you. I really don't think
it's feasible for one person to make sense of all commit messages across
all platforms.

On Wed, Dec 11, 2013 at 10:02 AM, Joe Bowser <bowserj@gmail.com> wrote:

> On Wed, Dec 11, 2013 at 6:53 AM, Andrew Grieve <agrieve@chromium.org>
> wrote:
> > Release notes:
> > - Keep people engaged in reading about Cordova
> > - Make people want the new thing
> >
> > I think the best way to communicate release notes is to do it within the
> > release blog posts.
> >
> > The release blog post is much much easier to write if there's already a
> > list of release notes to draw from.
> >
>
> I don't know why the person writing the blog post can't go off the
> commit logs.  This shouldn't be tied to the release, and I feel that
> this is unnecessary cruft that only serves a marketing purpose, and
> not a technical one.  Our average release has less than 50 commits, I
> don't really think it's appropriate to curate these commits,
> especially since I have a different opinion about which commits are
> important to curate than other people.  I really wish this was never
> added to our release process, and I really would like to see this file
> go away.
>
>
> >
> >
> > On Tue, Dec 10, 2013 at 7:35 PM, Brian LeRoux <b@brian.io> wrote:
> >
> >> I'm -1 on duplication of git log in a text file too. Unnecessary cruft.
> >> On Dec 11, 2013 9:03 AM, "Joe Bowser" <bowserj@gmail.com> wrote:
> >>
> >> > Honestly, I would rather have the log have all the commits but still
> >> > exist as opposed to not existing, which is what happened with 3.2.0.
> >> > I think that having this RELEASENOTES.md file slows down the release
> >> > process a LOT and there's very little gain except for people who can't
> >> > read a git log.
> >> >
> >> > On Tue, Dec 10, 2013 at 2:49 PM, Steven Gill <stevengill97@gmail.com>
> >> > wrote:
> >> > > It can be automated, but the output should be manually looked over
> to
> >> > remove
> >> > > commits that don't need to be in the release notes and blog posts
> >> > >
> >> > >
> >> > > On Tue, Dec 10, 2013 at 2:45 PM, Joe Bowser <bowserj@gmail.com>
> wrote:
> >> > >>
> >> > >> OK, I'm filing a ticket because THIS should be automated.  This
is
> way
> >> > >> trickier than just tagging something.
> >> > >>
> >> > >> On Tue, Dec 10, 2013 at 2:31 PM, Steven Gill <
> stevengill97@gmail.com>
> >> > >> wrote:
> >> > >> > Hey Joe,
> >> > >> >
> >> > >> > Check out Documentation to Update section at
> >> > >> > http://wiki.apache.org/cordova/CuttingReleases
> >> > >> >
> >> > >> > Pretty much
> >> > >> >
> >> > >> > git log --pretty=format:'* %s' --topo-order --no-merges
> >> > >> > origin/RELEASE_BRANCH..master >> RELEASENOTES.md
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >> > On Tue, Dec 10, 2013 at 2:15 PM, Joe Bowser <bowserj@gmail.com>
> >> > wrote:
> >> > >> >
> >> > >> >> Hey
> >> > >> >>
> >> > >> >> How are the RELEASENOTES.md get authored? Where do the
author
> >> counts
> >> > >> >> come from?  I could do this by hand, but this doesn't
look like
> >> they
> >> > >> >> were.  Is this documented anywhere?
> >> > >> >>
> >> > >> >> Joe
> >> > >> >>
> >> > >
> >> > >
> >> >
> >>
>

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