Esp-idf v4.0

[gibson12345]

Is there an expected release date for version of esp idf that is currently sitting in the master branch of the repository?

Cheers,
Gibson

[ESP_Angus]

Hi Gibson,

I'm afraid we don't have a release date estimate for v4.0 yet. v4.0 feature complete, so we're going to start the beta/testing cycle soon (and a release/v4.0 prerelease branch will be pushed to GitHub soon.)

The next stable release will be v3.3 (we're releasing the v3.3 release candidate today).

For more information about our versioning, see the docs here: https://docs.espressif.com/projects/esp ... sions.html

Angus

[gibson12345]

= v4.0 feature complete, so we're going to start the beta/testing cycle soon

Hey Angus,

Do you mean to say you have completed to features that you guys have set out to complete for v4 and are just setting up to do internal testing and beta testing to find bugs?

Cheers,
Gibson

[ESP_Angus]

Do you mean to say you have completed to features that you guys have set out to complete for v4 and are just setting up to do internal testing and beta testing to find bugs?

That's exactly right. Also there are some known issues that we need to resolve, but features have all been merged.

[gibson12345]

Hey again Angus,

Just wanted to ask a quick question about the new 4.0 branch on the github. Will all further work for 4.0 be done in that branch or will it be put into master and merged into 4.0 once verified? Or would the reverse be the case?

Cheers,
Gibson

[ESP_Angus]

Just wanted to ask a quick question about the new 4.0 branch on the github. Will all further work for 4.0 be done in that branch or will it be put into master and merged into 4.0 once verified? Or would the reverse be the case?

We follow a backport process, so any fix which goes into release/v4.0 branch will first get merged into master and then backported into the release/v4.0 branch and other branches as needed.

Deployment to GitHub master branch is currently stalled because of an internal CI problem, so we have the awkward situation that some backports have appeared on the release/v4.0 branch before they have appeared on master. But this is a temporary situation, the master branch should be updated soon as well.

[gibson12345]

Hey Angus,

Thanks for the heads up hope you guys get CI stuff fixed soon, setting up my companies was a pain.
Could I ask a slightly off topic question? Who is the BLE expert as Espressif among the dev team and could I potentially open a more direct channel of communication?

Cheers,
Gibson

[permal]

Deployment to GitHub master branch is currently stalled because of an internal CI problem

Sorry for hijacking the thread, but is there a guesstimate on when that'll be up and running again?

Gibson - just a few words re. my experience working from the master branch. I've done that since pre v2 I think and while it has mostly been a good experience, things do break at times, despite Espressif's efforts. Apart from having all the good things, the main reason I'm working off master is the change to CMake and the ability to use gcc 8, i.e. C++ 17 support, which for me is worth some additional hassle.

As Angus wrote, there are some issues left to solve. The two major ones (that I've been affected by) are #3624 and #3592, concerning PSRAM and WiFi respectively. I'm not sure what the status on #3624 is, but at least #3592 is waiting to be merged (hence my question above).

[ESP_Angus]

Sorry for hijacking the thread, but is there a guesstimate on when that'll be up and running again?

ASAP, next 24 hours or so I'm hoping.

Gibson - just a few words re. my experience working from the master branch. I've done that since pre v2 I think and while it has mostly been a good experience, things do break at times, despite Espressif's efforts. Apart from having all the good things, the main reason I'm working off master is the change to CMake and the ability to use gcc 8, i.e. C++ 17 support, which for me is worth some additional hassle.

FWIW, for these priorities you may want to consider switching to the release/v4.0 release branch now that it's available. Should be a less bumpy ride.

[permal]

FWIW, for these priorities you may want to consider switching to the release/v4.0 release branch now that it's available. Should be a less bumpy ride.

Yes, I will likely do that.