On Mon, Feb 3, 2025 at 12:52 PM 'Ramiro Aparicio Gallardo' via grpc.io <
grpc-io@googlegroups.com> wrote:

> The situation is worse now:
>   * grpc-kotlin does not work with latest grpc-java version
>

I'm assuming you're referencing
https://github.com/grpc/grpc-kotlin/issues/633 . That actually looks normal
and I don't think you're blocked by any actions from grpc-kotlin. Add a
dependency on io.grpc:grpc-stub:1.70.0 and you should be fine.

 * There is no support for editions 2023
>

I added a comment to https://github.com/grpc/grpc-kotlin/issues/625 to
mention this is a problem for grpc-java as well. I'd hope it is as easy as
setting a few fields that "edition 2023 is supported;" gRPC didn't really
care about proto2 vs proto3.

 * the last release is still missing in maven.org even when it was released
> almost 6 months ago.
>

I think that's https://github.com/grpc/grpc-kotlin/issues/620

Maybe Jetbrains can come and help with the support or open it to the
> community but at the current state it is very likely that a fork will be
> needed sooner than later if there is no reaction from the gRPC team.
>

The release is definitely a problem and is a bit specialized because of
permissions. But other than the release, part of the problem is
(apparently; I don't think I have any extra insider knowledge) the amount
of time being spent on it. If there's interest in a fork that would imply
someone would need to spend time on it. Are you aware of people that should
be considered to become maintainers of (or simply help) grpc-kotlin. I
recognize that no merged PRs doesn't nurture maintainers, so there probably
isn't "an obvious set of existing contributors."

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to grpc-io+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/grpc-io/CA%2B4M1oNSdABQeBXRqid8AJmM%3DvNXxYrXxsbkBh_a3nkuA_Lw%3Dw%40mail.gmail.com.

Reply via email to