ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
2.11.0 not tagged in git repository (Bug #1258)
I use git repo for upgrade.
$ git fetch remote: Counting objects: 98, done. remote: Compressing objects: 100% (32/32), done. remote: Total 61 (delta 44), reused 46 (delta 29) Unpacking objects: 100% (61/61), done. From https://github.com/chiliprojec... 63976e6..dfb7785 master -> origin/master 63976e6..93de0ba stable -> origin/stable 60b699e..1855439 stable-2.x -> origin/stable-2.x 52b568f..8be500d unstable -> origin/unstable * [new tag] v3.8.0 -> v3.8.0
Where is 2.11.0?
Meh... Looks like I tagged the wrong commit during release. The tag is there, but it is not the HEAD of the
stable-2.x branch as it should be. The branch is functionally equivalent to what is tagged. The on;y difference is the date in the changelog. I'm going to release v2.11.1 later to fix that. The release will contain no other changes other than the new tag.
Please compare for yourself:
- Assignee set to Holger Just
I can't checkout:
$ git fetch -v From https://github.com/chiliproject/chiliproject = [up to date] master -> origin/master = [up to date] release-v2.2.0 -> origin/release-v2.2.0 = [up to date] release-v3.0.0 -> origin/release-v3.0.0 = [up to date] release-v3.2.2 -> origin/release-v3.2.2 = [up to date] stable -> origin/stable = [up to date] stable-1.x -> origin/stable-1.x = [up to date] stable-2.x -> origin/stable-2.x = [up to date] unstable -> origin/unstable $ git checkout v2.11.0 error: pathspec 'v2.11.0' did not match any file(s) known to git.