search

w3c / beacon

Beacon
https://w3c.github.io/beacon/
Other
46 stars 22 forks source link

Setup auto publishing #76

Closed yoavweiss closed 9 months ago

yoavweiss commented 2 years ago

The current spec is out of date and should be re-published. Might as well set up autopublishing.

/cc @caribouW3 @nicjansma

caribouW3 commented 2 years ago

It's already in CR, we can republish CR drafts (no substantial change) or we need a CR snapshot (if substantial change since last CR). We probably need a wide/horizontal review if we need a new CR snapshot. If no substantial change were made, can we move on to PR, then REC instead?

yoavweiss commented 2 years ago

Looking at the diffs between the published version and the latest, it seems like the main difference is the integration with Fetch and its keep-alive flag. I don't think this merits a new review cycle.

yoavweiss commented 2 years ago

Moving to PR SGTM, as the WPTs are now green: https://wpt.fyi/results/beacon?label=experimental&label=master&aligned

IIRC, the group generally preferred the CR-snapshot Living Standard model, but in case of Beacon, there's a good chance we can get it to REC and call it done. (as we don't predict any substantive changes in its future)

yoavweiss commented 1 year ago

@caribouW3 - Can we move this to PR? What's the next action on that front?

caribouW3 commented 1 year ago

@yoavweiss We need a CfC to be able to record a WG's decision (for either a new CR Snapshot or a PR)

domenic commented 1 year ago

A CR-snapshot living standard would work better for maintaining the spec in the face of future updates to Fetch, Web IDL, HTML, etc.

caribouW3 commented 1 year ago

Fine by me. @yoavweiss should I issue the CfC then?

yoavweiss commented 1 year ago

I agree with @domenic about a CR-snapshot being the more future-proof route, especially given the work on https://github.com/wicg/unload-beacon which may be a good fit to fold into this spec (if folks are interested). I'll send a CfC for a CR snapshot.

clelland commented 1 year ago

It appears that auto-publishing has been set up already -- my last two merges appear to have updated https://www.w3.org/TR/beacon/ automatically; it's now showing as a CRD there.