- From: Philippe Le Hegaret <plh@w3.org>
- Date: Tue, 9 Nov 2021 16:16:23 -0500
- To: "Tab Atkins Jr." <jackalmage@gmail.com>, "spec-prod@w3.org Prod" <spec-prod@w3.org>
- Cc: sysreq@w3.org
Hi Tab, The changes to the templates were circulated in August: https://lists.w3.org/Archives/Public/spec-prod/2021JulSep/0015.html https://github.com/w3c/tr-design is where the changes were worked on. I was hoping to get time to help on the bikeshed front prior to November 2 but ended up not being able to. I'll look tomorrow at the changes done by David and complete them. Philippe [1] https://lists.w3.org/Archives/Public/spec-prod/2021OctDec/0044.html On 11/9/2021 4:06 PM, Tab Atkins Jr. wrote: > It looks like at the beginning of this month (November), Specberus > updated with some significant changes that are blocking publications, > but these changes were never communicated publicly, so now > Bikeshed-generated specs fail publication in a multitude of ways. Some > of the failure messages even *explicitly say* "If you are using > bikeshed, please update to the latest version.", but the current > latest version of Bikeshed does not conform to these new requirements, > because nobody told me about them! > > I've been bitten by numerous smaller unannounced Specberus updates in > the past, this month's update is just particularly egregious. Where > should I be watching to learn about these changes *before* they go > live on Specberus and get my users filing issues about failures? > > For an example, see > <https://www.w3.org/pubrules/?url=https%3A%2F%2Fwww.w3.org%2FTR%2F2021%2FWD-css-values-4-20211016%2F&profile=WD&validation=simple-validation&informativeOnly=false&echidnaReady=false&patentPolicy=pp2020>, > where a recent attempt at a publication is suddenly throwing over a > dozen errors, most or all of which are brand new and which I had no > way of anticipating. > > ~TJ >
Received on Tuesday, 9 November 2021 21:16:27 UTC