[logging-log4j2] 02/02: LOG4J2-3357 - use time trigger was scheduled to fire instead of current time.

[rg...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

rgoers pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git

commit e325de9abf771a4501bae7cd7910fcbce31f5663
Author: Ralph Goers <rg...@apache.org>
AuthorDate: Mon Jan 2 18:11:00 2023 -0700

    LOG4J2-3357 - use time trigger was scheduled to fire instead of current time.
---
 src/changes/changes.xml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index 48665a81b4..672feb51f3 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -29,7 +29,10 @@
          - "update" - Change
          - "remove" - Removed
     -->
-    <release version="2.19.1" date="TBD" description="GA Release 2.19.1">
+    <release version="2.20.0" date="TBD" description="GA Release 2.20.0">
+      <action issue="LOG4J2-3357" dev="rgoers" type="fix">
+        Use time trigger was expected to fire instead of current time.
+      </action>
       <action issue="LOG4J2-2297" dev="rgoers" type="fix">
         Allow java.sql.Time objects to format properly in MapMessages.
       </action>