Generate release notes with log4j-changelog - #477
Merged
Conversation
Convert the 16 releases from the JIRA-generated release pages into `src/changelog`, one XML entry per JIRA issue, so the release notes are generated by `log4j-changelog` like in the other Logging Services projects. Release dates come from the JIRA project metadata and the per-release introduction is kept in each release template. The `.2.x.x` directory distills the commit history since 1.11.0: components moved to satellite repositories, the Java 17 and Log4j API migrations, the slimmed-down `flume-ng-core` dependencies and the user-facing fixes. Changes to components that were later moved out of this repository are left to the changelogs of their new homes. Assisted-By: Claude Fable 5 <noreply@anthropic.com>
The hand-maintained pages under `releases/` duplicate what `log4j-changelog` now generates. The news page links now point to the per-version anchors of the generated page. Assisted-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Converts the release history to the
log4j-changelogformat used by the other Logging Services projects:src/site/antora/modules/ROOT/pages/releasesbecomesrc/changelog/<version>directories with one XML entry per JIRA issue (1171 entries); release dates come from the JIRA project metadata and the per-release introduction is preserved in each release template,src/changelog/.2.x.xdistills the commit history since 1.11.0 into changelog entries: components moved to satellite repositories, the Java 17 and Log4j API migrations, the slimmed-downflume-ng-coredependencies and the user-facing fixes. Changes to components that were later moved out of this repository are left to the changelogs of their new homes,log4j.changelog.skipproperty is removed, so thepre-sitephase exports the release notes pages into the Antora site.Overlaps with #475 only in the three shared FreeMarker templates, which are identical on both branches.
🤖 Generated with Claude Code