protobuf-java v4 uptake
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- backend-api-design
Research direction
No files or tests are named. Begin by checking how pekko-grpc currently pins grpc-java and protobuf dependencies, then compare them with grpc-java 1.67 and protobuf-java v4; done means the upgrade is compatible with the planned v1.1.0 release.
Written by the indexing model from the issue text.
Description
grpc-java 1.67 is due on Sept 17.
https://github.com/grpc/grpc-java/issues/11015#issuecomment-2326633165
We are looking at the v1.1.0 release of pekko-grpc soon but it may be worthwhile delaying until this is ready.
- Dominant language
- Scala
- Stars
- 56
- Forks
- 31
- Avg merge
- 17h 2m
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/pekko-grpc
-
Difficulty 4/5 3-5 days Newbie friendliness 43/100
apache/pekko-grpc#933 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
apache/pekko-grpc#932 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
apache/pekko-grpc#931 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
apache/pekko-grpc#930 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 46/100
apache/pekko-grpc#929 ·
Maintainers usually reply within 1 day
All issues in apache/pekko-grpc
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
propensive/soundness#2438 ·
Maintainers usually reply within 1 day
-
No test covers transaction re-request after a delivery timeoutPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ergoplatform/ergo#2916 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Area: PDF support
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
orbeon/orbeon-forms#8055 ·
Maintainers usually reply within 2 days