Re: [VOTE] Release Apache Commons Email Parent POM 2.0.0-M1 based on RC1

2024-06-27 Thread Henri Biestro


[ +1 ]
 
Builds/tests ok, site looks good, reports look good (nits: no Jacoco report, no 
japicmp, JIRA report missing some versions.)

Built using:
mvn clean install site -s ~/.m2/commons-settings.xml
On:
mvn -version
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /Users/hbiestro/Java/apache-maven-3.8.6
Java version: 1.8.0_352, vendor: Azul Systems, Inc., runtime: 
/Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.5", arch: "aarch64", family: "mac"

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons Email Parent POM 2.0.0-M1 based on RC1

2024-06-24 Thread Gary Gregory
Ping! to the PMC and curious reviewers.

On Thu, Jun 20, 2024 at 7:38 AM Gary Gregory  wrote:
>
> Ping! to the PMC and curious reviewers.
>
> TY,
> Gary
>
> On Tue, Jun 18, 2024 at 12:39 PM Rob Tompkins  wrote:
> >
> > +1
> >
> > > On Jun 15, 2024, at 1:20 PM, Gary Gregory  wrote:
> > >
> > > We have fixed a few bugs and added enhancements since Apache Commons
> > > Email Parent POM 1.6.0 was released, so I would like to release Apache
> > > Commons Email Parent POM 2.0.0-M1.
> > >
> > > The reason for a major new release is to deal with the horror show of
> > > Javax vs.Jakarta namespaces.
> > >
> > > Apache Commons Email Parent POM 2.0.0-M1 RC1 is available for review here:
> > >https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1
> > > (svn revision 69780)
> > >
> > > The Git tag commons-email-2.0.0-M1-RC1 commit for this RC is
> > > a514720114343be667e886123eddc90b36e72038 which you can browse here:
> > >
> > > https://gitbox.apache.org/repos/asf?p=commons-email.git;a=commit;h=a514720114343be667e886123eddc90b36e72038
> > > You may checkout this tag using:
> > >git clone https://gitbox.apache.org/repos/asf/commons-email.git
> > > --branch commons-email-2.0.0-M1-RC1 commons-email-2.0.0-M1-RC1
> > >
> > > Maven artifacts are here:
> > >
> > > https://repository.apache.org/content/repositories/orgapachecommons-1749/org/apache/commons/commons-email2-parent/2.0.0-M1/
> > >
> > > These are the artifacts and their hashes:
> > >
> > > #Release SHA-512s
> > > source/commons-email2-2.0.0-M1-src.tar.gz=9f2250cd484079e0d08cac0982985aae5261b87c42a36a4eaf61d6948e5afe0e43310819d6f442a864d95643b613dc2f197e455ab485afe794d614391145737d
> > > source/commons-email2-2.0.0-M1-src.zip=d9c8f206e0fd3e5b1fb38ea67d2e8f15eec53e340a64d4db0b253bfdf7edbad70710eb1ae6b0227b8926c072dc12e9772f1dbc9539217df8bb458318f700ab15
> > > binaries/commons-email2-2.0.0-M1-bin.tar.gz=c3ee2d6e0346f8bb15b9890767cd990353814cfacf18b8437f66fa573d63031f8ff47ce1d8de2868d5fa2ab4d04694e3aa1d8bd73faec5f3dea461c109ac8320
> > > binaries/commons-email2-2.0.0-M1-bin.zip=ba1207159f5c833bde93c691185da4114c040978b4454cab164582a3b633d86a49ebd91167c1786d7337d9faae982823ad5d4c24467abda9ca3331c3d24c1027
> > >
> > > I have tested this with 'mvn' (default goal) using:
> > >
> > > openjdk version "17.0.11" 2024-04-16
> > > OpenJDK Runtime Environment Homebrew (build 17.0.11+0)
> > > OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing)
> > >
> > > Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0)
> > > Maven home: /usr/local/Cellar/maven/3.9.7/libexec
> > > Java version: 17.0.11, vendor: Homebrew, runtime:
> > > /usr/local/Cellar/openjdk@17/17.0.11/libexec/openjdk.jdk/Contents/Home
> > > Default locale: en_US, platform encoding: UTF-8
> > > OS name: "mac os x", version: "14.5", arch: "x86_64", family: "mac"
> > >
> > > Darwin  23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:09:52
> > > PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64 x86_64
> > >
> > > Details of changes since 1.6.0 are in the release notes:
> > >
> > > https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/RELEASE-NOTES.txt
> > >
> > > https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/site/changes-report.html
> > >
> > > Site:
> > >
> > > https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/site/index.html
> > >(note some *relative* links are broken and the 2.0.0-M1
> > > directories are not yet created - these will be OK once the site is
> > > deployed.)
> > >There is no JApiCmp report in this major release.,
> > >
> > > RAT Report:
> > >
> > > https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-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-2.0.0-M1-RC1 commons-email-2.0.0-M1-RC1
> > > cd commons-email-2.0.0-M1-RC1
> > >
> > > 1b) Download and unpack the source archive from:
> > >
> > > https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/source
> > >
> > > 2) Check Apache licenses
> > >
> > > This step is not required if the site includes a RAT report page 

