"Giving up upstream-ing my patches & feel free to pick them up"
by csmantle on 1/31/2026, 10:53:38 AM
https://mail.openjdk.org/pipermail/hotspot-dev/2026-January/118080.html
Comments
by: rendaw
Regardless of the contents,<p>> For each of my emails, I got a reply, saying that they "sincerely apologize" and "@Dalibor Topic Can you please review...", with no actual progress being made.<p>then<p>> Sorry to hear this. .... @Dalibor Topic <dalibor.topic at oracle.com>, can we get this prioritized?<p>This is pretty morbidly funny.
1/31/2026, 4:27:52 PM
by: beart
I know Java has a complicated history of ownership, but I'm not sure I understand why Oracle is able to block contributions to OpenJDK. I thought the point of OpenJDK was to be separate from Oracle. I'm not a Java developer, just curious how this works.
1/31/2026, 6:05:14 PM
by: pjm331
I have this theory that with LLMs getting better at writing code our current open source model (relatively few large projects that everyone contributes to, relatively rare to maintain your own fork) will invert and it will be easier and more common for people to have personalized forks and a lot of the problems around managing large open source projects will just become irrelevant
1/31/2026, 5:56:40 PM
by: freedomben
All of the <a href="https://github.com/AOSC-Tracking/jdk/" rel="nofollow">https://github.com/AOSC-Tracking/jdk/</a> links 404 for me, so it's difficult to get a sense of what was being done. Going off of the "loongson fork" links though they look rather trivial. Not saying they should be ignored, but I do think trivial PRs to large critical open source projects like JDK can often end up taking more time away from contributing engineers doing reviews and testing than they are worth.<p>I know first-hand the frustration of having PRs ignored and it can be quite demoralizing, so I do feel for the author. It sounds like the author is getting to a place of peace with it, and my advice from having been down that path before is to do exactly that, and find something else interesting to hack on.
1/31/2026, 4:10:11 PM
by: voakbasda
When I want to contribute to an open source project, I throw together some trivial but useful patches and see how the project responds.<p>Many projects behave this way, particularly those with corporate overlords. At best, it will take weeks to get a simple patch reviewed. By then, I have moved on, at least with my intention to send anything upstream. I commend the author for giving them a whole year, but I have found that is best a recipe for disappointment.<p>Maintainers: how you react to patches and PRs significantly influence whether or not you get skilled contributors. When I was maintaining such projects, I always tried to reply within 24 hours to new contributors.<p>It would be interesting to see how quickly the retention rate drops off as the time to review/accept patches goes up. I imagine it looks like an exponential drop off.
1/31/2026, 4:41:37 PM
by: dwroberts
The PRs they link mostly seem like noise? “Remove the d prefix from this number because the C++ standard doesn’t require it”. Yeah great.
1/31/2026, 3:57:00 PM