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 <stevengil...@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 <bows...@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 <stevengil...@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 <bows...@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 >> >> > >