Re: [VOTE] Release Apache Commons Email Parent POM 2.0.0-M1 based on RC1

2024-06-20 Thread Gary Gregory
Ping! to the PMC and curious reviewers.

TY,
Gary

On Tue, Jun 18, 2024 at 12:39 PM Rob Tompkins  wrote:
>
> +1
>
> > On Jun 15, 2024, at 1:20 PM, Gary Gregory  wrote:
> >
> > We have fixed a few bugs and added enhancements since Apache Commons
> > Email Parent POM 1.6.0 was released, so I would like to release Apache
> > Commons Email Parent POM 2.0.0-M1.
> >
> > The reason for a major new release is to deal with the horror show of
> > Javax vs.Jakarta namespaces.
> >
> > Apache Commons Email Parent POM 2.0.0-M1 RC1 is available for review here:
> >https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1
> > (svn revision 69780)
> >
> > The Git tag commons-email-2.0.0-M1-RC1 commit for this RC is
> > a514720114343be667e886123eddc90b36e72038 which you can browse here:
> >
> > https://gitbox.apache.org/repos/asf?p=commons-email.git;a=commit;h=a514720114343be667e886123eddc90b36e72038
> > You may checkout this tag using:
> >git clone https://gitbox.apache.org/repos/asf/commons-email.git
> > --branch commons-email-2.0.0-M1-RC1 commons-email-2.0.0-M1-RC1
> >
> > Maven artifacts are here:
> >
> > https://repository.apache.org/content/repositories/orgapachecommons-1749/org/apache/commons/commons-email2-parent/2.0.0-M1/
> >
> > These are the artifacts and their hashes:
> >
> > #Release SHA-512s
> > source/commons-email2-2.0.0-M1-src.tar.gz=9f2250cd484079e0d08cac0982985aae5261b87c42a36a4eaf61d6948e5afe0e43310819d6f442a864d95643b613dc2f197e455ab485afe794d614391145737d
> > source/commons-email2-2.0.0-M1-src.zip=d9c8f206e0fd3e5b1fb38ea67d2e8f15eec53e340a64d4db0b253bfdf7edbad70710eb1ae6b0227b8926c072dc12e9772f1dbc9539217df8bb458318f700ab15
> > binaries/commons-email2-2.0.0-M1-bin.tar.gz=c3ee2d6e0346f8bb15b9890767cd990353814cfacf18b8437f66fa573d63031f8ff47ce1d8de2868d5fa2ab4d04694e3aa1d8bd73faec5f3dea461c109ac8320
> > binaries/commons-email2-2.0.0-M1-bin.zip=ba1207159f5c833bde93c691185da4114c040978b4454cab164582a3b633d86a49ebd91167c1786d7337d9faae982823ad5d4c24467abda9ca3331c3d24c1027
> >
> > I have tested this with 'mvn' (default goal) using:
> >
> > openjdk version "17.0.11" 2024-04-16
> > OpenJDK Runtime Environment Homebrew (build 17.0.11+0)
> > OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing)
> >
> > Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0)
> > Maven home: /usr/local/Cellar/maven/3.9.7/libexec
> > Java version: 17.0.11, vendor: Homebrew, runtime:
> > /usr/local/Cellar/openjdk@17/17.0.11/libexec/openjdk.jdk/Contents/Home
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "mac os x", version: "14.5", arch: "x86_64", family: "mac"
> >
> > Darwin  23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:09:52
> > PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64 x86_64
> >
> > Details of changes since 1.6.0 are in the release notes:
> >
> > https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/RELEASE-NOTES.txt
> >
> > https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/site/changes-report.html
> >
> > Site:
> >
> > https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/site/index.html
> >(note some *relative* links are broken and the 2.0.0-M1
> > directories are not yet created - these will be OK once the site is
> > deployed.)
> >There is no JApiCmp report in this major release.,
> >
> > RAT Report:
> >
> > https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-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-2.0.0-M1-RC1 commons-email-2.0.0-M1-RC1
> > cd commons-email-2.0.0-M1-RC1
> >
> > 1b) Download and unpack the source archive from:
> >
> > https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-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 

