Skip to content

Conversation

@iherman
Copy link
Member

@iherman iherman commented Feb 17, 2025

This is mostly to serve as placeholder for the PR transition; I am not sure the the document is indeed fully done.

@iherman iherman requested a review from mkhraisha as a code owner February 17, 2025 07:39
Copy link
Member Author

@iherman iherman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mkhraisha I am happy to help if an update is needed...

@iherman
Copy link
Member Author

iherman commented Feb 17, 2025

FWIW I ran the document against the pubrules checker and the link checker. The former went o.k. There are three issues raised by the linkchecker:

If you find the problems and it is merged, I guess you or I have to rebase the current branch to main and I can regenerate the PR.

B.t.w., here is the way I do the generation:

  1. Run the editors' draft (locally or on the Web, as you prefer) but using a query parameter to the URL:
?specStatus=PR&publishDate=2025-03-06
  1. On the upper right-hand corner of the page there is respec button, offering various ways to download the content. Choose HTML, you get an HTML on your machine, that is the generated version.
  2. The rest is github magic...

@mkhraisha
Copy link
Contributor

Will take the issues noted above and fix it prior to merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants