Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Done
-
None
-
None
-
None
Description
The current distribution build process through "mvn clean package" contains only 4 jars.
If we look at the hadoop's release artifacts. It contains src, binary tarballs, changelog, rat txt file, release note, and their signatures.
[ztang@release-vm target]$ ls artifacts/ CHANGELOG.md hadoop-3.1.3-site.tar.gz hadoop-3.1.3.tar.gz CHANGELOG.md.asc hadoop-3.1.3-site.tar.gz.asc hadoop-3.1.3.tar.gz.asc CHANGELOG.md.sha512 hadoop-3.1.3-site.tar.gz.sha512 hadoop-3.1.3.tar.gz.sha512 hadoop-3.1.3-rat.txt hadoop-3.1.3-src.tar.gz RELEASENOTES.md hadoop-3.1.3-rat.txt.asc hadoop-3.1.3-src.tar.gz.asc RELEASENOTES.md.asc hadoop-3.1.3-rat.txt.sha512 hadoop-3.1.3-src.tar.gz.sha512 RELEASENOTES.md.sha512
After SUBMARINE-169, there're several improvements we need. Some of them could be seperate JIRAs.
- Build source code tarball as well
- When building source code tarball, package file LICENSE, NOTICE, folder "licenses" into source code tarball
- The binary distribution should package "LICENSE-binary", "NOTICE-binary", folder "licenses-binary" besides the 4 jars.
- Sign the artifacts after they're generated. Refer to hadoop's dev-support/bin/create-release or spark's release dev/make-distribution.sh
- Release note and changelog generation
yuan_zac, could you please take a look at this? Thanks.
Attachments
There are no Sub-Tasks for this issue.