+1
I checked:
- Include the word incubating in the release file name.
- Include an ASF LICENSE and NOTICE file.
- Have valid checksums or signatures.
- Be placed in the correct place on the ASF’s infrastructure.
- Have a KEYS file to validate the release.
On 2023/05/25 06:00:20 He Sun wrote:
+1
Checked:
- Include the word incubating in the release file name.
- Include an ASF LICENSE and NOTICE file.
- Have valid checksums or signatures.
- Be placed in the correct place on the ASF’s infrastructure.
- Have a KEYS file to validate the release.
On 2023/05/25 06:00:20 He Sun wrote:
> Hi
Hi Felix,
Besides, the `KEYS` conflict will be solved in the next release.
Regards,
He
On 2023/05/30 07:14:28 Felix Cheung wrote:
> +1
>
> - incubating in name
> - signature and hash are fine
>
> it looks like there is a conflict between KEYS (file) and keys (directory):
> $ tar xzf
Hi Felix,
First time to hear from you. Thank you.
Those "external" files are actually from third-party and their licenses are
included in the `LICENSE` file. Please check it.
Wait for more advice and comments from you in the future about all aspects of
Teacalve.
Thanks,
He
On 2023/05/30
+1
- incubating in name
- signature and hash are fine
it looks like there is a conflict between KEYS (file) and keys (directory):
$ tar xzf apache-teaclave-0.5.1-rc.2-incubating.tar.gz
apache-teaclave-0.5.1-rc.2-incubating/KEYS: Can't replace existing
directory with non-directory
tar: Error exit
+1, thanks.
On Wed, May 24, 2023 at 11:00 PM He Sun wrote:
> Hi all,
>
> I am pleased to be calling this vote for the release of
> Apache Teaclave (incubating) 0.5.1 (release candidate 2).
>
> The Apache Teaclave (incubating) community has voted and approved the
> release. The result thread is
