Hi Michael,
Thanks for your suggestion! We're just back from the Lunar New Year holiday.
> My thought is that putting the information into a table on the website,
and not just on a Google Sheet referenced by the website
Each way has its advantages and limitations, I still prefer to keep the
info
> This google sheet [1] has been already contributed to our community.
> Everyone has access to view and comment on it.
Thank you for clarifying. This google sheet is filled with very
valuable, detailed information!
My thought is that putting the information into a table on the website,
and not j
Hi Michael,
Thanks for raising this up.
> It is only in a Google Sheet right now, though. Maybe the owners of
the Google doc would consider contributing it to the website?
This google sheet [1] has been already contributed to our community.
Everyone has access to view and comment on it.
> The w
We have a Client Features Matrix page on the GitHub wiki [0]. This
seems like a helpful and relevant resource for this thread.
It is only in a Google Sheet right now, though. Maybe the owners of
the Google doc would consider contributing it to the website?
The website references this matrix on th
Good ideas, we need such a mechanism to complement the current process to
ensure that other language SDKs know what's going on with the Java SDK,
which would be a good start for other language SDKs. We can clearly see
where the gap between the current SDK and the Java SDK is, which new
functions we
I'm not sure if the bots can detect if the change is a Java client change,
maybe based on the changes introduced in which directory.
The main headache here is missing it. If there are some mechanisms that can
remind us.
It will be great. Looks like
"hey, new changes introduced in Java client, you
+1
> I wonder if we can create issue in client repo automatically with bots for
> PRs labelled"component/client" in pulsar repo.
> This would save the extra effort for the reviewer.
But there are many PRs with "component/client" label that are specific
to java client changes. I think these shoul
+1.
I agree with Haiting Jiang.
The automatic process is a better way to solve this problem.
Thanks,
Mattison chao
+1. Great idea.
I wonder if we can create issue in client repo automatically with bots for PRs
labelled"component/client" in pulsar repo.
This would save the extra effort for the reviewer.
Thanks,
Haiting Jiang
On 2022/01/12 03:45:18 "r...@apache.org" wrote:
> Hello everyone:
>
> At present, a
Hello everyone:
At present, all our PIP and related function changes are mainly in the Java
language, and all new functions will be merged into the Java SDK first, but
for SDKs in other languages, this is completely a black box, they don't
know what changes or optimizations have been made on the J
10 matches
Mail list logo
