+1 (binding)
ran some manual tests:
- verified sha256 for the binaries
- verified that log4j2 2.16 is used, and nothing else
- tested fresh deployment on tomcat 9 + postgres 14.1 + JDK 11 +
debian-slim-bullseye in a podman container
- repeated same test on JDK 17
- didn't test the migration logic with the release build, but I did that
back when it was implemented in master on my own blog (hsqldb, jetty, jdk17)
best regards,
michael
On 14.12.21 23:09, Dave wrote:
I propose that we release Roller v6.1.0 based on the code that is currently
in the master branch. I have prepared a release candidate and some release
notes, below.
Please vote in the next 72 hours to approve this release.
+1 to release
-1 not to release (with reasons)
Thanks to Michael Bien for all his work since the 6.0.1 release on bug
fixes, general improvements and dependency updates like the important one
he made today to upgrade Log4j.
The release candidate files are here:
https://dist.apache.org/repos/dist/dev/roller/roller-6.1/v6.1.0/
Release notes
This is a bug fix and dependency update release that includes all changes
made to the master branch since Dev 27, 2019. It also includes the new
patched Log4j release. This release should be a drop-in replacement of the
previous v6.0.1 release.
Here is a summary of the changes.
All Pull Requests that were merged since Dec 27, 2019
https://github.com/apache/roller/pulls?q=is%3Apr+is%3Aclosed+is%3Amerged
Bug resolved since Dec 27, 2019
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ROL%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20resolutiondate%20%3E%20%272019%2F12%2F27%27
And there is one database change: in the weblog table, the column blacklist
has been renamed to bannedwordslist.
