[LLVMdev] Release Notes: Volunteers needed

Carl-Philip Hänsch cphaensch at googlemail.com
Thu Oct 27 23:19:56 PDT 2011

2011/10/28 Chris Lattner <clattner at apple.com>

> On Oct 27, 2011, at 5:37 PM, Michael Price wrote:
> Has there been much thought of attempting to automate this process?  I
> could imagine a fairly standard script that scrubbed a history for
> interesting tidbits.  Of course a standard methodology for labeling types of
> commits would help this in the future.
> A very simple script could at least do unique word counts and throw out
> words that match a dictionary (like parts of speech, contributer names,
> etc.).  A more complex script could retain "links" back to the commits that
> contained certain words in case you wanted more information.
> Hi Michael,
> I don't see any reasonable way that this can be automated.  The script
> would either miss a bunch of really important things or get a ton of not
> very useful stuff.  I'm open to suggestions of course and proof to the
> contrary though! :-)
> -Chris

There is a way, but this method needs interaction of the deveoper. In mesa
project, they add a line "Note: This is a candidate for 7.10 branch" to the
commit message to automatically merge security fixes into older releases. In
LLVM, it could be something like "ReleaseNote: New type system that adds
more foo and removes some bar". For the current bunch of changes you are
right, you can't automate this very good. And once the list of ReleaseNotes
is extracted, a human can decide if these changes had really that fatal
significance to appear in the release notes.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111028/95165275/attachment.html>

More information about the llvm-dev mailing list