Hi all,
The SAMOA community has voted to promote a release candidate to a
full-release.
The vote thread can be found at:
https://lists.apache.org/thread.html/r9ee34c67da99269915485635ae9c86e158fb9e149727e699d3990e23%40%3Cdev.samoa.apache.org%3E
and the result thread at:
https://lists.apache.org/
+1 (binding) with some caveats.
I checked:
* Incubating in name
* DISCLAIMER exists
* LICENSE and NOTICE okay (copyright end year in NOTICE needs a bump I
would suspect)
* Signatures okay
* Checksums okay
My understanding is that the KEYS file for your project is expected in:
https://dist.apach
HI,
-1 (binding) because of hash issue - but this is easily fixed without stopping
the vote and there’s no need for a revote. Once change I check and change my
vote to +1
I checked:
- incubating in name
- signature is fine (although it would be good to sigh with an apache email
address)
- hash
Looks like under "The developer's version artifacts" you have the sha512
hashes, but under the staging repo you just have sha1/md5.
On Wed, Mar 18, 2020 at 7:58 AM Justin Mclean
wrote:
> HI,
>
> -1 (binding) because of hash issue - but this is easily fixed without
> stopping the vote and there’
That is correct. The SHA1/MD5 files are automatically generated by the Maven
Release Plugin, and there doesn't seem to be anyway to configure this to use
SHA512 or override it. Furthermore:
https://infra.apache.org/maven-releases.html
states:
"
Don't try to publish .sha256 or .sha512 files; Ne
Hi,
> So the best I could do was to include the SHA512 with the developer artefacts.
That all that’s needed change my vote to:
+1 (binding)
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For a
Hi,
Look like this needs another IPMC vote, can any IPMC member help?
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
I’ll take a look this weekend or early next week.
Alan.
Sent from my iPhone
> On Apr 10, 2020, at 17:53, Justin Mclean wrote:
>
> Hi,
>
> Look like this needs another IPMC vote, can any IPMC member help?
>
> Thanks,
> Justin
>
> ---
+1. I checked the disclaimer, license, and notice files, the hash and key
signature. I did a build from source and ran the rat check.
One note on the rat check, five files fail. One of those is s shell script
that could have the license added, the others look like maybe they
couldn't. But it w
