Regarding Github issue resolution

Questions
1

Hi.

I raised a few days before an issue on GitHub (HTTPS request fails with mbedtls_ssl_handshake: -26112 on Windows and Android, works on macOS and iOS · Issue #13421 · defold/defold), which was quickly closed, mentioning that it did require an mbedTLS upgrade to 4.1.1 and a refresh of cacert.pem to the September 26 Mozilla bundle.

I deleted my build folder, thinking that any new updated libraries required for compiling would be updated, including mbedTLS, but the problem persisted. Does this mean that to get the updated libraries I’m just waiting for a new Defold version, or it’s a step I can already take with the existing 1.13.2?

2

The issue fixed in 1.14.1 (current alpha version).

3

A few words about how it works.

We have three channels: alpha, beta, and stable.
All development happens in alpha. All fixes go there.

Once a month, alpha is merged into beta, and we start beta testing for two weeks. We avoid merging any fixes into beta except for regressions introduced in that beta.

When beta testing is done, it is released as a stable version.

In this case, it is not a regression in the latest version, 1.14.0, so the fix goes to alpha, which will be promoted to beta in about two weeks.

But if you want to test it early and make sure it works for you, you can download the alpha here: Release v1.14.1 - alpha · defold/defold · GitHub

7 Likes
4

Thank you, crystal clear.

1 Like