h-vetinari wrote: > should have a release note (perhaps on the release branch).
sidenote: updated release notes on the maintenance branches almost never get published (though they should). | Version | Last Patch Release | Release Notes (RN) exist | RN don't exist | RN for most recent<br/>patch release published? | |--------|--------|--------|--------|--------| | v21 | 21.1.4 (currently) |✅ [21.1.0](https://releases.llvm.org/21.1.0/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes)<br/>✅ [21.1.2](https://releases.llvm.org/21.1.2/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes) | ❌[21.1.1](https://releases.llvm.org/21.1.1/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes)<br/>❌[21.1.3](https://releases.llvm.org/21.1.3/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes)<br/>❌[21.1.4](https://releases.llvm.org/21.1.4/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes) | ❌ | | v20 | 20.1.8 | ✅ [20.1.0](https://releases.llvm.org/20.1.0/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes) | ❌[20.1.1](https://releases.llvm.org/20.1.1/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes) and onward | ❌ | | v19 | 19.1.7 | ✅ [19.1.0](https://releases.llvm.org/19.1.0/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes) | ❌[19.1.1](https://releases.llvm.org/19.1.1/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes) and onward | ❌ | | v18 | 18.1.8 | ✅ [18.1.0](https://releases.llvm.org/18.1.0/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes)<br/>✅ [18.1.1](https://releases.llvm.org/18.1.1/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes)<br/>✅ [18.1.4](https://releases.llvm.org/18.1.4/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes)<br/>✅ [18.1.6](https://releases.llvm.org/18.1.6/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes)<br/>✅ [18.1.7](https://releases.llvm.org/18.1.7/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes)<br/>✅ [18.1.8](https://releases.llvm.org/18.1.8/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes) | ❌[18.1.2](https://releases.llvm.org/18.1.2/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes)<br/>❌[18.1.3](https://releases.llvm.org/18.1.3/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes)<br/>❌[18.1.5](https://releases.llvm.org/18.1.5/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes) | ✅ | | v17 | 17.0.6 | ✅ [17.0.1](https://releases.llvm.org/17.0.1/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes) | ❌ [17.0.0](https://releases.llvm.org/17.0.0/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes)<br/>❌ [17.0.2](https://releases.llvm.org/17.0.2/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes) and onward | ❌ | | v16 | 16.0.6 | ✅ [16.0.0](https://releases.llvm.org/16.0.0/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes) | ❌ [16.0.1](https://releases.llvm.org/16.0.1/tools/clang/docs/ReleaseNotes.html#potentially-breaking-changes) and onward | ❌ | It would help immensely if the release notes were built and published in an automated fashion per branch (some prior [discussion](https://discourse.llvm.org/t/improve-the-llvm-org-website-look-and-feel/76864/4?u=h-vetinari)), rather than being dependent on the availability and goodwill of the release managers. Though I realize this would be a big initial lift. https://github.com/llvm/llvm-project/pull/164654 _______________________________________________ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
