Subject: RE: [RELEASE] libssh2 1.5.0 is released!

RE: [RELEASE] libssh2 1.5.0 is released!

From: Bert Huijben <>
Date: Wed, 11 Mar 2015 11:05:28 +0100

> -----Original Message-----
> From: libssh2-devel [] On Behalf Of
> Daniel Stenberg
> Sent: woensdag 11 maart 2015 10:57
> To: libssh2 development
> Subject: RE: [RELEASE] libssh2 1.5.0 is released!
> 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.

It is a small problem to me (but I have to work around it for a few other packages as well).

When I build packages for inclusion in SharpSvn and SharpGit, I run a tool that automatically adds their version control locations to the .pdb debug symbols. That way when somebody uses my debug symbols in Visual Studio, VS will just fetch the original sourcefiles directly from sourcecontrol when he/she steps through the code.

So in most cases I try to build from source repositories instead of from tarballs, as tarballs don't have these sourcecontrol locations available.

The slightly bigger problem is that it also affects the banner used for authentication to servers... 1.5.0 build from the tag will now identify as 1.4.4_dev, while 1.5.0_dev would be more accurate.

If a server would have different behavior for different versions of libssh2, it would choose the wrong behavior. (But I think currently only some clients such as putty really use this behavior tweaking)


Received on 2015-03-11