On Wed, 11 Mar 2015, Bert Huijben wrote:
The tag you created still thinks it is libssh2 1.4.4 development.
Yes. This is a side-effect of the version being done for the tarball by the maketgz script so the actual release-string is never used in the git repo.
But I think you already fixed that on MASTER for the next release.
I bumped it for the next development period, yes. It is not a fix for the problem at the time of the next release...
To avoid future problems it could be an idea to create an 1.5.x branch (to create patch releases from after merging fixes) and bump trunk directly through to 1.6.x.
That wouldn't fix this problem. To fix this particular problem I would have to change the header in git to say the correct version before I package the release.
Is it really a problem to anyone though? The release is made with maketgz using the files in the git repo with the appropriate tag. The output tarball will have the correct version number in it.
-- / daniel.haxx.se _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
