Hi Norbert,

having something integrated into the VM is not necessarily hard.

The pull request of Holger has been accepted fast enough.

So your point is maybe more about delivery of the binary artefacts.

The pharo builds have been broken for some time but are now fixed, thanks to Fabio/Christophe/Clement/Esteban!

I wish we can preserve the green status longer this time.

The question is then about the release cycle which is well too loooonnng...

Continuous integration require GREEN builds, I wish we start using feature branchs and reject half-ready PR

Then stability of head revision (cog) also matters.

Automated tests don't catch all problems.

Changing the garbage collector for example may trigger rare bugs...

Maybe some essential (and limited) patch could be back-ported to well known stable point.

But this can't happen with current ressources...

IOW help is welcome!

Nicolas

2017-12-22 16:31 GMT+01:00 Esteban Lorenzano <estebanlm@gmail.com>:

the week I return from holidays I��m planing to get all that done (vm stuff).

Esteban

> On 22 Dec 2017, at 16:17, Norbert Hartl <norbert@hartl.name> wrote:
>
> I had that problem when openssl 1.1x library was present and SqueakSSL uses 1.0.2 library. The patch is done by Holger and ready to be integrated. But as always it is close to impossible to having something integrated in the vm.
>
> Norbert
>
>
>> Am 22.12.2017 um 16:12 schrieb Torsten Bergmann <astares@gmx.de>:
>>
>> Hi,
>>
>> I used ZnClient to call an HTTPS URL and while it worked well in the past
>> I now receive an "SSL Exception: connect failed [code:-5]".
>>
>> I guess the reason is an update of the URLs site to a server with newer TLS
>> protocol (TLS 1.2 instead of TLS 1.0).
>>
>> Do we support that already in Pharo?
>>
>> Thx
>> T.
>