This is an automated email from the ASF dual-hosted git repository.
garydgregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-parent.git
The following commit(s) were added to refs/heads/master by this push:
new 0089c83 Prepare for the release candidate
0089c83 is described below
commit 0089c832b3dc3ce0b06231f301220ea63c41d4e0
Author: Gary Gregory <[email protected]>
AuthorDate: Tue Oct 13 22:10:07 2026 +0000
Prepare for the release candidate
---
CONTRIBUTING.md | 20 ++++++++++----------
README.md | 10 +++++-----
RELEASE-NOTES.txt | 39 +++++++++++++++++++++++++++++++++++++++
src/changes/changes.xml | 2 +-
4 files changed, 55 insertions(+), 16 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index c699011..ab07333 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -41,17 +41,17 @@
Contributing to Apache Commons Parent
======================
-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.
+Have you found a bug, or do 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, please review these guidelines to help us
manage contributions.
Getting Started
---------------
+ Make sure you have a [JIRA account](https://issues.apache.org/jira/).
-+ Make sure you have a [GitHub account](https://github.com/signup). This is
not essential, but makes providing patches much easier.
-+ If you're planning to implement a new feature it makes sense to discuss your
changes on the [dev list](https://commons.apache.org/mail-lists.html) first.
This way you can make sure you're not wasting your time on something that isn't
considered to be in Apache Commons Parent's scope.
++ Make sure you have a [GitHub account](https://github.com/signup). This is
not essential, but it makes providing patches much easier.
++ If you're planning to implement a new feature, it makes sense to discuss
your changes on the [dev list](https://commons.apache.org/mail-lists.html)
first. This way you can make sure you're not wasting your time on something
that isn't considered to be in Apache Commons Parent's scope.
+ Submit a [Jira Ticket][jira] for your issue, assuming one does not already
exist.
- + Clearly describe the issue including steps to reproduce when it is a bug.
+ + Clearly describe the issue, including steps to reproduce it if it is a bug.
+ Make sure you fill in the earliest version that you know has the issue.
+ Find the corresponding [repository on
GitHub](https://github.com/apache/?query=commons-),
[fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo)
and check out your forked repository. If you don't have a GitHub account, you
can still clone the Commons repository.
@@ -60,16 +60,16 @@ Making Changes
--------------
+ Create a _topic branch_ for your isolated work.
- * Usually you should base your branch from the `master` branch.
- * A good topic branch name can be the JIRA bug ID plus a keyword, e.g.
`COMMONSSITE-123-InputStream`.
+ * 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`.
* 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.
* For example, `[COMMONSSITE-123] Close input stream sooner`
+ Respect the original code style:
+ Only use spaces for indentation; you can check for unnecessary whitespace
with `git diff` before committing.
- + 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.
-+ Write unit tests that match behavioral changes, where the tests fail if the
changes to the runtime are not applied. This may not always be possible but is
a best practice.
+ + 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.
++ Write unit tests that match behavioral changes, where the tests fail if the
changes to the runtime are not applied. This may not always be possible, but it
is a best practice.
Unit tests are typically in the `src/test/java` directory.
+ Run a successful build using the default [Maven](https://maven.apache.org/)
goal with `mvn`; that's `mvn` on the command line by itself.
+ Write a pull request description that is detailed enough to understand what
the pull request does, how, and why.
@@ -95,7 +95,7 @@ Submitting Changes
+ Push your changes to a topic branch in your fork of the repository.
+ Submit a _Pull Request_ to the corresponding repository in the `apache`
organization.
* Verify _Files Changed_ shows only your intended changes and does not
- include additional files like `target/*.class`
+ include additional files like `target/*.class`.
+ Update your JIRA ticket and include a link to the pull request in the ticket.
If you prefer to not use GitHub, then you can instead use
diff --git a/README.md b/README.md
index 7762f78..5cf824c 100644
--- a/README.md
+++ b/README.md
@@ -45,9 +45,9 @@ Apache Commons Parent
[](https://github.com/apache/commons-parent/actions/workflows/maven.yml)
[](https://search.maven.org/artifact/org.apache.commons/commons-parent)
-[](https://javadoc.io/doc/org.apache.commons/commons-parent/105)
+[](https://javadoc.io/doc/org.apache.commons/commons-parent/106)
[](https://github.com/apache/commons-parent/actions/workflows/codeql-analysis.yml)
-[](https://api.securityscorecards.dev/projects/github.com/apache/commons-parent)
+[](https://scorecard.dev/viewer/?uri=github.com/apache/commons-parent)
The Apache Commons Parent POM provides common settings for all Apache Commons
components.
@@ -68,7 +68,7 @@ Alternatively, you can pull it from the central Maven
repositories:
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-parent</artifactId>
- <version>105</version>
+ <version>106</version>
</dependency>
```
@@ -83,11 +83,11 @@ From a command shell, run `mvn` without arguments to invoke
the default Maven go
Contributing
------------
-We accept Pull Requests via GitHub. The [developer mailing
list](https://commons.apache.org/mail-lists.html) is the main channel of
communication for contributors.
+We accept pull requests via GitHub. The [developer mailing
list](https://commons.apache.org/mail-lists.html) is the main channel of
communication for contributors.
There are some guidelines which will make applying PRs easier for us:
+ No tabs! Please use spaces for indentation.
+ Respect the existing code style for each file.
-+ 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.
++ Create minimal diffs: disable on-save actions like reformatting source code
or organizing imports. If you feel the source code should be reformatted,
create a separate PR for this change.
+ Provide JUnit tests for your changes and make sure your changes don't break
any existing tests by running `mvn`.
+ Before you push a PR, run `mvn` (without arguments). This runs the default
goal which contains all build checks.
+ To see the code coverage report, regardless of coverage failures, run `mvn
clean site -Dcommons.jacoco.haltOnFailure=false -Pjacoco`
diff --git a/RELEASE-NOTES.txt b/RELEASE-NOTES.txt
index 53a45c3..d0c5fb0 100644
--- a/RELEASE-NOTES.txt
+++ b/RELEASE-NOTES.txt
@@ -1,3 +1,42 @@
+Apache Commons Parent 106 Release Notes
+---------------------------------------
+
+The Apache Commons Parent team is pleased to announce the release of Apache
Commons Parent 106.
+
+The Apache Commons Parent POM provides common settings for all Apache Commons
components.
+
+This is a feature and maintenance release. Java 8 or later is required.
+
+Changes
+-------
+* Bump org.apache.bcel:bcel from 6.12.0 to 6.13.0. Thanks to
Gary Gregory.
+* Bump com.github.spotbugs:spotbugs-maven-plugin from
4.10.4.0 to 4.10.5.0. Thanks to Gary Gregory.
+* Bump Bump com.github.spotbugs:spotbugs from 4.10.4 to
4.10.5. Thanks to Gary Gregory.
+* Bump org.codehaus.mojo:animal-sniffer-maven-plugin from
1.27 to 1.28. Thanks to Gary Gregory.
+* Bump org.codehaus.mojo:build-helper-maven-plugin from
3.6.1 to 3.6.2. Thanks to Gary Gregory.
+* Bump org.codehaus.mojo:exec-maven-plugin from 3.6.3 to
3.6.4. Thanks to Gary Gregory.
+* Bump org.codehaus.mojo:taglist-maven-plugin from 3.2.2 to
3.2.3. Thanks to Gary Gregory.
+* Bump org.codehaus.mojo:versions-maven-plugin from 2.21.0
to 2.23.0. Thanks to Gary Gregory.
+* Bump org.apache.maven.plugins:maven-artifact-plugin from
3.6.1 to 3.7.0. Thanks to Gary Gregory.
+* Bump org.apache.felix:maven-bundle-plugin from 6.1.2 on
6.2.0 on Java 17 and up. Thanks to Gary Gregory.
+* Bump org.apache:apache from 39 to 40 (parent POM). Thanks
to Gary Gregory.
+* Bump commons.pmd-impl.version from 7.27.0 to 7.28.0.
Thanks to Gary Gregory.
+* Bump com.puppycrawl.tools:checkstyle from 14.1.0 to 14.3.0
on Java 21 and up. Thanks to Gary Gregory.
+* Bump com.github.siom79.japicmp:japicmp-maven-plugin from
0.26.2 to 0.26.3. Thanks to Gary Gregory.
+* Bump org.ow2.asm:asm from 9.10.1 to 9.11. Thanks to Gary
Gregory.
+
+
+Historical list of changes:
https://commons.apache.org/proper/commons-parent/changes.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 105 Release Notes
---------------------------------------
diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index 27dd2a2..2c14e79 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="106" date="YYYY-MM-DD" description="This is a feature
and maintenance release. Java 8 or later is required.">
+ <release version="106" date="2026-10-13" description="This is a feature
and maintenance release. Java 8 or later is required.">
<!-- FIX -->
<!-- ADD -->
<!-- UPDATE -->
