Release Plan for Gerrit 3.8
High Level Release Plan
|May 9-15||Gerrit Hackathon on Discord|
|May 19||Final release of
The Gerrit hackathon is planned during the release week, fully remote and hosted on Discord.
We also encourage all the JGit contributors and committers to join the event.
We will also ask the community members to allocate some of their time during the hackathon to help with finalizing the release:
- Test the release candidates.
- Report issues.
- Triage and troubleshoot incoming bug reports.
- Make fixes.
- Do code reviews.
- Test the latest head of the stable branch.
To expedite reviews of Library-Compliance and frontend changes, we will ask Google to make some members available in the EU time-zone.
NOTE: for all of those who cannot travel there will be a remote collaboration channel where anyone around the world could join the hackathon remotely.
We plan to use the Gatling e2e test framework for Git, developed by GerritForge and Ericsson, to test the stability of the release on a production-like setup on AWS automatically provisioned using the aws-gerrit templates.
GerritForge has also offered its own AWS infrastructure to test the scalability of Gerrit v3.8, particularly with medium to large sized projects and in a multi-primary setup.
The Gerrit-CI has also an automated aws-gerrit pipeline that will be pointed to the stable-3.8 branch and run on a daily basis.
End of Life for Gerrit 3.5.x
Per the support policy mentioned on the project homepage, after 3.8.0 is released 3.5.x will reach end of life and will no longer be actively supported.
Support for 3.6.x and 3.7.x will continue as usual. Users of 3.5.x or earlier are recommended to upgrade to one of these versions.