Re: New release distribution checksum policy

2018-08-24 Thread sebb
On 24 August 2018 at 19:42, sebb wrote: > On 24 August 2018 at 18:51, Thomas Vandahl wrote: >> On 24.08.18 15:42, sebb wrote: >>> If it really is the case that the Apache Parent POM only creates the >>> checksums for artifacts with a specific name, then IMO it is badly >>> broken and needs a bug

Re: New release distribution checksum policy

2018-08-24 Thread sebb
On 24 August 2018 at 18:51, Thomas Vandahl wrote: > On 24.08.18 15:42, sebb wrote: >> If it really is the case that the Apache Parent POM only creates the >> checksums for artifacts with a specific name, then IMO it is badly >> broken and needs a bug report. > > Feel free. Lines 425 to 454. > >>

Re: New release distribution checksum policy

2018-08-24 Thread Gilles
On Fri, 24 Aug 2018 19:51:04 +0200, Thomas Vandahl wrote: On 24.08.18 15:42, sebb wrote: If it really is the case that the Apache Parent POM only creates the checksums for artifacts with a specific name, then IMO it is badly broken and needs a bug report. Feel free. Lines 425 to 454. Note

Re: New release distribution checksum policy

2018-08-24 Thread Thomas Vandahl
On 24.08.18 15:42, sebb wrote: > If it really is the case that the Apache Parent POM only creates the > checksums for artifacts with a specific name, then IMO it is badly > broken and needs a bug report. Feel free. Lines 425 to 454. > Note that it says: > "For every artifact distributed to the

Re: New release distribution checksum policy

2018-08-24 Thread sebb
On 24 August 2018 at 14:13, Benedikt Ritter wrote: > Hi Thomas, > > Am Fr., 24. Aug. 2018 um 13:13 Uhr schrieb Thomas Vandahl : > >> Hi Benedikt, >> >> On 23.08.18 18:25, Benedikt Ritter wrote: >> > Am Do., 23. Aug. 2018 um 09:16 Uhr schrieb Thomas Vandahl > >: >> > >> >> Shall we use this for

Re: New release distribution checksum policy

2018-08-24 Thread Gilles
On Fri, 24 Aug 2018 15:13:22 +0200, Benedikt Ritter wrote: Hi Thomas, Am Fr., 24. Aug. 2018 um 13:13 Uhr schrieb Thomas Vandahl : Hi Benedikt, On 23.08.18 18:25, Benedikt Ritter wrote: > Am Do., 23. Aug. 2018 um 09:16 Uhr schrieb Thomas Vandahl >: > >> Shall we use this for

Re: New release distribution checksum policy

2018-08-24 Thread Benedikt Ritter
Hi Thomas, Am Fr., 24. Aug. 2018 um 13:13 Uhr schrieb Thomas Vandahl : > Hi Benedikt, > > On 23.08.18 18:25, Benedikt Ritter wrote: > > Am Do., 23. Aug. 2018 um 09:16 Uhr schrieb Thomas Vandahl >: > > > >> Shall we use this for commons-parent? > >> > > > > Sounds reasonable to me. > > If I'm

Re: New release distribution checksum policy

2018-08-24 Thread Thomas Vandahl
Hi Benedikt, On 23.08.18 18:25, Benedikt Ritter wrote: > Am Do., 23. Aug. 2018 um 09:16 Uhr schrieb Thomas Vandahl : > >> Shall we use this for commons-parent? >> > > Sounds reasonable to me. If I'm not mistaken, the requirement for SHA-512 checksums only exists for the source distribution,

Re: New release distribution checksum policy

2018-08-23 Thread Benedikt Ritter
Am Do., 23. Aug. 2018 um 09:16 Uhr schrieb Thomas Vandahl : > Shall we use this for commons-parent? > Sounds reasonable to me. Benedikt > > Bye, Thomas. > > Forwarded Message ---- > Subject: Re: New release distribution checksum policy > Date: Thu, 23

Fwd: New release distribution checksum policy

2018-08-23 Thread Thomas Vandahl
Shall we use this for commons-parent? Bye, Thomas. Forwarded Message Subject: Re: New release distribution checksum policy Date: Thu, 23 Aug 2018 08:02:45 +0200 From: Hervé BOUTEMY Reply-To: memb...@apache.org To: memb...@apache.org FYI, Apache parent POM 21 has been released

Fwd: New release distribution checksum policy

2018-08-13 Thread Gary Gregory
Date: Mon, Aug 13, 2018 at 4:46 PM Subject: New release distribution checksum policy To: Apache Members TLDR; The release distribution checksum policy requires new releases to use SHA-512 or SHA-256 and not SHA-1 for verification. Existing releases do not need to be changed. Releases still need