Hi,
I'd suggest start looking at requests for code cleanup, performance
optimizations or similar that doesn't
alter any public semantics (such as adding public APIs or subtly
changing the behavior of existing
ones).
A few simple JBS searches lists at least some things that look tempting:
"Cleanup":
https://bugs.openjdk.java.net/issues/?jql=text%20~%20%22Cleanup%22%20%26%26%20status%20in%20(Open)%20and%20assignee%20is%20EMPTY
"Optimize":
https://bugs.openjdk.java.net/issues/?jql=text%20~%20%22Cleanup%22%20%26%26%20status%20in%20(Open)%20and%20assignee%20is%20EMPTY
Some, mostly hotspot engineers, use the "starter" label to mark issues
thought to be good candidates for someone new to the project (this
doesn't necessarily
mean "easy"):
https://bugs.openjdk.java.net/issues/?jql=labels%20in%20(%22starter%22)%20%26%26%20status%20in%20(Open)
Hope this helps!
/Claes
On 2016-12-01 22:58, Patrick Reinhart wrote:
Hi there,
I wanted to ask if there is a simple JBS query to find small clean up parts to
help with?
Seems to me a good starting point for some „hacking-on-the-OpenJDK-sessions“
-Patrick
