iherman
commented
1 year ago @OR13, I indeed did not give all the details in #115 because I thought it was obvious that the full respec structure of the spec must be changed. My bad. I will create a separate PR with the way I believe the respec must be. I will also cc the webmaster to that PR to be on the safe side, and I actually will have a question to him there.
To avoid any mess up, I would propose:
- We close this PR without a merge
- The yml change for the actions that you had in this PR should be made separately and asap; better do it as a separate step to avoid any action happening in subsequent PR-s. (It is actually unnecessary, imho, to go through a PR for that one, just do the change directly on the repo.)
- I realized that we must change the repo before the publishing. The fact is that respec refers and, more importantly, pulls in issues based on the github reference, and that must be the final one. So just ping me when the repo change can be done.
- I will set the publication date to July 20; we should be able to handle all the steps by then.
edited: the aforementioned PR is #126
OR13
Preview | Diff