Re: [VOTE] Release Apache Commons Email Parent POM 2.0.0-M1 based on RC1

2024-06-18 Thread Rob Tompkins
+1

> On Jun 15, 2024, at 1:20 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added enhancements since Apache Commons
> Email Parent POM 1.6.0 was released, so I would like to release Apache
> Commons Email Parent POM 2.0.0-M1.
> 
> The reason for a major new release is to deal with the horror show of
> Javax vs.Jakarta namespaces.
> 
> Apache Commons Email Parent POM 2.0.0-M1 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1
> (svn revision 69780)
> 
> The Git tag commons-email-2.0.0-M1-RC1 commit for this RC is
> a514720114343be667e886123eddc90b36e72038 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-email.git;a=commit;h=a514720114343be667e886123eddc90b36e72038
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-email.git
> --branch commons-email-2.0.0-M1-RC1 commons-email-2.0.0-M1-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1749/org/apache/commons/commons-email2-parent/2.0.0-M1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> source/commons-email2-2.0.0-M1-src.tar.gz=9f2250cd484079e0d08cac0982985aae5261b87c42a36a4eaf61d6948e5afe0e43310819d6f442a864d95643b613dc2f197e455ab485afe794d614391145737d
> source/commons-email2-2.0.0-M1-src.zip=d9c8f206e0fd3e5b1fb38ea67d2e8f15eec53e340a64d4db0b253bfdf7edbad70710eb1ae6b0227b8926c072dc12e9772f1dbc9539217df8bb458318f700ab15
> binaries/commons-email2-2.0.0-M1-bin.tar.gz=c3ee2d6e0346f8bb15b9890767cd990353814cfacf18b8437f66fa573d63031f8ff47ce1d8de2868d5fa2ab4d04694e3aa1d8bd73faec5f3dea461c109ac8320
> binaries/commons-email2-2.0.0-M1-bin.zip=ba1207159f5c833bde93c691185da4114c040978b4454cab164582a3b633d86a49ebd91167c1786d7337d9faae982823ad5d4c24467abda9ca3331c3d24c1027
> 
> I have tested this with 'mvn' (default goal) using:
> 
> openjdk version "17.0.11" 2024-04-16
> OpenJDK Runtime Environment Homebrew (build 17.0.11+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing)
> 
> Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0)
> Maven home: /usr/local/Cellar/maven/3.9.7/libexec
> Java version: 17.0.11, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.11/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.5", arch: "x86_64", family: "mac"
> 
> Darwin  23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:09:52
> PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.6.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/site/index.html
>(note some *relative* links are broken and the 2.0.0-M1
> directories are not yet created - these will be OK once the site is
> deployed.)
>There is no JApiCmp report in this major release.,
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-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-2.0.0-M1-RC1 commons-email-2.0.0-M1-RC1
> cd commons-email-2.0.0-M1-RC1
> 
> 1b) Download and unpack the source archive from:
> 
> https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-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 

