Hi Mark, FWIW, I make the date in changes.xml, the date I cut the release candidate so that it matches the RC tag creation date. If all goes well, the release tag is based on the same commit, so the date makes sense. A future date might make sense if it's the same date the announcement email goes out but that's "harder" to synchronize.
Gary On Wed, Nov 19, 2025, 10:26 <[email protected]> wrote: > This is an automated email from the ASF dual-hosted git repository. > > markt pushed a commit to branch master > in repository https://gitbox.apache.org/repos/asf/commons-daemon.git > > commit d53e76e1bdeead714736084b555392718a79740b > Author: Mark Thomas <[email protected]> > AuthorDate: Wed Nov 19 14:37:41 2025 +0000 > > Targeting a release in 7 days time (should be plenty of time). > --- > src/changes/changes.xml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/src/changes/changes.xml b/src/changes/changes.xml > index 6abb0f1..247d6e8 100644 > --- a/src/changes/changes.xml > +++ b/src/changes/changes.xml > @@ -40,7 +40,7 @@ > <title>Apache Commons Daemon Release Notes</title> > </properties> > <body> > - <release version="1.5.0" date="YYYY-MM-DD" description="This is a > maintenance release. Java 8 or later is required."> > + <release version="1.5.0" date="2025-11-26" description="This is a > maintenance release. Java 8 or later is required."> > <!-- FIX --> > <action type="fix" dev="ggregory" due-to="Gary Gregory">Remove > -nouses directive from maven-bundle-plugin. OSGi package imports now state > 'uses' definitions for package imports, this doesn't affect JPMS (from > org.apache.commons:commons-parent:80).</action> > <action type="fix" dev="michaelo">Document --enable-preview</action> > >
