Geeklog has Switched to GitHub

Back in September of 2008 Geeklog made the switch from CVS to Mercurial to take advantage of a distributed version control system. Geeklog had used CVS for about 7 years. Source control has kept improving and after another 7 years The Geeklog Team has decided to move from using Mercurial to Git, and to using GitHub as our web-based Git repository hosting service.

This change really only affects the developers of Geeklog. Normal web masters who use the Geeklog CMS will not notice any changes.

We decided on the change since GitHub offers all of the features our older setup had plus many more and, it is one of the largest source hosting services in the world. It also means we don't have to worry about maintaining our old systems and we can concentrate more on coding. GitHub offers many social networking type features along with the ability to track issues, access control, teams, fork projects, wikis, and task management. Plus currently a large number of Geeklog Plugins use GitHub as well.

The new Geeklog CMS and related code repositories can be found at the GitHub Geeklog Core Organization.

The Geeklog Team also have decided to switch from using our current Bug Tracker (called Mantis) to the Issue tracker which GitHub provides. We have updated the links on Geeklog.net and the Geeklog Wiki to reflect these changes. We have imported all the open and closed bug reports and feature request from our old Bug Tracker to GitHub. Some information we could not automatically import so the issues in the new tracker need some updating which we will get to in time. Information which needs updating includes labels, milestones (which version it is for) and descriptions. For this reason the old Mantis Bug Tracker will still be accessible but, please do not add any new information to it.

For all new bug reports and feature requests, please submit them to the new Geeklog Issues Tracker.