- From: Atsushi Shimono (W3C Team) <atsushi@w3.org>
- Date: Fri, 11 Mar 2022 18:30:45 +0900
- To: spec-prod@w3.org
- Message-ID: <ff53bc4e-3743-8208-507e-98bbdd001e9e@w3.org>
hi Francois, Chris, Thank you for letting me know on how to fix, and also one for spec-prod. I've noticed that PR merged: https://github.com/w3c/spec-prod/pull/129 and it should fix this point without any update in GHAction. Not like GPU for the web, updates at IWWG are not so frequent, so I may need some time (days or a week) to confirm. # sorry for late response, I was mostly off-the-keyboard yesterday, due that preparation for office moving On 2022/03/10 03:04, Francois Daoust wrote: > Yes, the issue is indeed that "Prepare for TR: yes" is not set. > > WebXR and WebGPU specs are automatically published to TR through the spec-prod action. The problem is that the spec-prod action does not set "Prepare for TR: yes", whereas it should. That has gone unnoticed until now because the pubrules checker was more lax than it now is. > > I closed the issue I had created against Bikeshed (which works as intended), and created one against spec-prod instead: > https://github.com/w3c/spec-prod/issues/128 > > Atsushi, in the meantime, you may add "Prepare for TR: yes" to WebXR specs, which should be enough to resume publication. I'm hoping that we can fix the spec-prod action pretty soon though, because I need the fix for Media WG and GPU for the Web WG specs as well ;) > > Francois. > > ------ Original message ------ > From: "Chris Lilley" <chris@w3.org> > To: "Atsushi Shimono (W3C Team)" <atsushi@w3.org>; spec-prod@w3.org > Date: 09/03/2022 17:42:28 > >> Do you have >> >> Prepare for TR: yes >> >> in your bikeshed document, when you are preparing for publication? >> >> On 2022-03-09 01:28, Atsushi Shimono (W3C Team) wrote: >>> hi spec-prod colleagues, >>> >>> Not a main topic for here, but let me ask some help on bikeshed. >>> >>> I'm working as a team contact for Immersive-Web (WebXR), and we are suffering to error >>> of /TR/ publication, with >>> e.g. >>> https://labs.w3.org/echidna/api/status?id=bf194827-43d5-4429-a928-25717b4e7e34 >>> https://labs.w3.org/echidna/api/status?id=ec014e14-6ac6-4fa9-b2d6-c05bff69be2a >>> >>> also I've found several similar, like (gpuweb) >>> https://labs.w3.org/echidna/api/status?id=80dbafe9-108e-46e8-b2c6-1c45e9e65354 >>> >>> # note, this seems to happen from 4th March globally to bikeshed specs?? >>> >>> >>> These error (style.sheet last) is to check whether /TR/ stylesheet is at the last of >>> stylesheets >>> https://github.com/w3c/specberus/blob/main/lib/rules/style/sheet.js >>> but last change to the file was at around one month ago. >>> https://github.com/w3c/specberus/commit/e95ca8845f0b6978f28dcf8dd05c9a765c4d167a >>> (so, timing is inconsistent) >>> >>> boilerplate for IWWG does not contain style definition, also generated html has one >>> external stylesheet (/TR/ one) and several inline style blocks specified in .bs source. >>> header for W3C has one placeholder of stylesheet: >>> https://github.com/tabatkins/bikeshed-boilerplate/blob/main/boilerplate/header.include >>> >>> Do we need to ask some change in bikeshed processing, like what respec performed >>> several years ago, or, do I miss some bikeshed configuration?? >>> https://github.com/w3c/respec/pull/2142/files >>> >> -- Chris Lilley >> @svgeesus >> Technical Director @ W3C >> W3C Strategy Team, Core Web Design >> W3C Architecture & Technology Team, Core Web & Media >> >> >
Received on Friday, 11 March 2022 09:30:50 UTC