the release procedure for Z-Push 2.4.x versions will be the same as for Z-Push 2.3.x versions (except that we won’t publish tarballs anymore).
From today pre-final branch will contain Z-Push 2.4.x releases. If for some reason you want to continue using Z-Push 2.3.x pre-final, you’ll have to disable the current Z-Push pre-final repository and checkout release/2.3 branch. More information about using branches is available at: https://wiki.z-hub.io/display/ZP/How+to+get+the+latest+Z-Push+code+from+GIT.
By using the pre-final repository you will automatically get fixes fast and install beta versions.
- When a final is released, in the release/2.4 branch/pre-final repo this version also gets a tag, like version+1-beta0. So, 2.4.0 final in master is called 2.4.1.beta0 in release/2.4.
- Changes are going to be continuously merged into the release/2.4 branch.
- By using the pre-final repository you will get these changes when update/upgrade from the repository.
- These changes will be part of the next released beta, but you will have them before the beta is officially released (a released beta is just a bundle of changes).
- 2.4.0 was released (final, in the GIT master branch)
- in release/2.4 2.4.0 is called 2.4.1.beta0+0 (same thing, just a different name)
- as changes are merged, the last number will increase, 2.4.1.beta0+6 are changes that are going to become 2.4.1.beta1. Same as 2.4.1.beta1+X are changes that are going to become 2.4.1.beta2 (or perhaps final if we consider these changes trivial enough that we don’t release another beta).
This thread is to keep you updated about the changes that are merged into the release/2.4 branch.
Alternatively you could get the same via a GIT checkout of the release/2.4 branch.
If you have any feedback about the version, please open a new thread mentioning the exact version number logged in your z-push log.