Gemini JPA Committers Guide
Welcome to Gemini JPA! As a committer you have demonstrated that you are not only interested in the project but are willing to contribute some of your time and energy to improving and advancing it. Thanks for that.
This page contains some hints and helps to get you up to speed and on your way.
Gemini is a multi-faceted project, with multiple subprojects that work together. The most important way to achieve this is to ensure there is regular communication not only with other team members but with members of the other teams. This is achieved in 3 different ways:
1) Project Conference Calls
The Gemini team has a regular conference call that is open to both committers and community members alike (although in practice consumers rarely join). Comitters are strongly encouraged to be on this call as it is the primary way that important issues are discussed and resolved. See the wiki http://wiki.eclipse.org/Gemini/Meetings for the call details, agenda for the next call, and minutes of previous calls.
2) Gemini Dev List
The dev list can be used to ask questions or bring up issues to the Gemini JPA subproject or the Gemini project at large. Committers should subscribe to the dev list (https://dev.eclipse.org/mailman/listinfo/gemini-dev) and participate in the discussions.
3) Bugzilla threads
Bugzilla is used to track bugs and issues and there are often bug-related discussions. Avoid having these discussions in email since the discussion has value worth capturing and should be associated with and locatable from the bug under discussion.
External code must come through the Eclipse IP process (http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf). Bugs must be filed by the contributor, with the code attached. Contributers should have been the primary authors of the code, and the code should be approved by the project lead before being committed to the repo.
All code that is being committed to the Gemini JPA repo should have an associated bug or enhancement request in Bugilla. The code should be revewed by another member of the team and have appropriate tests in place before being committed.
Builds are done by individual developers using Eclipse. To build Gemini JPA import the Eclipse project in the org.eclipse.gemini.jpa folder and build from within Eclipse.
The Gemini JPA team is not currently big enough to experience checkin collisions, but this highlights the importance of communication. If a checkin collision should occur, contact the team member you are colliding with and work out a suitable solution. It will likely just involve doing a simple managed merge.
Gemini JPA depends on EclipseLink so the most recent versions of the EclipseLink bundles should be obtained. The OSGi JPA classes are also required and are checked in the repo. Potential new dependencies should be discussed on the dev list before entering CQ requests.
We try (and have been successful up to this point) to achieve consensus around any issues and decisions that come up. This implies that there be flexibility on the part of all those involved. Stances taken based on pride or preconception are not productive and only serve to make issues more difficult to resolve.
In the event that a decision cannot be reached by consensus then a simple polling of the committers will be taken, with the project lead having the right to exercise a veto.
Releases should be discussed and included in the project plan. The release process must include an Eclipse release review as dictated by http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews.
A number of developer resources are available on the Eclipse wiki: http://wiki.eclipse.org/Development_Resources.