Whatever the level of automation to generate the data, from fully manual to fully manual, such a page is better than looking over several months worth of commits to pick out features to add to a release announcement. Some things may be missed, some may get added in too much detail. Either way a human has a starting place to distill the data into information for a new release announcement.
Rick On Apr 7, 10:14 pm, Michael Harris <[email protected]> wrote: > 2009/4/8 Owen Winkler <[email protected]>: > > > > > > > Chris Meller wrote: > >> Just as it's not really practical to look down the list of commit > >> messages and quickly glean what was being done, I don't think it's > >> really feasible to expect everyone to "tag" their commits for the same > >> reasons: often it's a smaller part of a larger feature... should you > >> have to tag them all, tag what you think is the final, what? > > >> I suspect that anything like that would only ever be minimally useful > >> due to the patchy nature of usage. > > > Yeah, that's one reason why I created the wiki page. If you forget to > > add the feature in the commit log, even someone else could notice and > > add it to the wiki. > > > It might be useful to add an automated feature to the post-commit hook > > to look for things, but in the end that's just a tool to help the > > primary goal of listing high-level new features somewhere. > > Worthwhile features are also likely to be added over multiple commits > too. What commit added ACL ? :) > > -- > Michael C. Harris, School of CS&IT, RMIT > Universityhttp://twofishcreative.com/michael/blog > IRC: michaeltwofish #habari --~--~---------~--~----~------------~-------~--~----~ 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/habari-dev -~----------~----~----~----~------~----~------~--~---
