KevI think it'd be a good idea (at least for me) in the future for us to avoid having many LCs on the go at once. Assuming about 90 to 120 minutes to read/digest/comment/reply on each one, and it's difficult to find enough time to deal with each one properly when there's several on the go at once.
ZashThat sounds sensible
KevI think the point's largely irrelevant, because I think all (or pretty much all) the current LCs are things that last Council didn't finish before their term ended.
KevBut ... just suffering a bit here trying to do decent reviews of all the specs under LC at the moment.
ZashI don't envy you
Ge0rGWe can hardly stop people from opening LCs at any desired speed.
KevWell, we *can* :)
KevIn as much as Council has always traditionally been asked before an LC is issued.
Kev(And throttling in order to ensure things get the review they need is probably one of the good reasons for delaying LCs).
Ge0rGI'm really confused by now, it seems. I actually misread all of the "LC" mentions above as [github] "PR"s.
Ge0rGRight, that sounds sensible.
KevMany people find my conversations are more pleasant if they replace many of my words with other ones of their choosing :p