CR pub fails due to spurious "missing transition request" issue

[tabatkins]

We're trying to publish CSS View Transitions as a CR, which we already have approval for in the transitions repo: https://github.com/w3c/transitions/issues/561

However, Specberus is failing with the following message:

"transition-checker": {
        "status": "error",
        "errors": [
          "Error: Issue not found on the github repository w3c/transitions. Make sure all the requirements are met: https://github.com/w3c/echidna/wiki/CR-publication-workflow#request-a-transition-request"
        ]
      }

We have no idea what this check is actually asking for.

[fantasai]

See https://wiki.csswg.org/spec/publish#step-by-step-publishing-a-css-spec ; for CR you need to file an issue in the Transitions repo I don't think you can't publish it yourself.

[tabatkins]

Yes, that issue is already filled and linked in the original post. It was approved last week.

[fantasai]

I believe at this point the Team needs to handle the publication.

[deniak]

The list of requirements to publish CR with echidna is listed here. In this case, @plehegar needs to update his comment to 'Transition approved.' and the team contact needs to send a draft announcement to the communication team. Once reviewed, they will then comment 'draft transition received.'. With these 2 comments, echidna will be able to detect that the transition has been approved.

[deniak]

Also note that the title of the issue should end with the shortname of the spec.

It's important that the title of the issue ends with the shortname of your specification. That's how Echidna will find the right issue when processing your request.

[tabatkins]

The templates should be changed, then - currently it defaults the issue title to "CR Request for <title>", which suggests that what Khushal wrote was correct, rather than putting the shortname.

[svgeesus]

So the existing comment "Approved" isn't good enough and it needs the exact string "Transition approved."?

[svgeesus]

and the team contact needs to send a draft announcement to the communication team.

OK, on it.

[svgeesus]

"Some more information is needed before your document can be generated. Initial values may have been set automatically for some items, but please check to make sure they are correct."

SpecName |   -- | -- DocumentURI |   TransitionRequestURI |   FeedBackDueDate |   GroupName |   DisclosurePageURI |   Team Contact Name

However, for an automatic publication, `DocumentURI` is not known with any exactitude because it depends on which day the comm team adds the label that the draft is okay. I supose I will make an educated guess of this Monday. Has this procedure been, like, tested by someone?

[svgeesus]

Please try again. I have:

• edited the transition request title to be what specberus expects
• updated the .bs to have the correct status, review end date
• asked, and got, plh to change the "transition approved" message

Please report here if it fails again.

[svgeesus]

@tabatkins who was doing the specberus publication, when it failed?

[tabatkins]

Khushal

[svgeesus]

@khushalsagar do you want to try again, or would you rather I do it manually?

[khushalsagar]

@svgeesus happy to have you do it.

[svgeesus]

publication requested (manually) 3 Sept expected 5 Sept

[svgeesus]

I'm still interested to see if automatic CR publication works, but also unwilling to hold up a CR publication until after TPAC just to find out. Someone else can be the guinea-pig for this.

[deniak]

Hi Chris,

I think you now have all the requirements to publish that document with echidna. All you need to do is to:

• generate a token (link restristed to chairs and team contacts) for the spec https://www.w3.org/TR/css-view-transitions-1/
• update the date on the editor's draft to match the current day
• prepare a manifest listing all the related files and upload it under https://drafts.csswg.org/css-view-transitions-1/:

  index.html
  diagrams/desktop-browser-snapshot-root.svg
  diagrams/desktop-browser.svg
  diagrams/phases/phases.html
  diagrams/phases/script.js
  diagrams/phone-browser-scrolled-to-top-with-url.svg
  diagrams/phone-browser-scrolled-to-top-without-url.svg
  diagrams/phone-browser-snapshot-root.svg
  diagrams/phone-browser-with-url.svg
  diagrams/phone-browser-without-url.svg
  diagrams/phone-browser.svg
  diagrams/resources/scaler.js
  diagrams/resources/slides.js
  diagrams/videos/bad-sidebar.mp4
  diagrams/videos/circle.mp4
  diagrams/videos/default.mp4
  diagrams/videos/good-sidebar.mp4
  diagrams/videos/header.mp4
  diagrams/videos/slide.mp4
  diagrams/videos/slow.mp4

Once it's done, you can trigger the request to echidna with the following command:

curl 'https://labs.w3.org/echidna/api/request' --data 'url=<pathToTheManifest>&decision=<decisionUrl>&token=<token>

[svgeesus]

Published (manually) 5 Sept