Temporary fixup done.
Andy
On 24/10/2018 21:54, Andy Seaborne wrote:
I can fix up the current dist/binaries as per (1), if that's OK. As a
fixup, this is not assuming it is the long term decision.
For 3.8.0, the format was the format of Linux sha512sum (not the other
checksums) - that
I can fix up the current dist/binaries as per (1), if that's OK. As a
fixup, this is not assuming it is the long term decision.
For 3.8.0, the format was the format of Linux sha512sum (not the other
checksums) - that includes the file name and can be verify by sha512sum
--verify, and end in
The report is correct.
When we moved to SHA512 we had to additionally create them.
Then for 3.9.0, the Apache release profile did it for source-release.
Doing it for source-release is the only required part in ASF release policy.
We can either
1: put back the addition step to add SHA512 the b
Hi!
I’m not sure if this email address is the best way to report the issue
(I found it when trying to “improve this page” using the link in the
upper right corner), but FYI: the Apache Jena Releases page [1] links to
SHA512 files for the downloads, but those files don’t actually exist;
instead, ac
