Hi Juan Pablo, agreed. The last ChangeLog.md and Release.java update was 2026-09-16 (3.0.1-git-02) and 25 PRs have been merged since. I have just pushed the backlog to master (BUILD bumped to git-03, one entry per issue with links and credits). For future batches, whoever merges them commits both files directly to master afterwards, which avoids conflicts in the first lines of ChangeLog.md.
cheers Arturo On Wed, Oct 28, 2026 at 10:47 PM Juan Pablo Santos Rodríguez < [email protected]> wrote: > Hi, > > This last days have seen a lot of code land into master, which is great :-) > May I ask to update Release.java and ChangeLog.md files? It's hard (for me) > to see in one glance what's being going on, and those two files are/were a > great way to track the project from a browser. > > Changelog.md for quick history (which automatically ends up at jspwiki.a.o) > and Release.java is a great way to pin where an issue is detected / solved > before a release. > > I get that commit history and/or jira store, more or less, the same > information, but jira requires login and the commit list isn't as > welcoming, they're more useful to me to see the details of a specific > issue. > > When working via PRs, updating those files is a bit of a PITA, so I've > always committed them directly into master when I was done with whatever > gets pushed. Don't know if there's an easier way, perhaps asking Claude or > whatever AI agent to update those files through a command? > > I'd like to keep having this info, but I'm also open to other alternatives. > WDYT? > > > cheers, > juan pablo >
