Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the next version emscripten 4.0.0! #23235

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Dec 19, 2024

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!

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

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!
@sbc100 sbc100 changed the title Make the next version emscripten 4.0.0 Make the next version emscripten 4.0.0! Dec 19, 2024
@sbc100 sbc100 requested review from kripken and dschuff December 19, 2024 20:09
@sbc100
Copy link
Collaborator Author

sbc100 commented Dec 19, 2024

The wider discussion of the future of versioning is still up in the air: #19053, but that shouldn't causes us version paralysis in the meantime.

Copy link
Member

@kripken kripken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good!

Let's give it a longer than usual time to bake before the release, though, given all these changes. Anyhow, we can think about that next year...

@sbc100 sbc100 enabled auto-merge (squash) December 19, 2024 20:18
@msqr1
Copy link

msqr1 commented Dec 20, 2024

Finally...! After staying at 3.x.x for like 5 years.

@cclauss
Copy link
Contributor

cclauss commented Dec 20, 2024

Congrats on reaching v4. Should the testing versions be upgraded, or are they kept back on purpose?

.circleci/config.yml

executors:
  linux-node:
    docker:
      - image: cimg/node:18.20.3
  linux-python:
    docker:
      - image: cimg/python:3.10.7
  bionic:
    docker:
      - image: emscripten/emscripten-ci:focal

@sbc100
Copy link
Collaborator Author

sbc100 commented Dec 20, 2024

Congrats on reaching v4. Should the testing versions be upgraded, or are they kept back on purpose?

.circleci/config.yml

executors:
  linux-node:
    docker:
      - image: cimg/node:18.20.3
  linux-python:
    docker:
      - image: cimg/python:3.10.7
  bionic:
    docker:
      - image: emscripten/emscripten-ci:focal

I don't think the first two really matter. But the third one we choose deliberately to make sure we test on older versions of linux. If we want to drop support for the version of glibc in Ubuntu/Focal we could update this, but it don't any pressing reason for do that (at least not that I know of).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants