On Oct 28, 2008, at 7:20 PM, Todd Zullinger wrote: > James Turnbull wrote: >> I am just adding a rake task to do the new CHANGELOG creation. I'd >> like some input on the format. I've basically done: >> >> Tue, 28 Oct 2008 14:12:36 +0100 >> Brice [EMAIL PROTECTED] >> Fix #1682 - ASTArray should flatten product of evaluation of its >> children >> >> Tue, 28 Oct 2008 17:13:31 -0500 >> Luke [EMAIL PROTECTED] >> Fixing #1667 - regex automatic value documentation is now readable. >> >> Tue, 28 Oct 2008 15:57:03 +1100 >> James [EMAIL PROTECTED] >> Fixed #1692 - k5login fails to set mode when file is created >> >> But it's highly customisable. What else would people expect/like? >> Hashes? The full commit? > > If completely changing the CHANGELOG format is an option, what about > just using "git log" output as is? That contains plenty of useful > information and gives anyone reading the ability to dig deeper since > it contains the commit sha1.
I'm actually concerned that there's going to be way too much information in the CHANGELOG unless we significantly trim both the number of commits and the length of comment. Either that, or people will be encouraged to either 1) ignore the changelog or 2) write terse commit logs and mash many commits into one. We've been working hard for the last year to get smaller commits, so each commit has a specific, documented purpose -- however, that mushrooms into *tons* of commit messages, and most of them are entirely uninteresting to non-developers. > >> The git log string is currently: >> >> git log --pretty=format:'%n%aD%n%an%ae%n%s' > > You'd want to add a space after the author name and some brackets > around the email address, to avoid output like: > > Luke [EMAIL PROTECTED] > > So, just tweaking your format options: > > git log --pretty=format:'%n%aD%n%an <%ae>%n%s' Sounds good to me. > > BTW, is it possible to run the tarball creation outside of > reductivelabs? The DevelopmentLifecycle page on the wiki leads me to > believe the answer is no, but if I am mistaken, I'd be happy to help > test the Rakefile changes. You should be able to install my build library (which, of course, sucks) from the reductive-build git repo on my github account, and then run: rake package I think you could also do 'rake pkg/puppet-0.24.6.tgz' and just get the tarball, or even 'rake pkg/puppet-0.24.6' to get the directory structure, but I haven't done those in a while. -- When I die, I want go out just like my grandfather, in his sleep, peaceful and quiet...not kicking and screaming like the other guys in his car. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
