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

use automatic publishing #101

Open
samuelweiler opened this issue Sep 21, 2020 · 17 comments
Open

use automatic publishing #101

samuelweiler opened this issue Sep 21, 2020 · 17 comments
Assignees
Labels

Comments

@samuelweiler
Copy link
Contributor

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.

@torgo
Copy link
Member

torgo commented Sep 23, 2020

Looping in @ylafon

@samuelweiler
Copy link
Contributor Author

At the least, can we do another versioned release in the next week or so?

@hober
Copy link
Contributor

hober commented Sep 28, 2020

Sounds good to me. I've never done this before, so I don't know where to start.

@hober hober added the task label Sep 28, 2020
@ylafon
Copy link
Member

ylafon commented Sep 28, 2020

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.

@samuelweiler
Copy link
Contributor Author

(c) section?

@samuelweiler
Copy link
Contributor Author

Any update on this? I dislike that the published version is so very much out of date...

@ylafon
Copy link
Member

ylafon commented Nov 12, 2020

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.

@hober hober assigned ylafon and unassigned hober and pes10k Nov 30, 2020
@pes10k
Copy link
Contributor

pes10k commented Jan 19, 2021

Publishing a snapshot sounds good to me!

@torgo
Copy link
Member

torgo commented Jan 28, 2021

Hi @ylafon any update on this? I think we are all keen to set up a process via which this can be auto-published.

@torgo
Copy link
Member

torgo commented Jan 28, 2021

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.

@wseltzer
Copy link
Contributor

I understand there's a Process issue. In the meantime, could we mint a new snapshot?

@hober
Copy link
Contributor

hober commented May 13, 2021

@wseltzer wrote, in February:

I understand there's a Process issue. In the meantime, could we mint a new snapshot?

A new snapshot got published in March.

Leaving this open as we still don't have automatic publishing set up for this document.

@samuelweiler
Copy link
Contributor Author

Tickling this issue, since people file new issues (like #129) that are already fixed in the editor's draft.

@ylafon
Copy link
Member

ylafon commented Sep 3, 2021

It should be part of implementation of process 2021 in specberus, so no progress can be made until the tool allow it.

@hober
Copy link
Contributor

hober commented Dec 8, 2021

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?

@hober
Copy link
Contributor

hober commented Mar 23, 2022

Any updates here, @ylafon @samuelweiler? We'd love to not have to think too hard about when to publish this thing.

@ylafon
Copy link
Member

ylafon commented Apr 1, 2022

It is making (slow) progress, I should be able to test soon, if it works, then we can make it automatic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants
@hober @pes10k @torgo @wseltzer @ylafon @samuelweiler and others