Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes to 3-WD #371

Closed
13 of 14 tasks
mmccool opened this issue Jul 4, 2022 · 3 comments · Fixed by #398
Closed
13 of 14 tasks

Fixes to 3-WD #371

mmccool opened this issue Jul 4, 2022 · 3 comments · Fixed by #398
Assignees

Comments

@mmccool
Copy link
Contributor

mmccool commented Jul 4, 2022

@mmccool
Copy link
Contributor Author

mmccool commented Jul 4, 2022

When I was putting together PR #372 I noticed a couple more things to fix: an extraneous ed note, PR #353 on tracking/profiling, and updating the change log. So this PR does those too, and I added them to the description.

@mmccool
Copy link
Contributor Author

mmccool commented Jul 11, 2022

PR #373 addresses the point related to Issue #99. I added checkboxes to the description so we can check off everything that we have a PR for now, and proactively checked off the things that PR #373 and PR #372 address.

@mmccool mmccool mentioned this issue Jul 11, 2022
@mmccool
Copy link
Contributor Author

mmccool commented Aug 22, 2022

So current WD links to the implementation report in the repo, using github.io. We should really make a static snapshot and update this URL to point at the snapshot. For now I will update the implementation to fix the internal links and dates, and then close this issue, but for the final CR version we should point at a snapshot.

See also issue #391 - the link to the implementation report exists only in the WD, not the editor's draft. In general there are a number of fixes that only made it into the WD and we should back-patch them into the main branch.

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 a pull request may close this issue.

2 participants