Thanks, Justin.
We will fix the minor issues which you point out in our next release.
在 2021/11/30 下午2:44，“Justin Mclean” 写入:
H,
+1 (binding)
I checked:
- incubating in name
- LICENSE and NOTICE are good
- signatures and hashes correct
- All ASF files have ASF he
thanks, Willem.
On 2021/11/30 07:11:06 Willem Jiang wrote:
> +1 binding.
>
> I checked:
>
> - incubating in name
> - signed key and checksum.
> - the License and Notice file.
> - There is no binary file in the source Kit.
>
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
Hi, Lorin,
we have got three binding +1 from panjuan, justin, williem,
and the vote has passed three days.
we could close this vote as passed now.
please go on,
thanks.
On 2021/11/25 04:09:04 Lorin Lee wrote:
> Hello IPMC,
>
>
> The Apache brpc community has voted and approved the relea
Hello Incubator Community,
Thanks to everyone that participated. The vote to release Apache brpc
(Incubating) version 1.0.0 in general@incubator is now closed as PASSED.
Vote thread:
https://lists.apache.org/thread/c09hdp6c7thhg1v4n1qrqf4d93j8d1xb
The vote PASSED with 3 binding +1, 1 non bind
Thanks, Lorin，
we got 1.0.0 released finally.
Thanks for the vote from PanJuan，Justin，Willem，Ovilia and others，
and thanks for all suggestions and helps from the whole incubator community.
Best wishes,
Jerry
在 2021/11/30 下午5:52，“Lorin Lee” 写入:
Hello Incubator Community,
Thanks to ev
Hello,
After 6 days of being open, the vote has passed and I am closing the vote. I
will announce the results shortly.
On 2021/11/29 19:21:33 Eya Badal wrote:
> Hello Sebb,
>
> The mentioned key now also exists in the
> https://downloads.apache.org/incubator/age/KEYS
>
> Thank you,
> Eya
>
Hello Incubator Community,
Thanks to everyone that participated. The vote to release Apache AGE
(Incubating) version 0.6.0 in general@incubator is now closed as PASSED.
Vote thread:
https://lists.apache.org/thread/9q98y8lq2vv6o1fzcmj8jrbhdhgt3khx
This vote passed with 8 +1 votes (3 bindings and
Thanks for your input, Julian and Bertrand!
Unless there's anything else that needs to be discussed, I guess we can
close this [DISCUSS] thread, start a vote to graduate Hop without Ricardo
on the PMC, and vote him in after graduation.
Regards,
Bart
On Mon, Nov 29, 2021 at 9:14 PM Julian Hyde wr
Hi,
Sorry but -1 (binding) due to incompatible licenses in source release and those
licenses not mentioned. A WIP disclaimer isn’t a blanket exception and you need
to note what the issues are and inform the used of what licenses are
incompatible. Please see [4]
When voting on releases, it’s al
Hi,
Sorry but it’s -1 (binding) from me. You might want to consider using the work
in progress disclaimer.
I checked:
- incubator in name
- signatures and hashes are fine
- LICENSE is missing info on [1] and about a dozen other files. License
information needs to go in the LICENSE file. [3]
- N
Hi,
I know you’ve announced the result on this but I also checked it and would have
voted +1 (binding).
I found:
- incubating in name
- signatures and hashes are fine
- LICENSE and NOTICE are correct
- No unexpected binary files
- all files have correct headers
- can’t compile from source but
Hi Justin,
Thanks for the careful screening.
Basically, there are two issues in the release tar bar:
1. We are using a customized Rust's standard library and include
modified sources and other upstream code in our codebase.
2. We also include code of OP-TEE libraries as our vendored
third-par
Hi,
> Basically, there are two issues in the release tar bar:
> 1. We are using a customized Rust's standard library and include
> modified sources and other upstream code in our codebase.
> 2. We also include code of OP-TEE libraries as our vendored
> third-party libraries.
>
> These two codeb
You know, I want to know clearly what we need to put because we already
iterate four times, and if you tell us what we need to do and add, it will
be faster and more efficient.
The license issue came again over the same files, and this is the second
time the release got rejected by the same proble
Hi,
There’s no issue with the file headers, other than it just hard to review as
there is a lot of files without headers. On solution is to perhaps put all the
3rd party code into a folder called “3rdparty” so it’s clearer what is ASF code
and what is not?
Re license information you need to li
HI,
> There’s no issue with the file headers, other than it just hard to review as
> there is a lot of files without headers. On solution is to perhaps put all
> the 3rd party code into a folder called “3rdparty” so it’s clearer what is
> ASF code and what is not?
Sorry Ignore the above I was
Hi Justin,
Thanks for your checking, and valuable pointers.
--
Juan Pan(Trista), Twitter: @tristaZero
On 12/1/2021 12:35，Justin Mclean wrote：
Hi,
I know you’ve announced the result on this but I also checked it and w
17 matches
Mail list logo
