@jple Just pinging you again, now that the "end of next week" has passed. 
4 Likes
Here's the related announcement: Change in Revocation Methods Due to a (now patched) ACME bug
6 Likes
Thank you all for your patience. This change is related to a (now patched) ACME bug that could have potentially been used for a denial of service attack. Let's Encrypt considered it a security bug that could affect other ACME CA implementations and embargoed the information during a responsible disclosure period.
Our update regarding this ACME implementation change is available here: Change in Revocation Methods Due to a (now patched) ACME bug
Additional questions and discussion can be held here: Question re: Change in Revocations Methods
10 Likes