From: Joel D. <jr...@pr...> - 2013-03-18 18:39:44
|
Lieven, I think a one line summary for each change is a better way to populate a changelog. How about folks write a 1 line summary at the top of each closed issue that could be grabbed to automatically build the changelog? Joel > Hi all, > > also, in preparation of the next release, I've prepared a changelog. > https://github.com/hollie/misterhouse/wiki/Changelog > > We could generate a changelog automatically based on the closed issues, > however, that would maybe too much detail. Would it be a good idea to keep > a list of one-liners describing the bug fixes and features we add? Then, > when we decide it is time for a new release, we simply have the changelog > ready. > > Kind regards, > Lieven. > > Op 17-mrt.-2013, om 19:30 heeft Joel Davidson <jr...@pr...> het > volgende geschreven: > >> On Sun, 17 Mar 2013, it would appear that Michael Stovenour wrote: >> >>> On Mar 17, 2013 4:40 AM Lieven wrote, >>>> >>>> I'd like to ask your opinion on this pull request: >>>> https://github.com/hollie/misterhouse/pull/123 >>>> >>>> OK to merge? I think keeping the version number in a single place >>>> helps in making new >>>> releases easier. Also, I propose to keep the version for the master >>>> branch to 'unstable' >>>> so that people know they are running the 'developer release' if they >>>> checkout master. >>> >>> I think it is a reasonable approach. >>> >>> Sincerely, >>> Michael >> >> Agreed. >> >> Joel |