-
Notifications
You must be signed in to change notification settings - Fork 34
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
use automatic publishing #101
Comments
Looping in @ylafon… |
At the least, can we do another versioned release in the next week or so? |
Sounds good to me. I've never done this before, so I don't know where to start. |
There are manual steps when publishing as the (c) section is not the usual one, so it would require some adaptation in order to do automatic publishing. |
(c) section? |
Any update on this? I dislike that the published version is so very much out of date... |
There are roadblocks that we are working on, expect this to use automatic publishing once the issues in getting design-principles document to do the same will be solved. |
Publishing a snapshot sounds good to me! |
Hi @ylafon any update on this? I think we are all keen to set up a process via which this can be auto-published. |
Just to be clear - auto-publication would imply that joint agreement is reached between PING and TAG via the PR and PR approval mechanism. And therefore any merged PR is a-ok to auto-publish to TR space. |
I understand there's a Process issue. In the meantime, could we mint a new snapshot? |
@wseltzer wrote, in February:
A new snapshot got published in March. Leaving this open as we still don't have automatic publishing set up for this document. |
Tickling this issue, since people file new issues (like #129) that are already fixed in the editor's draft. |
It should be part of implementation of process 2021 in specberus, so no progress can be made until the tool allow it. |
I think those updates have happened, but I'm not sure. What say you, @ylafon? |
Any updates here, @ylafon @samuelweiler? We'd love to not have to think too hard about when to publish this thing. |
It is making (slow) progress, I should be able to test soon, if it works, then we can make it automatic. |
Can we arrange for this doc to be automatically published, so we don't need to point at the editor's drafts?
If we need help, PLH is likely willing to help.
The text was updated successfully, but these errors were encountered: