| 21:55 | <bakkot> | ljharb https://github.com/tc39/ecma262/pull/3559 and https://github.com/tc39/ecma262/pull/3566 should both get backported to es2025 |
| 21:55 | <bakkot> | I can do it but I assume you have a process |
| 22:01 | <ljharb> | yup |
| 22:02 | <ljharb> | is it ok to pull in the meta and editorial changes that have landed since the cut as well? (normally i pull in everything except unnecessary normative changes, when updating a candidate) |
| 23:15 | <Michael Ficarra> | @ljharb we'd rather not, just those 2 please |
| 23:26 | <ljharb> | alrighty. why not? |
| 23:53 | <Michael Ficarra> | there's plenty of things we could pull in, but we shouldn't make changes after the opt-out period starts unless they're really vital |
| 23:53 | <Michael Ficarra> | in theory, we should probably be notifying committee about every cherry-picked commit at plenary |
| 23:54 | <ljharb> | the attitude for all the editors in the past was that only normative ones fell into that category, editorial was just a nice to have and within the editors' purview |
| 23:54 | <Michael Ficarra> | @bakkot @shu 402 issue tracking <emu-normative-optional>: https://github.com/tc39/ecma402/issues/998 |
| 23:55 | <Michael Ficarra> | I'm not personally against that policy, though I don't feel particularly compelled to pull in the editorial changes either |
| 23:56 | <ljharb> | ¯\_(ツ)_/¯ up to yall, this'll just be the first time we didn't eagerly pull all non-normatives in |