Hi, according to ASF policy we should provide a SHA512 for the source-release artifact (https://infra.apache.org/release-distribution#sigs-and-sums <https://infra.apache.org/release-distribution#sigs-and-sums>). In addition it would be nice to allow reproducible builds (https://maven.apache.org/guides/mini/guide-reproducible-builds.html <https://maven.apache.org/guides/mini/guide-reproducible-builds.html>).
Basic support for former has been added in Sling Parent 35 (https://github.com/apache/sling-parent/commit/8d1903a1189424c8ba8a8a110b2dd9d75a8744fe0 <https://github.com/apache/sling-parent/commit/8d1903a1189424c8ba8a8a110b2dd9d75a8744fe0>) and also added to the staging repo in Parent 43 (https://issues.apache.org/jira/browse/SLING-7534 <https://issues.apache.org/jira/browse/SLING-7534>) The latter is supported since https://issues.apache.org/jira/browse/SLING-9307 <https://issues.apache.org/jira/browse/SLING-9307>. Also building with Java 11 is only supported in newer Sling Parents. What do you think about adding a check to the release management page in https://sling.apache.org/documentation/development/release-management.html#prerequisites <https://sling.apache.org/documentation/development/release-management.html#prerequisites> that the module must reference the latest Sling Parent? WDYT? Konrad
