[LLVMdev] Release Notes: Volunteers needed

Chris Lattner clattner at apple.com
Thu Oct 27 23:48:52 PDT 2011

On Oct 27, 2011, at 11:19 PM, Carl-Philip Hänsch wrote:
> 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.

Ok, sure, it would be reasonable to automate the *next* release or just have people update the 3.1 release notes when they make major changes.  One issue is that the release notes are hacked on mainline for 3.0 now, so Dan Gohman can release note all the reaping he's been doing, for example.

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

More information about the llvm-dev mailing list