This is an automated email from the ASF dual-hosted git repository.
swebb2066 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/logging-log4cxx.git
The following commit(s) were added to refs/heads/master by this push:
new 5bbe6224 Bump version to 1.7.0 (#614)
5bbe6224 is described below
commit 5bbe6224101ca048392c758de0f0135dff5b476b
Author: Stephen Webb <[email protected]>
AuthorDate: Sat Mar 28 14:55:22 2026 +1100
Bump version to 1.7.0 (#614)
---
admin/release-review-instructions.md | 14 ++++-----
admin/releasing.md | 16 +++++-----
admin/staging.md | 16 +++++-----
src/cmake/projectVersionDetails.cmake | 2 +-
src/examples/cpp/MyApp-qt/CMakeLists.txt | 1 -
.../include/log4cxx/varia/fallbackerrorhandler.h | 1 +
src/site/markdown/change-report-gh.md | 35 ++++++++++++++++++----
7 files changed, 54 insertions(+), 31 deletions(-)
diff --git a/admin/release-review-instructions.md
b/admin/release-review-instructions.md
index 0ec7d155..2754f5ec 100644
--- a/admin/release-review-instructions.md
+++ b/admin/release-review-instructions.md
@@ -3,7 +3,7 @@ Reviewing a Log4cxx release
The review should confirm the uploaded source code is not corrupt and
is identical to the package generated by the Github action.
-The steps below use version 1.6.2 as an example.
+The steps below use version 1.7.0 as an example.
Prerequisites
----------
@@ -31,9 +31,9 @@ Steps
- Windows: `validate-release.ps1`
- Run the script
- Linux, MacOS:
- - `sh validate-release.sh 1.6.2`
+ - `sh validate-release.sh 1.7.0`
- Windows:
- - `.\validate-release.ps1 1.6.2`
+ - `.\validate-release.ps1 1.7.0`
- For success, the final output line needs to include:
- `100% tests passed, 0 tests failed out of 63`
1. Download the packaged release files from Github
@@ -48,16 +48,16 @@ Steps
- The browser will download the file `release_files.zip` onto your
system
1. Confirm the artifacts were sourced from Github using these commands
- Linux, MacOS (bash):
- - `cd /tmp/log4cxx-1.6.2`
+ - `cd /tmp/log4cxx-1.7.0`
- `unzip $HOME/Downloads/release_files.zip -d github`
- - `ARCHIVE=apache-log4cxx-1.6.2`
+ - `ARCHIVE=apache-log4cxx-1.7.0`
- `for TYPE in tar.gz zip; do`
- `diff {,github/}$ARCHIVE.$TYPE.sha512 && echo "$ARCHIVE.$TYPE.sha512:
OK"`
- `done`
- Windows (powershell):
- - `Set-Location -Path "${ENV:TEMP}\log4cxx-1.6.2"`
+ - `Set-Location -Path "${ENV:TEMP}\log4cxx-1.7.0"`
- `Expand-Archive -Path "${ENV:HOMEPATH}\Downloads\release_files.zip"
-DestinationPath "github"`
- - `$ARCHIVE="apache-log4cxx-1.6.2"`
+ - `$ARCHIVE="apache-log4cxx-1.7.0"`
- `foreach ($TYPE in @("tar.gz", "zip")) {`
- `` if (@(Get-Content -Path "$ARCHIVE.$TYPE.sha512")[0]` ``
- `-eq @(Get-Content -Path "github\$ARCHIVE.$TYPE.sha512")[0]) {`
diff --git a/admin/releasing.md b/admin/releasing.md
index c88d2ce6..a9c3aab3 100644
--- a/admin/releasing.md
+++ b/admin/releasing.md
@@ -2,7 +2,7 @@ Releasing a Log4cxx version
===================
This document lists the steps that must be performed to release Log4cxx
-using 1.6.2 as the example.
+using 1.7.0 as the example.
Prerequisites
----------
@@ -27,9 +27,9 @@ Steps
- `svn up log4cxx`
- `cd log4cxx`
- `svn delete *`
- - `mkdir 1.6.2`
- - `svn add 1.6.2`
- - `cd 1.6.2`
+ - `mkdir 1.7.0`
+ - `svn add 1.7.0`
+ - `cd 1.7.0`
1. Download the packaged release files from Github
- Open https://github.com/apache/logging-log4cxx/commits/v1.6.1-RC1 in
your web browser
- Click the green tick mark on the top commit
@@ -40,11 +40,11 @@ Steps
- The numbered steps will display
- Click the link next to `Artifact download URL:`
- The browser will download the file `release_files.zip` onto your
system
-1. Unpack the release files using these commands (with
`apache-dist-logging-dev/log4cxx/1.6.2` as the working directory)
+1. Unpack the release files using these commands (with
`apache-dist-logging-dev/log4cxx/1.7.0` as the working directory)
- `unzip "$HOME/Downloads/release_files.zip"`
-1. Send the new artifacts to svn (with `apache-dist-logging-dev/log4cxx/1.6.2`
as the working directory)
+1. Send the new artifacts to svn (with `apache-dist-logging-dev/log4cxx/1.7.0`
as the working directory)
- `svn add *`
- - `svn commit -m 'log4cxx 1.6.2'`
+ - `svn commit -m 'log4cxx 1.7.0'`
- check https://dist.apache.org/repos/dist/dev/logging/log4cxx
1. Raise a vote on the mailing list ([email protected])
- Using [this template](MailTemplate.txt)
@@ -54,7 +54,7 @@ Steps
- Using [this template](MailTemplate.Result.txt)
- Enter the name of each PMC member that voted
1. Get artifacts up to https://downloads.apache.org/logging/log4cxx/
- - `svn move -m "Release log4cxx 1.6.2"
https://dist.apache.org/repos/dist/dev/logging/log4cxx/1.6.2
https://dist.apache.org/repos/dist/release/logging/log4cxx/`
+ - `svn move -m "Release log4cxx 1.7.0"
https://dist.apache.org/repos/dist/dev/logging/log4cxx/1.7.0
https://dist.apache.org/repos/dist/release/logging/log4cxx/`
1. Tag the released version
- `git checkout v1.6.1-RC1`
- `git tag rel/v1.6.1`
diff --git a/admin/staging.md b/admin/staging.md
index f95b5000..b7274d3a 100644
--- a/admin/staging.md
+++ b/admin/staging.md
@@ -2,7 +2,7 @@ Updating the Log4cxx web site
===================
This document describes the steps used to update Log4cxx web site
-using 1.6.2 as an example Log4cxx version.
+using 1.7.0 as an example Log4cxx version.
Prerequisites
----------
@@ -23,9 +23,9 @@ Steps to update the Log4cxx web site
- `cd /tmp/log4cxx-site`
- `git checkout asf-staging`
1. Use the newly generated files for the web site documentation
- - `git rm -r 1.6.2`
- - `mv /tmp/build/src/site/html 1.6.2`
- - `git add 1.6.2`
+ - `git rm -r 1.7.0`
+ - `mv /tmp/build/src/site/html 1.7.0`
+ - `git add 1.7.0`
1. Push the `asf-staging` branch to Github and wait a bit
- `git commit -m "Improved the ... documentation"`
- `git push origin asf-staging`
@@ -45,18 +45,18 @@ Steps to add a new version to the Log4cxx web site
- `cd /tmp/log4cxx-site`
- `git checkout asf-staging`
1. Use the newly generated files for the web site documentation
- - `mv /tmp/build/src/site/html /tmp/log4cxx-site/1.6.2`
- - `git add 1.6.2`
+ - `mv /tmp/build/src/site/html /tmp/log4cxx-site/1.7.0`
+ - `git add 1.7.0`
1. Update the symbolic links in the base of the web site working directory
- `cd /tmp/log4cxx-site`
- `rm old_stable`
- `ln -s 1.6.0 old_stable`
- `git add old_stable`
1. Update `.htaccess` so the final `RewriteRule` redirects to the new version
- - `RewriteRule ^(.*)$ /log4cxx/1.6.2/$1 [R=temp,L]`
+ - `RewriteRule ^(.*)$ /log4cxx/1.7.0/$1 [R=temp,L]`
- `git add .htaccess`
1. Push the `asf-staging` branch to github and wait a bit
- - `git commit -m "Add the 1.6.2 documentation"`
+ - `git commit -m "Add the 1.7.0 documentation"`
- `git push origin asf-staging`
1. Check https://logging.staged.apache.org/log4cxx (after a minute or two)
- Are you seeing the new pages?
diff --git a/src/cmake/projectVersionDetails.cmake
b/src/cmake/projectVersionDetails.cmake
index f767eda0..e531f040 100644
--- a/src/cmake/projectVersionDetails.cmake
+++ b/src/cmake/projectVersionDetails.cmake
@@ -2,4 +2,4 @@
# setting the project version. The variable name must not
# clash with the log4cxx_VERSION* variables automatically
# defined by the project() command.
-set(log4cxx_VER 1.6.2.0)
+set(log4cxx_VER 1.7.0.0)
diff --git a/src/examples/cpp/MyApp-qt/CMakeLists.txt
b/src/examples/cpp/MyApp-qt/CMakeLists.txt
index 7400ff0e..f05ce386 100644
--- a/src/examples/cpp/MyApp-qt/CMakeLists.txt
+++ b/src/examples/cpp/MyApp-qt/CMakeLists.txt
@@ -20,7 +20,6 @@ project(MyApp LANGUAGES CXX)
# Find the required libraries
find_package(QT NAMES Qt6 Qt5 REQUIRED COMPONENTS Core)
find_package(Qt${QT_VERSION_MAJOR} REQUIRED COMPONENTS Core)
-find_package(log4cxx REQUIRED)
find_package(log4cxx COMPONENTS qt REQUIRED)
# Optionally locate fmt::fmt
find_package(fmt QUIET)
diff --git a/src/main/include/log4cxx/varia/fallbackerrorhandler.h
b/src/main/include/log4cxx/varia/fallbackerrorhandler.h
index 3fcf9f0d..c3dfce6a 100644
--- a/src/main/include/log4cxx/varia/fallbackerrorhandler.h
+++ b/src/main/include/log4cxx/varia/fallbackerrorhandler.h
@@ -37,6 +37,7 @@ whatever reason.
logged in the new secondary appender.
Here is a sample configuration file that installs this error handler:
+\anchor fallback-ref-example
\include async-fall-back-example.xml
*/
class LOG4CXX_EXPORT FallbackErrorHandler :
diff --git a/src/site/markdown/change-report-gh.md
b/src/site/markdown/change-report-gh.md
index 2dc5eea5..52bc740e 100644
--- a/src/site/markdown/change-report-gh.md
+++ b/src/site/markdown/change-report-gh.md
@@ -25,7 +25,7 @@ Change Log {#changelog}
| Version | Date | Description |
| ------------------- | ---------- | -------------------- |
-| [1.6.2](#rel_1_6_2) | 2026-XX-XX | Bugfix release |
+| [1.7.0](#rel_1_7_0) | 2026-XX-XX | Maintenance release |
| [1.6.1](#rel_1_6_1) | 2026-01-09 | Bugfix release |
| [1.6.0](#rel_1_6_0) | 2025-12-14 | Maintenance release |
| [1.5.0](#rel_1_5_0) | 2025-08-03 | Maintenance release |
@@ -52,11 +52,34 @@ Change Log {#changelog}
| [0.1.0](#rel_1_0) | 2003-07-08 | |
| [0.0.1](#rel_0_1) | 2003-05-31 | |
-## Release 1.6.2 - 2026-XX-XX {#rel_1_6_2}
-This is a minor bugfix release to fix issues found with 1.6.1.
+## Release 1.7.0 - 2026-XX-XX {#rel_1_7_0}
-### Bug {#rel_1_6_2_bugs}
+Release 1.7.0 includes the following new features:
+
+* Support for a 'fallback-ref' attribute in the 'appender-ref' element of a
configuration file (see \ref fallback-ref-example)
+ \[[#606](https://github.com/apache/logging-log4cxx/pull/606)\]
+
+* Qt support can be enabled using a Log4cxx CMake find_package component (see
\ref MyApp-qt/CMakeLists.txt)
+ \[[#600](https://github.com/apache/logging-log4cxx/pull/600)\]
+
+* A TelnetAppender option (NonBlocking) to close the connection when the
network buffer is full
+ \[[#591](https://github.com/apache/logging-log4cxx/pull/591)\]
+
+The following issues have been addressed:
+
+* XML output could contain characters not allowed by the XML 1.0 specification
+ * [#609](https://github.com/apache/logging-log4cxx/pull/609)
+ , [#610](https://github.com/apache/logging-log4cxx/pull/610)
+
+* An XML configuration file with recursive references caused program
termination
+ \[[#605](https://github.com/apache/logging-log4cxx/pull/605)\]
+
+* Possible undefined behavior during a configuration change
+ \[[#601](https://github.com/apache/logging-log4cxx/pull/601)\]
+
+* Message loss when the calculation of a logged value also logs
+ \[[#594](https://github.com/apache/logging-log4cxx/pull/594)\]
* ODBCAppender prepared statement value buffers had incorrect lifetimes
\[[#581](https://github.com/apache/logging-log4cxx/pull/581)\]
@@ -87,8 +110,8 @@ and the LOG4CXX_CONFIGURATION environment variable (see
log4cxx::spi::Configurat
* Console output (Log4cxx internal logging and BasicConfigurator) use a color
per message level by default
\[[#529](https://github.com/apache/logging-log4cxx/pull/529)\]
* New logging macros that defer binary-to-text conversion until used in
AsyncAppender's background thread
- * \[[#548](https://github.com/apache/logging-log4cxx/pull/548)\]
- , \[[#554](https://github.com/apache/logging-log4cxx/pull/554)\]
+ * [#548](https://github.com/apache/logging-log4cxx/pull/548)
+ , [#554](https://github.com/apache/logging-log4cxx/pull/554)
* A simplified way to attach an AsyncAppender to a logger using a
configuration file
\[[#550](https://github.com/apache/logging-log4cxx/pull/550)\]
