| Date | Activity |
|---|---|
| Oct 21 | Create stable-3.11 branch, Release 3.11.0-rc0 |
| Oct 28 | Release 3.11.0-rc1 |
| Nov 4 | Release 3.11.0-rc2 |
| Nov 11 | Release 3.11.0-rc3 - Feature freeze deadline. |
| Nov 18 | Release 3.11.0-rc4 |
| Nov 25 | Release 3.11.0-rc5 - Release freeze |
| Dec 1 | Final release of 3.11.0 |
The Gerrit hackathon is planned before the stable-3.11 branch cut, from the 7th to the 8th of October at Qualcomm in San Diego (CA), focused on the JGit multi-pack index support.
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 and k8s-gerrit deployments.
GerritForge has also offered its own AWS infrastructure to test the scalability of Gerrit v3.11, particularly with medium to large sized projects and in a multi-primary setup and will also use its Google Cloud infrastructure to test Gerrit v3.11 with K8s.
The Gerrit-CI has also an automated aws-gerrit pipeline that will be pointed to the stable-3.11 branch and run on a daily basis.
Per the support policy mentioned on the project homepage, after 3.11.0 is released 3.8.x will reach end of life and will no longer be actively supported.
Support for 3.9.x and 3.10.x will continue as usual. Users of 3.8.x or earlier are recommended to upgrade to one of these versions.