We have fixed a few bugs and added some enhancements since Apache
Commons Email 1.5 was released, so I would like to release Apache
Commons Email 1.6.0.
Apache Commons Email 1.6.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/email/1.6.0-RC1
(svn revision 66107)
The Git tag commons-email-1.6.0-RC1 commit for this RC is
87af7b59e028eeddab6fbb0913f478806ef35f4b which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-email.git;a=commit;h=87af7b59e028eeddab6fbb0913f478806ef35f4b
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-email.git
--branch commons-email-1.6.0-RC1 commons-email-1.6.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1679/org/apache/commons/commons-email/1.6.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Sun Dec 17 15:18:49 EST 2023
commons-email-1.6.0-bin.tar.gz=6a4a10caf0b34f03a11ff304d5f6f375f9db4b308d90faae3e6481e65aa7a656878f75f125fffbf810cb6f593be7421f28ee28fe3186235ff8e0ea314ec4a20c
commons-email-1.6.0-bin.zip=1778e9bfdb4187db5ca6decdf145c9fb2d2fb40ea8b0042e2cb9f9b01894ffc769e52b445944ce3a61d09961ec06363265cbc7da5bbb9ef12b304f762c3e5e29
commons-email-1.6.0-bom.json=305440224d8a8656b45f3520e3412a070e2e6aa81cbfcc3db99e7d46aa0ebf375073b56acd38d6f8e1a8c65ae720977fea018fb2cab9357bd2215b0ed10f585d
commons-email-1.6.0-bom.xml=cd6bc9d89de911ed74c6b5dab5566de461f104a190ead92ac7d1fc84e8470bf183ab27206cd0a833da7ce57ad72f6adf7f1ad3ff2e28a37995161d3aa4eb14d7
commons-email-1.6.0-javadoc.jar=66098b52ef630c7cce7360eb56c852a90468013cab518d7b8b1138ab4fa991445a4955ee53a1b257399da75f47c7625c221b20275b1b04aec7abdc437ffdfeb1
commons-email-1.6.0-sources.jar=4034bffae7692d304be7e85e658ae527c1e4e73f5bbb18c86a79c4db02e258d08f0647c8569e67bb60e5122063cf9cf2b6b1e966d1489d5e6c7a001d95dd2dd7
commons-email-1.6.0-src.tar.gz=6e4d3d231d87df63e37a23e1c2aa560574ddf098d425866612373d3bd157c86e291eb5c00696234e22828fa9e49e849213715a4f5ed05491c0a890fb05f1e0fa
commons-email-1.6.0-src.zip=97b10a33f00f25c42c49d395bcb88f47979e8900001953e6f984edacaba9473f3de5b80f2d95c3b8b163ba7330e93180ba05b5841e317bad2859f8245d0083f1
commons-email-1.6.0-test-sources.jar=c08aa2683a1d668cfc54e7e7c33b2cac5af448bb090a43e95ff6bb7b925f5edcecc05a5830a7892dce3039496a7b8e9adec8f7e3455b9750aac6baf9d162da88
commons-email-1.6.0-tests.jar=d66a90e061e6bd3a60554bc28f97520f4e07dea6a904d31b05eef003c604b9e497b53c740271cd9e6b63cf55cdec3379423e1e0a26a50f3d0512b641011e9f45
org.apache.commons_commons-email-1.6.0.spdx.json=c6743eb717cba41d7cc891f12955494e0d7b8bc2e8a687a8cd45cd5110c36d8deac0266969b830c6041270fa89b18e20dba82c329c5240ddc3367635c753f52b
I have tested this with:
- 'mvn' and
- 'mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package
site deploy'
Using:
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /usr/local/Cellar/maven/3.9.6/libexec
Java version: 21.0.1, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk/21.0.1/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.2", arch: "x86_64", family: "mac"
Darwin **** 23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:54:10
PST 2023; root:xnu-10002.61.3~2/RELEASE_X86_64 x86_64
Details of changes since 1.5 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/email/1.6.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/email/1.6.0-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/email/1.6.0-RC1/site/index.html
(note some *relative* links are broken and the 1.6.0 directories
are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 1.5):
https://dist.apache.org/repos/dist/dev/commons/email/1.6.0-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/email/1.6.0-RC1/site/rat-report.html
KEYS:
https://downloads.apache.org/commons/KEYS
Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now.
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
Thank you,
Gary Gregory,
Release Manager (using key 86fdc7e2a11262cb)
For following is intended as a helper and refresher for reviewers.
Validating a release candidate
==============================
These guidelines are NOT complete.
Requirements: Git, Java, Maven.
You can validate a release from a release candidate (RC) tag as follows.
1a) Clone and checkout the RC tag
git clone https://gitbox.apache.org/repos/asf/commons-email.git
--branch commons-email-1.6.0-RC1 commons-email-1.6.0-RC1
cd commons-email-1.6.0-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/email/1.6.0-RC1/source
2) Check Apache licenses
This step is not required if the site includes a RAT report page which
you then must check.
mvn apache-rat:check
3) Check binary compatibility
Older components still use Apache Clirr:
This step is not required if the site includes a Clirr report page
which you then must check.
mvn clirr:check
Newer components use JApiCmp with the japicmp Maven Profile:
This step is not required if the site includes a JApiCmp report page
which you then must check.
mvn install -DskipTests -P japicmp japicmp:cmp
4) Build the package
mvn -V clean package
You can record the Maven and Java version produced by -V in your VOTE reply.
To gather OS information from a command line:
Windows: ver
Linux: uname -a
5) Build the site for a single module project
Note: Some plugins require the components to be installed instead of packaged.
mvn site
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html
-the end-
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