Re: [VOTE] Release Apache Commons Email Parent POM 2.0.0-M1 based on RC1

2024-06-18 Thread Gary D. Gregory
My +1

Gary

On 2024/06/15 17:19:50 Gary Gregory wrote:
> We have fixed a few bugs and added enhancements since Apache Commons
> Email Parent POM 1.6.0 was released, so I would like to release Apache
> Commons Email Parent POM 2.0.0-M1.
> 
> The reason for a major new release is to deal with the horror show of
> Javax vs.Jakarta namespaces.
> 
> Apache Commons Email Parent POM 2.0.0-M1 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1
> (svn revision 69780)
> 
> The Git tag commons-email-2.0.0-M1-RC1 commit for this RC is
> a514720114343be667e886123eddc90b36e72038 which you can browse here:
> 
> https://gitbox.apache.org/repos/asf?p=commons-email.git;a=commit;h=a514720114343be667e886123eddc90b36e72038
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-email.git
> --branch commons-email-2.0.0-M1-RC1 commons-email-2.0.0-M1-RC1
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1749/org/apache/commons/commons-email2-parent/2.0.0-M1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> source/commons-email2-2.0.0-M1-src.tar.gz=9f2250cd484079e0d08cac0982985aae5261b87c42a36a4eaf61d6948e5afe0e43310819d6f442a864d95643b613dc2f197e455ab485afe794d614391145737d
> source/commons-email2-2.0.0-M1-src.zip=d9c8f206e0fd3e5b1fb38ea67d2e8f15eec53e340a64d4db0b253bfdf7edbad70710eb1ae6b0227b8926c072dc12e9772f1dbc9539217df8bb458318f700ab15
> binaries/commons-email2-2.0.0-M1-bin.tar.gz=c3ee2d6e0346f8bb15b9890767cd990353814cfacf18b8437f66fa573d63031f8ff47ce1d8de2868d5fa2ab4d04694e3aa1d8bd73faec5f3dea461c109ac8320
> binaries/commons-email2-2.0.0-M1-bin.zip=ba1207159f5c833bde93c691185da4114c040978b4454cab164582a3b633d86a49ebd91167c1786d7337d9faae982823ad5d4c24467abda9ca3331c3d24c1027
> 
> I have tested this with 'mvn' (default goal) using:
> 
> openjdk version "17.0.11" 2024-04-16
> OpenJDK Runtime Environment Homebrew (build 17.0.11+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing)
> 
> Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0)
> Maven home: /usr/local/Cellar/maven/3.9.7/libexec
> Java version: 17.0.11, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.11/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.5", arch: "x86_64", family: "mac"
> 
> Darwin  23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:09:52
> PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.6.0 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/RELEASE-NOTES.txt
> 
> https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/site/changes-report.html
> 
> Site:
> 
> https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-RC1/site/index.html
> (note some *relative* links are broken and the 2.0.0-M1
> directories are not yet created - these will be OK once the site is
> deployed.)
> There is no JApiCmp report in this major release.,
> 
> RAT Report:
> 
> https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-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-2.0.0-M1-RC1 commons-email-2.0.0-M1-RC1
> cd commons-email-2.0.0-M1-RC1
> 
> 1b) Download and unpack the source archive from:
> 
> https://dist.apache.org/repos/dist/dev/commons/email/2.0.0-M1-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