GeoServer has moved to GitHub
GeoServer and GeoTools have moved to Git and GitHub for version control and source hosting. We hope that this change will make work easier for existing GeoServer developers and encourage contributions from new ones.
Git is a relatively new version management software. Compared with the Subversion software that GeoServer previously used, it offers several features including offline commits and history browsing, cryptographic checksums for commits, and several advanced options for automatic merging. In addition, Git’s distributed nature means that any potential contributor can “fork” the GeoServer code and make changes instead of waiting on a GeoServer committer to grant access. (Such changes must still be approved by the GeoServer development team in order to be included in an official GeoServer release.)
Along with the shift to Git, we are moving GeoServer’s source hosting to GitHub. GitHub provides free hosting for open-source projects, including nice tracking of forks, a syntax-highlighting source browser, and interesting reports on who is contributing to the project. GeoServer’s documentation, bug tracking, mailing lists, and IRC chat, however, are unaffected by the move.
The GeoServer developer manual has been updated with instructions on working with Git. If you are a Git guru with some tips to add to the guide, a savvy user with addenda for the manual, or a Java hacker with bugs to fix, please fork us on GitHub!
Vulnerability
- GeoServer 2.26.1 Release
- GeoServer 2.25.4 Release
- GeoServer 2.26.0 Release
- CVE-2024-36401 Remote Code Execution (RCE) vulnerability in evaluating property name expressions
- GeoServer 2.25.2 Release
- GeoServer 2.24.4 Release
- GeoServer 2.23.6 Release
- GeoServer 2.25.1 Release
- GeoServer 2.25.0 Release
- GeoServer 2.23.5 Release