Milos Djermanovic

> To the extent that someone needs to support an older ECMAScript version, and they're using the `RegExp` constructor rather than a literal (so no parsing error), it seems helpful...

I'm also okay with it, and I agree we should use a more generic name that would allow us to add more to it in the future. Maybe `universal`, like...

Seems like we should also discuss branches. While we were in the v9 prerelease phase, we used the `v8.x` branch for development. The corresponding docs site branch was `latest`, because...

`v8.x-dev` sounds good to me.

I'll start working on this now.

I created `v8.x-dev` branch and updated the Branch name pattern to `v*.x-dev` in the Branch protection rule.

All tasks are done, so closing.

Where shall we maintain info about which rules are frozen? Maybe in `meta.docs.frozen` property (boolean) of rules?

Those are deprecated rules. What we need is to define a list of non-deprecated rules that are frozen.

To start, here's the list of all non-deprecated rules with `"type": "suggestion"` or `"type": "layout"`. I'm assuming that neither of `"type": "problem"` rules are frozen. Edit: This is now the...