- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Thu, 25 Apr 2024 10:23:05 -0400
- To: Ivan Herman <ivan@w3.org>
- Cc: Brent Zundel <brent.zundel@gmail.com>, W3C VC Working Group <public-vc-wg@w3.org>
On Wed, Apr 24, 2024 at 11:41 PM Ivan Herman <ivan@w3.org> wrote: > The publication of a CR Snapshot does require an official transition request by the W3C management, akin to the initial transition from a Working Draft to CR. Good to know that I'm not going insane (yet)... I remember CR2 transitions being historically painful from a documentation and horizontal review checking perspective. It's why I've been muscle-memory tagging everything w/ "CR1" and "editorial" or "normative" labels, so it's easy to review what sort of horizontal re-review we'd need as well as the disposition of comments for every issue. I remember having to hand compile those over the years by going back through the commit history (when we worked in CVS and then Subversion) and the transition to Github making it slightly easier. In any case, a reminder to the Chair and Staff that we need to be really careful about marking every issue and PR now with "CR1" and "editorial" or "normative" labels (I've been doing this since we entered CR1, but might have missed a few issues / PRs). Doing so will help us figure out if we need to ping test suite authors, implementers, and/or the horizontal review groups again. It will also help us write the disposition of comments into the changelog during the CR transition request. > However, the load is somewhat lower. There is a section in the process document on "Streamlined Publication Request" > > https://www.w3.org/2023/Process-20231103/#streamlined-update Hmm, I don't think our "Horizontal Review Group has made available a set criteria under which their review is not necessary"... we'll probably have to make a judgement call on normative changes that might require a re-review. Or, we might just ask every HR group for a re-review and point them to the changelog and PRs for them to make a determination if they need to re-review. Also, I don't know what this requirement means: "There must have been no changes to Working Group requirements about this document." Does that mean "no normative changes to the specification"? If so, all of our specs will have suffered at least one normative change during CR1 (which is expected). -- manu -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. https://www.digitalbazaar.com/
Received on Thursday, 25 April 2024 14:23:45 UTC