List view
4.17.0 release.
Due by November 19, 2025Release candidate for v4.17.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by November 12, 20254.16.0 release.
Due by November 6, 2024Release candidate for v4.16.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by October 30, 20244.15.0 release.
Due by July 24, 2024Release candidate for v4.15.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by July 17, 20244.14.0 release.
Due by April 24, 2024Release candidate for v4.14.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by April 17, 20244.13.0 release.
Due by October 11, 2023Release candidate for v4.13.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by October 4, 20234.12.0 release.
Due by January 25, 2023Release candidate for v4.12.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by January 18, 20234.11.0 release.
Due by April 6, 2022Release candidate for v4.11.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by March 30, 20224.10.0 release.
Due by November 3, 2021Release candidate for v4.10.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by October 27, 20214.9.0 release.
Due by August 19, 2021Release candidate for v4.9.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by August 12, 20214.8.0 release.
Due by March 24, 2021Release candidate for v4.8.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by March 17, 20214.7.0 release.
Due by December 9, 2020Release candidate for v4.7.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by December 2, 20204.6.0 release.
Due by June 18, 2020Release candidate for v4.6.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by June 11, 20204.5.0 release.
Due by March 6, 2020Release candidate for v4.5.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by February 28, 20204.4.0 release.
Due by October 23, 2019Release candidate for v4.4.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by October 16, 20194.3.0 release.
Due by June 21, 2019Release candidate for v4.3.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by June 14, 20194.2.0 release.
Due by October 24, 2018Release candidate for v4.2.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by October 17, 20184.1.1 release.
Due by March 5, 2018Release candidate for v4.1.1. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by February 26, 20184.1.0 release.
Due by November 21, 2017Release candidate for v4.1.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by November 14, 2017•2/2 issues closed4.0.0 release.
Due by January 31, 2017Release candidate for v4.0.0. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by January 10, 2017- Due by February 2, 2016
The 3.9.6 release.
Due by January 22, 2015Release candidate for v3.9.6. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by January 15, 2015•17/24 issues closedThe 3.9.4 release.
Due by November 20, 2012•2/2 issues closedThe 3.9.4 release candidate. At this point there will be a code freeze. That means no new features and all issues resolved where resolution was feasible. The time between RC and the final release should be used for testing.
Due by November 13, 2012•8/8 issues closed