ESP32 Forum

Which version of these two 3.3 branches of the IDF is the most recent and up to date?

v3.3-dev-278, or v3.3-beta1-223?

And can someone please tell me what the difference between "-dev" and "-beta1" is so that I can figure these things out for myself?

And I've just discovered there is a v3.3-beta2. After it "comes out of beta", what version number does it become?

Is there such a thing a stable release on the v3.3 branch?

I'm looking for the most stable version of v3.3 that doesn't involve me having to make the jump to v4.0

--- Doug

Which version of these two 3.3 branches of the IDF is the most recent and up to date?

v3.3-dev-278, or v3.3-beta1-223?

I'm not sure where the numbers 278 and 223 are from but the esp-idf git repository has two tags called v3.3-dev and v3.3-beta1. v3.3-beta1 is newer than v3.3-dev. All the tags for the esp-idf repository can be seen at https://github.com/espressif/esp-idf/tags. The tags are listed in chronological order, newest first.

And can someone please tell me what the difference between "-dev" and "-beta1" is so that I can figure these things out for myself?

To me, it looks like the esp-idf developers create a tag with the suffix "-dev" on the day they start developing a new version. The tag v3.3-dev was created on November 1st 2018, so I guess v3.3 development started on this day.

And I've just discovered there is a v3.3-beta2. After it "comes out of beta", what version number does it become?

Probably v3.3-rc1 for the first v3.3 release candidate.

Is there such a thing a stable release on the v3.3 branch?

Not yet.

I'm looking for the most stable version of v3.3 that doesn't involve me having to make the jump to v4.0

That would be v3.3-beta2.

Hi Doug,

I think Fivdi has covered most of your individual questions, but I'll add a couple more details:

- There is a page in the docs here which has a description of the different kind of IDF versions, branches, etc: https://docs.espressif.com/projects/esp ... sions.html . Please let me know if any information is missing from there.

- If I check out the "release/v3.3" branch from GitHub and do "git describe --tags" then I get:
This means this branch (the "v3.3 release branch") has had 116 commits since "v3.3-beta2" tag was taken.

So if you want to use a v3.3 prerelease, you can either take "v3.3-beta2" or take the "release/v3.3" release branch which has fixes applied since v3.3-beta2. Probably a v3.3-beta3 will be tagged soon (testing is ongoing for this version.)

If you want the latest stable release, at this time it is v3.1.3. But we'll be tagging a v3.2 Release Candidate this week, hopefully to be followed by the actual release. Check the GitHub Release page for that.

Fivdi & Angus,

Thanks for helping me get up to speed on versioning

--- Doug