AaronBallman wrote: > @AaronBallman You might know how to edit the template we reset back after > branching off each time. I suspect it's just a simple `git checkout` of the > release notes file at some specific commit. However, to have a similar fix > stick, we would need to interact folks doing this.
CC @tstellar @tru for help answering this but I think it might be this file? https://github.com/llvm/llvm-project/blob/main/clang/docs/ReleaseNotesTemplate.txt I think the changes here are a bit... awkward. These release notes are meant to be read by users and downstreams as much as by other developers, even while under active development. So the text is kind of out of place for those folks. Also, my experience has been that folks tend not to read the existing text in the file anyway, so they're just as likely to miss this new text as they are to miss the headings (particularly as the release notes get longer and so that text may be scrolled off screen for them). Another approach to solve this problem would be to remove the subcategories under the static analyzer heading so it's just a general list of changes to the static analyzer. Or to spread the static analyzer changes out among the other categories. WDYT about a reorganization of some kind instead of adding text like that? https://github.com/llvm/llvm-project/pull/175935 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
