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. On Wed, Oct 26, 2011 at 2:02 PM, <cfe-dev-request at cs.uiuc.edu> wrote: Date: Wed, 26 Oct 2011 11:52:50 -0700> From: Tanya Lattner <lattner at apple.com> > Subject: [cfe-dev] Release Notes: Volunteers needed > To: "llvmdev at cs.uiuc.edu List" <llvmdev at cs.uiuc.edu> > Cc: clang-dev Developers <cfe-dev at cs.uiuc.edu> > Message-ID: <4B2469FD-7E09-46E2-9539-54937E811B6A at apple.com> > Content-Type: text/plain; charset="us-ascii" > > We need some volunteers to help with the 3.0 release notes. Traditionally, > Chris has been the one to go through all the commits (6 months worth!) and > come up with a concrete list of things that have changed in 3.0. Ideally, > its much better if this document is incrementally updated as well, but we > know how that goes. This is a huge amount of work and with the pace that > LLVM/Clang are being developed, its a big task and becoming too much for one > person. > > We need some volunteers from both the Clang and LLVM communities to help > with the release notes. This would involve going through the commits (on > both LLVM and Clang side) and coming up with the list of features/important > changes. Please send mail to me if you are interested in helping. The time > frame for this would be end of Phase 2 testing (November 6th). Chris would > of course be helping review this and give suggestions on how to go about > this task. It may be also worthwhile to start a separate Clang release > notes.. > > Thanks, > Tanya >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111027/2dbbc3fe/attachment.html>
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> > > On Wed, Oct 26, 2011 at 2:02 PM, <cfe-dev-request at cs.uiuc.edu> wrote: > > Date: Wed, 26 Oct 2011 11:52:50 -0700 > From: Tanya Lattner <lattner at apple.com> > Subject: [cfe-dev] Release Notes: Volunteers needed > To: "llvmdev at cs.uiuc.edu List" <llvmdev at cs.uiuc.edu> > Cc: clang-dev Developers <cfe-dev at cs.uiuc.edu> > Message-ID: <4B2469FD-7E09-46E2-9539-54937E811B6A at apple.com> > Content-Type: text/plain; charset="us-ascii" > > We need some volunteers to help with the 3.0 release notes. Traditionally, Chris has been the one to go through all the commits (6 months worth!) and come up with a concrete list of things that have changed in 3.0. Ideally, its much better if this document is incrementally updated as well, but we know how that goes. This is a huge amount of work and with the pace that LLVM/Clang are being developed, its a big task and becoming too much for one person. > > We need some volunteers from both the Clang and LLVM communities to help with the release notes. This would involve going through the commits (on both LLVM and Clang side) and coming up with the list of features/important changes. Please send mail to me if you are interested in helping. The time frame for this would be end of Phase 2 testing (November 6th). Chris would of course be helping review this and give suggestions on how to go about this task. It may be also worthwhile to start a separate Clang release notes.. > > Thanks, > Tanya > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111027/b4591d65/attachment.html>
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. Carl-Philip -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111028/95165275/attachment.html>
I'm willing to volunteer. We're looking to move our integration from LLVM 2.8 to 3.0, and so I'll be doing some of this anyway. Cheers, Joe Abbey Software Architect Arxan Technologies, Inc. 1305 Cumberland Ave, Ste 215 West Lafayette, IN 47906 jabbey at arxan.com<mailto:jabbey at arxan.com> www.arxan.com On Wed, Oct 26, 2011 at 2:02 PM, <cfe-dev-request at cs.uiuc.edu<mailto:cfe-dev-request at cs.uiuc.edu>> wrote: Date: Wed, 26 Oct 2011 11:52:50 -0700 From: Tanya Lattner <lattner at apple.com<mailto:lattner at apple.com>> Subject: [cfe-dev] Release Notes: Volunteers needed To: "llvmdev at cs.uiuc.edu<mailto:llvmdev at cs.uiuc.edu> List" <llvmdev at cs.uiuc.edu<mailto:llvmdev at cs.uiuc.edu>> Cc: clang-dev Developers <cfe-dev at cs.uiuc.edu<mailto:cfe-dev at cs.uiuc.edu>> Message-ID: <4B2469FD-7E09-46E2-9539-54937E811B6A at apple.com<mailto:4B2469FD-7E09-46E2-9539-54937E811B6A at apple.com>> Content-Type: text/plain; charset="us-ascii" We need some volunteers to help with the 3.0 release notes. Traditionally, Chris has been the one to go through all the commits (6 months worth!) and come up with a concrete list of things that have changed in 3.0. Ideally, its much better if this document is incrementally updated as well, but we know how that goes. This is a huge amount of work and with the pace that LLVM/Clang are being developed, its a big task and becoming too much for one person. We need some volunteers from both the Clang and LLVM communities to help with the release notes. This would involve going through the commits (on both LLVM and Clang side) and coming up with the list of features/important changes. Please send mail to me if you are interested in helping. The time frame for this would be end of Phase 2 testing (November 6th). Chris would of course be helping review this and give suggestions on how to go about this task. It may be also worthwhile to start a separate Clang release notes.. Thanks, Tanya _______________________________________________ LLVM Developers mailing list LLVMdev at cs.uiuc.edu<mailto:LLVMdev at cs.uiuc.edu> http://llvm.cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111028/723bd733/attachment.html>