Skip to content

Conversation

@BigBlueHat
Copy link
Member

So...this is likely my fault...so I fixed the mess.

Not sure how the post-pub fixes work, but here it is all the same @iherman.

@iherman
Copy link
Member

iherman commented Feb 27, 2017 via email

@BigBlueHat
Copy link
Member Author

Yeah...that's what I figured. 😢 I'll do those steps.

@BigBlueHat
Copy link
Member Author

@iherman turned out to be a lot easier than I thought. 😃 I've added the necessary labels to this PR--which I hope "counts" as an issue for the needs of the errata process.

It (thankfully) shows up in the correct listing:
ErratumRaised

@iherman
Copy link
Member

iherman commented Mar 10, 2017

@BigBlueHat I would propose to close this PR without merge.

@almereyda
Copy link

This is a very minor change, easy to fix. Is there something one can do to promote it to the release version on https://www.w3.org/TR/annotation-html/ four years after discovery and providing an erratum?

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