www.libssh2.org | Daily snapshots | Mailing list archive | Docs | Examples | github

Archive Index This month's Index

Subject: Re: ping for release

Re: ping for release

From: Alexander Lamaison <swish_at_lammy.co.uk>
Date: Tue, 12 Jan 2016 22:29:37 +0000

On Tue, 12 Jan 2016 22:00 Daniel Stenberg <daniel_at_haxx.se> wrote:

> On Tue, 12 Jan 2016, Jakob Egger wrote:
>
> > Has anybody been able to sort this out in the last two months?
>
> I haven't seen any attempts nor reports on the list since Alexander pointed
> out the likely offending commits. I take that as a pretty strong sign that
> there isn't a very strong desire to get a version out.
>

I'm keen to see a new release, but I've been waiting to test whether the
commits I highlighted really do cause a problem or not. My trusty old test
suite that used to prove these kinds of things, depends on infrastructure
that no longer exists. I've started updating it, but it won't be finished
this week.

What about preemptively reverting those commits, making a release, then
immediately re-applying the commits to master. It's seems a shame to delay
other useful improvements.

Alex

_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2016-01-12

the libssh2 team