Alice Ryhl

And then six weeks later, the beta release becomes the next stable release.

Yeah, and so we don't really have a concept of beta features that are only available on beta.

Yeah, the main purpose of beta is to test, like you get six weeks to test the stable release.

So hopefully if there's any problems, we can fix them before it goes out into a stable release.

So here there are a few different ways to do it.

So let's say you want to add a new function in the standard library or a new type.

Then the library team actually has this thing called an ACP, an API change proposal, which is basically just an issue on GitHub.

So you open your issue, you describe your API, describe what the interface is, and explain why you should have it.

And it's much smaller than an IFC would be.

And then the library team can say, this is okay with us.

And then you can implement it unstable or nightly.

And then later you can then stabilize it.

And similarly, the compiler team has major change proposals.

MCPs.

Which are for the smaller features.

Yeah.

Even though it's called major, right?

It's big enough that they need you to put up an issue, but not big enough to need an RFC.

And for the compiler team, the classic example would be a new compiler flag.

So the thing about additions that is different from versions is that if you're using version 1.90 of the compiler, everything is using that version.