@casion
Thank you for your suggestions.
I have removed the old releases from[1] following your advice.
You can find the documentation in [2], and I will append it in the next vote
email.
1. https://dist.apache.org/repos/dist/release/incubator/devlake/
2. https://devlake.apache.org/docs/Develop
+1, binding
I checked:
[X] release files have the word incubating in their name
[X] the digital signature and hashes correct
[X] LICENSE and NOTICE files exist
--
Sincerely,
Liang Zhang (John)
Apache ShardingSphere
cas...@apache.org 于2022年9月2日周五 00:22写道：
> +1 (non-binding)
>
Hi all,
Thanks for reviewing and voting for Apache Kyuubi(Incubating)
v1.6.0-incubating RC1 release, I am happy to announce
the release voting has passed with
(* = binding)
+1:
- Cheng Pan
- Willem Jiang*
- Jeff Zhang*
- Chen Xia
- Duo Zhang*
- Akira Ajisaka*
- li gang
+0: None
OK, if it is not an actual production bug but only a test issue, then
it is not a blocker, we can fix it in the next release cycle.
+1 binding
Checked sigs and sums: Matched
LICENSE and NOTICE: looks fine.
DISCLAIMER: In place
Built from src: Passed with jdk8u292
Thanks.
Cheng Pan 于2022年9月5日周一
Hi all,
Apache Linkis (Incubating) Team is glad to announce the new release of
Apache Linkis (Incubating) 1.2.0.
Apache Linkis (Incubating) builds a computation middleware layer to
decouple the upper applications and the underlying data engines,
provides standardized interfaces (REST, JDBC, WebSo
+1 (non-binding)
Good luck!
Joe Evans 于2022年8月17日周三 22:41写道：
> Hi Apache Incubator community,
>
> The Apache MXNet (incubating) community has discussed[1] graduating to a
> top level project and passed a community vote[2][3]. We have also
> discussed[4] graduating in the Incubator community.
>
>
+1 (non-binding)
I checked
- DISCLAIMER、LICENSE and NOTICE files exist
- Incubating in the artifact names
- NOTICE file is good
- All download links are valid
- Apache rat checks are OK
Nicholas 于2022年9月2日周五 00:15写道：
> Hello Incubator Community,
>
>
> The Apache Kyuubi community has voted on and
Hi Duo,
Thanks for your patience, I checked the two failed test cases you
mentioned, but I can not reproduce the first[1] failure, it may be a
flaky test or something depending on your environment.
And we confirm that the test case[2] is a bad test case, but it does
not mean a bug, we opened an i
