Since Google Code is turning read-only soon, KeeperFX code repository, issues and wikis were migrated to GitHub.
The SVN repository is directly converted to GitHub here:
https://github.com/dkfans/keeperfx
Issues and wikis are also there:
https://github.com/dkfans/keeperfx/issues
https://github.com/dkfans/keeperfx/wiki
I am now working on an 'improved' repository - with some cleanups, nightly builds even for very old versions, and code history from way before SVN repo was created (that was around version 0.3.4). The new repository (work in progress) is here:
https://github.com/dkfans/keeperfx-stable
Creating the "refactored" repository will take considerable time (for now I didn't even get to the point when SVN was created), but has a few advantages:
- cleaner code
- easier backtracing of code changes
- further backtracing of regressions
- clean distinction between main KeeperFX and related tools (tools are in separate repositories, linked to main repo as GIT Submodules)
- old code updated to be compilable on new GCC
- broken commits will be merged with their fixes, so that the code tree is always in good shape
Until the new branch is finished (which may take a month or two), development will continue on the migrated repository.
After all changes are merged to new repo, the the "dkfans/keeperfx" branch will be replaced by new repository. Developers will still have access to that branch, and nightly builds will be generated from it to allow testers check if the changes being made are ok.
Nightly builds will start working on the "dkfans/keeperfx" repository within days.
The "dkfans/keeperfx-stable" will have its own, separate collection of nightly builds. It will become a branch for reviewed and tested commits only.