This is an automated email from the ASF dual-hosted git repository.
ggregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-parent.git
commit a8a714ce05a25f6dbdfc5889a766cc231231364f
Author: Gary Gregory <garydgreg...@gmail.com>
AuthorDate: Sun Jul 21 18:19:26 2024 +0000
Prepare for the next release candidate
---
CONTRIBUTING.md | 9 ++++-----
README.md | 5 +++--
RELEASE-NOTES.txt | 41 +++++++++++++++++++++++++++++++++++++++++
pom.xml | 6 +++---
src/changes/changes.xml | 2 +-
5 files changed, 52 insertions(+), 11 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 87dd20e..3e0f57f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -41,9 +41,8 @@
Contributing to Apache Commons Parent
======================
-You have found a bug or you have an idea for a cool new feature? Contributing
code is a great way to give something back to
-the open source community. Before you dig right into the code there are a few
guidelines that we need contributors to
-follow so that we can have a chance of keeping on top of things.
+Have you found a bug or have an idea for a cool new feature? Contributing code
is a great way to give something back to the open-source community.
+Before you dig right into the code, we need contributors to follow a few
guidelines to have a chance of keeping on top of things.
Getting Started
---------------
@@ -62,7 +61,7 @@ Making Changes
+ Create a _topic branch_ for your isolated work.
* Usually you should base your branch on the `master` branch.
- * A good topic branch name can be the JIRA bug id plus a keyword, e.g.
`COMMONSSITE-123-InputStream`.
+ * A good topic branch name can be the JIRA bug ID plus a keyword, e.g.
`COMMONSSITE-123-InputStream`.
* If you have submitted multiple JIRA issues, try to maintain separate
branches and pull requests.
+ Make commits of logical units.
* Make sure your commit messages are meaningful and in the proper format.
Your commit message should contain the key of the JIRA issue.
@@ -72,7 +71,7 @@ Making Changes
+ Create minimal diffs - disable _On Save_ actions like _Reformat Source
Code_ or _Organize Imports_. If you feel the source code should be reformatted
create a separate PR for this change first.
+ Check for unnecessary whitespace with `git diff` -- check before
committing.
+ Make sure you have added the necessary tests for your changes, typically in
`src/test/java`.
-+ Run all the tests with `mvn clean verify` to assure nothing else was
accidentally broken.
++ Run all the tests with `mvn clean verify` to ensure nothing else was
accidentally broken.
Making Trivial Changes
----------------------
diff --git a/README.md b/README.md
index 7536a48..63e2d13 100644
--- a/README.md
+++ b/README.md
@@ -45,7 +45,8 @@ Apache Commons Parent
[](https://github.com/apache/commons-parent/actions/workflows/maven.yml)
[](https://maven-badges.herokuapp.com/maven-central/org.apache.commons/commons-parent/?gav=true)
-[](https://javadoc.io/doc/org.apache.commons/commons-parent/71)
+[](https://javadoc.io/doc/org.apache.commons/commons-parent/72)
+[](https://github.com/apache/commons-parent/actions/workflows/codeql-analysis.yml)
[](https://api.securityscorecards.dev/projects/github.com/apache/commons-parent)
The Apache Commons Parent POM provides common settings for all Apache Commons
components.
@@ -67,7 +68,7 @@ Alternatively, you can pull it from the central Maven
repositories:
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-parent</artifactId>
- <version>71</version>
+ <version>72</version>
</dependency>
```
diff --git a/RELEASE-NOTES.txt b/RELEASE-NOTES.txt
index 611c03f..4e56417 100644
--- a/RELEASE-NOTES.txt
+++ b/RELEASE-NOTES.txt
@@ -1,3 +1,44 @@
+Apache Commons Parent 72
+RELEASE NOTES
+
+The Apache Commons Parent team is pleased to announce the release of Apache
Commons Parent 72.
+
+The Apache Commons Parent POM provides common settings for all Apache Commons
components.
+
+Version 72: Maintenance and update dependencies.
+
+New features
+------------
+* Add org.codehaus.mojo:taglist-maven-plugin:3.1.0 to plugin
management. Thanks to Gary Gregory.
+
+Changes
+-------
+* Bump org.apache:apache from 32 to 33 #445. Thanks to
Dependabot, Gary Gregory.
+* Bump org.apache.maven.plugins:maven-pmd-plugin from 3.22.0
to 3.24.0 #428, #450. Thanks to Dependabot, Gary Gregory.
+* Bump org.apache.maven.plugins:maven-failsafe-plugin from
3.2.5 to 3.3.1 #434, #443. Thanks to Dependabot, Gary Gregory.
+* Bump
org.apache.maven.plugins:maven-project-info-reports-plugin from 3.5.0 to 3.6.2
#433, #436. Thanks to Dependabot, Gary Gregory.
+* Bump org.apache.maven.plugins:maven-surefire-report-plugin
from 3.2.5 to 3.3.1 #432, #444. Thanks to Dependabot, Gary Gregory.
+* Bump org.apache.maven.plugins:maven-surefire-plugin from
3.2.5 to 3.3.1 #431, #446. Thanks to Dependabot, Gary Gregory.
+* Bump com.github.spotbugs:spotbugs from 4.8.5 to 4.8.6.
Thanks to Gary Gregory.
+* Bump org.apache.maven.plugins:maven-jar-plugin from 3.4.1
to 3.4.2 #435. Thanks to Dependabot, Gary Gregory.
+* Bump com.github.spotbugs:spotbugs-maven-plugin from
4.8.5.0 to 4.8.6.2 #437, #449. Thanks to Dependabot, Gary Gregory.
+* Bump commons.pmd-impl.version from 7.2.0 to 7.3.0 #438.
Thanks to Dependabot, Gary Gregory.
+* Bump org.moditect:moditect-maven-plugin from 1.2.1.Final
to 1.2.2.Final #439. Thanks to Dependabot, Gary Gregory.
+* Bump org.codehaus.mojo:versions-maven-plugin from 2.16.2
to 2.17.1 #440, #451. Thanks to Dependabot, Gary Gregory.
+* Bump org.codehaus.mojo:animal-sniffer-maven-plugin from
1.23 to 1.24 #441. Thanks to Dependabot.
+
+
+Historical list of changes:
https://commons.apache.org/proper/commons-parent/changes-report.html
+
+For complete information on Apache Commons Parent, including instructions on
how to submit bug reports,
+patches, or suggestions for improvement, see the Apache Commons Parent website:
+
+https://commons.apache.org/proper/commons-parent/
+
+Enjoy!
+Apache Commons Team
+
+-----------------------------------------------------------------------------
Apache Commons Parent 71
RELEASE NOTES
diff --git a/pom.xml b/pom.xml
index c697fa6..d0caf1c 100644
--- a/pom.xml
+++ b/pom.xml
@@ -80,13 +80,13 @@
<!-- configuration bits for cutting a release candidate, must be
overridden by components -->
<!-- TODO How can we make project.build.outputTimestamp and changes.xml's
release data the same? -->
<project.build.outputTimestamp>2024-06-10T20:12:58Z</project.build.outputTimestamp>
- <commons.release.version>71</commons.release.version>
- <commons.release.next>72</commons.release.next>
+ <commons.release.version>72</commons.release.version>
+ <commons.release.next>73</commons.release.next>
<commons.rc.version>RC1</commons.rc.version>
<commons.jira.id>COMMONSSITE</commons.jira.id>
<!-- Commons Release Plugin -->
<!-- Previous version of the component (used for reporting binary
compatibility check)-->
- <commons.bc.version>70</commons.bc.version>
+ <commons.bc.version>71</commons.bc.version>
<commons.release.isDistModule>true</commons.release.isDistModule>
<!--
Define the following in ~/.m2/settings.xml in an active profile:
diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index 7eb4f10..36a3bcd 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -57,7 +57,7 @@ The <action> type attribute can be add,update,fix,remove.
The changes report outputs actions in the order they appear in this file.
-->
<body>
- <release version="72" date="YYYY-MM-DD" description="Version 72:
Maintenance and update dependencies.">
+ <release version="72" date="2024-07-21" description="Version 72:
Maintenance and update dependencies.">
<!-- FIX -->
<!-- ADD -->
<action type="add" dev="ggregory" due-to="Gary Gregory">Add
org.codehaus.mojo:taglist-maven-plugin:3.1.0 to plugin management.</action>
