| 01:01 | <rkirsling> | oh wow we went from a pretty sparse agenda to a really full one |
| 16:00 | <davethegr8> | Why did promise with resolvers for stage 4 #1453 merge after the deadline to advance? |
| 16:10 | <bakkot> | "must be added (and noted as such) along with links to the supporting materials prior to the deadline, or else delegates may withhold consensus for advancement solely on the basis of missing the deadline." |
| 16:11 | <bakkot> | i.e. you are still allowed to add things if you really want, just that delegates can object to advancement on the basis of lateness |
| 16:14 | <Chris de Almeida> | it is also noted with the emoji indication: ⌛️ late addition for stage advancement and/or schedule prioritization |
| 16:15 | <Chris de Almeida> | via Rob on Reflector: We have ~20 hours of content on the agenda and only ~16 hours of capacity. Meaning ~4 hours of content will likely overflow. Please consider if you would like to send a PR to reduce the requested timebox of any of your agenda items. Likewise if you would like to proactively designate your item as low priority (i.e. a candidate for overflow to the next meeting if we don't find time for it), please mark it with a ⬇ emoji. |
| 16:40 | <shu> | Rob Palmer: i don't know if you or someone else added the promise withresolvers thing, but i think it's too early for stage 4 just yet |
| 16:41 | <shu> | it just shipped and i'd like to wait for it to hit at least beta |
| 16:53 | <Chris de Almeida> | peetk: 👀 |
| 20:43 | <peetk> | oopsie daisy -- will revert agenda item |
| 20:48 | <ljharb> | (btw no need for a PR, just push up a commit) |