[
https://issues.apache.org/jira/browse/SLING-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16592868#comment-16592868
]
Konrad Windszus edited comment on SLING-7534 at 9/3/18 4:35 PM:
----------------------------------------------------------------
As the first step I updated the ASF Parent Pom in the Sling Parent:
https://github.com/apache/sling-parent/commit/8d1903a1189424c8ba8a8a110b2dd9d75a8744fe
Still missing: Update the necessary steps at
http://sling.apache.org/documentation/development/release-management.html#promoting-the-release-1
as now the dist should rather be based on the target directory than on the
downloaded artifacts.
Update: Even the Maven team has not yet updated
https://maven.apache.org/developers/release/maven-project-release-procedure.html#Copy_the_source_release_to_the_Apache_Distribution_Area,
but I think now it is strictly required that someone builds the release
version to have the sha512 file (as it is not part of the Maven Staging Repo).
was (Author: kwin):
As the first step I updated the ASF Parent Pom in the Sling Parent:
https://github.com/apache/sling-parent/commit/8d1903a1189424c8ba8a8a110b2dd9d75a8744fe
Still missing: Update the necessary steps at
http://sling.apache.org/documentation/development/release-management.html#promoting-the-release-1
as now the dist should rather be based on the target directory than on the
downloaded artifacts.
> Release policy - stop providing MD5 and start providing SHA-512 signatures
> --------------------------------------------------------------------------
>
> Key: SLING-7534
> URL: https://issues.apache.org/jira/browse/SLING-7534
> Project: Sling
> Issue Type: Task
> Components: Tooling
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: Parent 35
>
>
> See http://www.apache.org/dev/release-distribution#sigs-and-sums , we SHOULD
> no longer provide MD5 checksums for new releases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
