This page lists out the current recommended steps to submit a patch as a New Contributor to OpenJDK. It assumes that you are making a fairly small change to core OpenJDK libraries, (i.e. Java code, as opposed to Hotspot C/C++/Assembly) for the latest version (9 at time of writing).Note that a OpenJDK 9 or OpenJDK 8 Updates.
NOTE: A new project called Betterrev is being built to automate the manual steps below and provide a Build & Test farm for new patch contributions, we. We're looking for more volunteers, please contact email@example.com if you'd like to help!
I NEED HELP! If you need help at any time don't hesitate to contact us at firstname.lastname@example.org or on the IRC channel (#adoptopenjdk on irc.freenode.orgnet).
- Firstly read Read the Official Contribution Guide for OpenJDK.Email email@example.com and .
- If you feel you are comfortable diving straight in, then simply follow the steps outlined in that guide.
I'd like to be guided through my first patch(es)
If you'd like some assistance in submitting your first patch, then the adoption group is a great place to start! You generally need to go through the following steps.
- Find something you'd like to work on, either in JBUG or if you need some ideas contact the mailing list.
- Once you've decided, email the mailing list and state what you're going to work on. It can be disheartening if you work on something privately that OpenJDK isn't able to accept, so it's good to check early.s important to discuss a patch early!
- Sign the OCA if you haven't already done so.
- Get the latest OpenJDK Source source and Build build it - Instructions Here
- Make your changes.
- Don't forget to update the appropriate test case or provide a new one using TestNG
- Run the JTreg Tests jtreg tests locally to make sure your patch is OK
- Each OpenJDK Project project has their own coding standards, you should check for the area that you are working on. Make sure you check their pages for any relevant info the relevant project page and apply the standards as needed.
- Create a Webrev by running the webrev.sh tool located at TODO for your patch - it will create a mini static HTML website for you.
- Host the Webrev somewhere on a web server that others can find/see.
- Email firstname.lastname@example.org and tell them about your patch and ask if you've got the right project and whether they can provide linking your Webrev and ask for an initial review.
- Once that passes, you'll need to find a Sponsor to officially review your patch. This This is typically someone with Reviewer status for that project.You , we can help you find one.
- If you didn't have a JBUG issue, you may need to ask that reviewer to submit a bug on your behalf to reference against in JBUG.
- Assuming your patch passes review it will then be merged into OpenJDK. Please note that subsequent testing by Oracle's internal team in particular may find bugs in your patch and you'll be asked to fix those.
I NEED HELP! If you need help at any time don't hesitate to contact us at email@example.com or on the IRC channel (#adoptopenjdk on irc.freenode.net).