| 13:54 | <ljharb> | also it seems like there's some linting errors in main of ecma262 |
| 14:07 | <bakkot> | that should not be possible |
| 14:07 | <bakkot> | I don't see any? |
| 14:14 | <ljharb> | hm |
| 14:14 | <ljharb> | maybe i wasn't npm installed, one sec |
| 14:14 | <bakkot> | oh yeah probably |
| 14:14 | <bakkot> | we changed the rules in the latest version |
| 14:14 | <bakkot> | specifically https://github.com/tc39/ecma262/pull/2708 |
| 14:15 | <ljharb> | yeah, that was most of the errors, and it seems like they're fine now |
| 14:15 | <ljharb> | let me make sure the 2022 build doesn't need an update :-) |
| 14:18 | <ljharb> | ok, it did; it's done |
| 14:46 | <bakkot> | shu / Michael Ficarra: can one of you give this report? my pattern is still asleep and I don't want to wake her |
| 14:46 | <bakkot> | I was intending to move my computer to somewhere it would be quieter but it turns out to be broken |
| 14:47 | <shu> | happy unless michael wants to |
| 14:47 | <Michael Ficarra> | @shu sure, I'll just do the CR slide I guess? |
| 14:47 | <shu> | sure we can tag-team |
| 14:47 | <shu> | anything special we want to say about cutting es22? |
| 14:48 | <ljharb> | just that the candidate is posted, on the repo and in the reflector, and we should approve it to start the optout period |
| 15:23 | <Michael Ficarra> | ljharb: the chairs want us to explicitly announce the 2022 cut and start of RF opt-out, would you like to do it since you've been managing that? |
| 15:24 | <ljharb> | sure |