Document version number change to 4.0.0

[ypujante]

Sorry to open a ticket for this, but can you provide an explanation of why the version is going from 3.1.74 to 4.0.0 (at least according to the file Changelog.md on the main branch)? I don't care either way, I just would like to understand the reasoning. Is there something that will be fundamentally broken between 3.1.74 and 4.0.0? That seems like a gigantic version change (why not 3.2.0 for example?). Usually, in other software projects, such a version change is because of fundamental changes.

Is there a forum/site/PR that discuss this change?

At the minimum, I believe the Changelog.md file entry for 4.0.0 should start with an explanation/reasoning about the change.

Thanks

[hoodmane]

The reason for the bump is given in #23235:

We have a whole bunch of significant change in the next release:

• 3 new wasm features enabled by default
• Use of async/await internally and in MODULARIZE mode
• LLVM libraries updated for v19.1
• Lots of old polyfills finally removed

Also, 74 revisions the 3.1 release is gettting pretty long in the tooth.

Plus it will be the first release of the new year!

It could be a slightly harder update than normal, but probably not way harder.

[sbc100]

Our versioning scheme is (as you have noticed) somewhat arbitrary, and we specifically do not do semantic versioning. Its more like the Linux kernel where its semi-arbitrary.

If you would like to see something different then we have an open discussion where we are trying to think if there is a way we can perhaps do things differently: #19053

[ypujante]

I am absolutely fine with "arbitrary" versioning. I just think PR #23235 should be the first entry in the Changelog file for 4.0.0, that way there is no confusion and or question like I had :)