We have fixed a few bugs and added enhancements since Apache Commons
FileUpload 2.0.0-M2 was released, so I would like to release Apache
Commons FileUpload 2.0.0-M3.
Apache Commons FileUpload 2.0.0-M3 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/fileupload/2.0.0-M3-RC1
(svn revision 76739)
The Git tag commons-fileupload-2.0.0-M3-RC1 commit for this RC is
a75dde28fe9e340a2f89c349f05a4ee5281417be which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-fileupload.git;a=commit;h=a75dde28fe9e340a2f89c349f05a4ee5281417be
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-fileupload.git
--branch commons-fileupload-2.0.0-M3-RC1
commons-fileupload-2.0.0-M3-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1834/org/apache/commons/
These are the artifacts and their hashes:
${commons.sha512list}
I have tested this with 'mvn' and 'mvn clean site' using:
Details of changes since 2.0.0-M2 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/fileupload/2.0.0-M3-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/fileupload/2.0.0-M3-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/fileupload/2.0.0-M3-RC1/site/index.html
(note some *relative* links are broken and the 2.0.0-M3
directories are not yet created - these will be OK once the site is
deployed.)
JApiCmp Report: There is no report because this is a milestone to a
new major release with a new package name.
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/fileupload/2.0.0-M3-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)
The following is intended as a helper and refresher for reviewers.
Validating a release candidate
==============================
These guidelines are NOT complete.
Requirements: Git, Java, and Maven.
You can validate a release from a release candidate (RC) tag as follows.
1a) Download and decompress the source archive from:
https://dist.apache.org/repos/dist/dev/commons/fileupload/2.0.0-M3-RC1/source
1b) Check out the RC tag from git (optional)
This is optional, as a reviewer must check source distributions as a minimum.
git clone https://gitbox.apache.org/repos/asf/commons-fileupload.git
--branch commons-fileupload-2.0.0-M3-RC1
commons-fileupload-2.0.0-M3-RC1
cd commons-fileupload-2.0.0-M3-RC1
2) Checking the build
All components should include a default Maven goal, such that you can
run 'mvn' from the command line by itself.
2) Check Apache licenses
This step is not required if the site includes a RAT report page which
you then must check.
This check should be included in the default Maven build, but you can
check it with:
mvn apache-rat:check
3) Check binary compatibility
This step is not required if the site includes a JApiCmp report page
which you then must check.
This check should be included in the default Maven build, but you can
check it with:
mvn verify -DskipTests -P japicmp japicmp:cmp
4) Build the package
This check should be included in the default Maven build, but you can
check it with:
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
4b) Check reproducibility
To check that a build is reproducible, run:
mvn clean verify artifact:compare -DskipTests
-Dreference.repo=https://repository.apache.org/content/repositories/staging/
'-Dbuildinfo.ignore=*/*.spdx.json'
Note that this excludes SPDX files from the check.
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
6) Build the site for a multi-module project
mvn site
mvn site:stage
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html
Note that the project reports are created for each module.
Modules can be accessed using the 'Project Modules' link under
the 'Project Information' menu (see <path-to-site>/modules.html).
-the end-
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
