chore(.travis): enable auto-publish

w3c / FileAPI

File API

https://w3c.github.io/FileAPI/

Other

104 stars 44 forks source link

chore(.travis): enable auto-publish #129

Closed marcoscaceres closed 5 years ago

marcoscaceres commented 5 years ago

Preview | Diff

marcoscaceres commented 5 years ago

@siusin @deniak, having some problems with this that I can't figure out: https://labs.w3.org/echidna/api/status?id=431c7058-5045-49d9-bd87-c418ec0eff2d

I think the "this-latest-shortname" might be invalid because BikeShed adds a "-1-" for the "level" (which is required by BikeShed), but I'm not sure. Could you confirm? We can ping Tab if true.

I'm not sure why the copyright is generating issues, however. The generated markup seems fine, unless there is something obvious I'm not seeing.

deniak commented 5 years ago

Here are the headers of the documents:

This version:
    https://www.w3.org/TR/2019/WD-fileapi-1-20190522/
Latest published version:
    https://www.w3.org/TR/FileAPI/
Editor's Draft:
    https://w3c.github.io/FileAPI/
Previous Versions:
    https://www.w3.org/TR/2017/WD-FileAPI-20171026/

The first thing I notice is that it'll be considered as a shortname change and Echidna currently doesn't support that so you would have to send a request to webreq@w3.org for that version at least. Then, I'm not sure how bikeshed generates the document but the shortnames in the "This version" link and in the "Latest published version" should be the same. So in this case, you should have something like

This version:
    https://www.w3.org/TR/2019/WD-fileapi-1-20190522/
Latest published version:
    https://www.w3.org/TR/fileapi-1/

Regarding the copyright, the link for MIT, ERCIM and Keio should be under https.

marcoscaceres commented 5 years ago

Thanks @deniak! I'll send a fix for those HTTP URLs and figured out how to fix the levels thing.

marcoscaceres commented 5 years ago

@mkruisselbrink, just confirming that you are ok with switching off the levels (see above, as I don't think we want to request a new short name).

I've fixed the https issues over on BikeShed https://github.com/tabatkins/bikeshed/pull/1478

mkruisselbrink commented 5 years ago

Yes, thanks. This looks good to me.

marcoscaceres commented 5 years ago

Thanks @mkruisselbrink for confirming. Just ironing out last little things.

marcoscaceres commented 5 years ago

Blocked on https://github.com/tabatkins/bikeshed/issues/1480

marcoscaceres commented 5 years ago

@deniak, final thing is the switching deliverer issue. How do we proceed with that? Anything I can do to help? It’s currently blocking publication of all other specs in the wg.

deniak commented 5 years ago

@marcoscaceres unfortunately, Echidna is not able yet to handle change of deliverer as it requires some IPP changes. You will need to send a publication request to webreq@w3.org at least for that version. Once it has been published, you will be able to publish the next versions with echidna.

siusin commented 5 years ago

@deniak Ok, I'll do that.

Do we need to republish all the WebPlatform specs under WebApps WG?

deniak commented 5 years ago

yeah, Echidna will reject your document if it changes deliverers

siusin commented 5 years ago

All right, in that case, I'll send a pubreq that includes all the specs next Monday :)

marcoscaceres commented 5 years ago

Filed https://github.com/w3c/webappswg/issues/7 about republishing ... will file bugs for the other specs.