Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EGerrit/Contributor Guide
EGerrit | |
Website | |
Download | |
Community | |
Mailing List • Forums • IRC • mattermost | |
Issues | |
Open • Help Wanted • Bug Day | |
Contribute | |
Browse Source |
Contents
Communication
Channel | EGerrit |
---|---|
Developer Mailing List | EGerrit developer mailing list |
Reporting Bugs | File new EGerrit bug |
User Forum | EGerrit Forum |
Obtaining Sources
EGerrit is self hosted in Git. You can browse the repository on the web: EGerrit
Build jobs
The build jobs can be found at EGerrit on Hudson
IDE configuration
Running the tests
The tests require a Gerrit server on which you can connect and commit. Don't worry, we have you covered. All you need to do is to install vagrant and depending on your OS you may also need to install VirtualBox yourself. Once this is done, go to the org.eclipse.egerrit/org.eclipse.egerrit.releng folder and run "vagrant up --provision"
Once this is done, you can run the tests either from the IDE or by executing the Maven build.
Plan
We are planning releasing the 1.0 version of our project in June 2016 as part of the Neon release. You can find an overview of our plan here
Contributing to the release train
Contributions to the release trains are done in the simrel git repository. In the release leading to 1.0 we are contributing our milestone p2 repository. This means that we have to make sure that the content we want to contribute has been promoted up to the milestone repo, and we don't have to update the various files in the simrel repo. If we wanted our contributions to be more specific (e.g. provide a specific build), then we will have to update the files from the simrel repo. For record, here is the initial commit adding EGerrit to the train: [1]
Note that in order to edit the simrel files, it is recommended to use the b3 aggregator editor.