Re: Pubrules: Use https for /TR documents
Tobie Langel <[email protected]> Mon, 01 Aug 2016 11:50:30 +0100
| Newsgroups | gmane.org.w3c.specifications |
|---|---|
| Message-ID | <1470048630.2963881.682437865.19D6999D@webmail.messagingengine.com> |
This is a multi-part message in MIME format. --_----------=_147004863029638813 Content-Transfer-Encoding: 7bit Content-Type: text/plain On Mon, 1 Aug 2016, at 10:20, Mike West wrote: > On Mon, Aug 1, 2016 at 9:14 AM, Denis Ah-Kang <[email protected]> wrote: >> The day has finally come. With the official release of the new >> pubrules [1], we now require people to switch the TR links to https. >> The spec generators like Bikeshed and Respec have been updated to >> handle >> that switch so if you are using these tools, you probably have >> nothing >> to do. >> As usual, if you want to make sure your documents are ready to be >> published, you should check them with pubrules [2]. >> >> Feel free to report issues on irc (#pub) or github [3]. > > Thanks for getting this done! > > I filed https://github.com/tabatkins/bikeshed/issues/767 against > Bikeshed to correct one error I found (and update WebAppSec's > templates), but was otherwise able to publish an update to > https://www.w3.org/TR/CSP3/ this morning without issue. And the latest update of CSP3 showed up as expected in Specref: http://www.specref.org/?q=CSP3 Sounds like we're all good on the Specref side. --tobie --_----------=_147004863029638813 Content-Transfer-Encoding: 7bit Content-Type: text/html <!DOCTYPE html> <html> <head> <title></title> </head> <body><div>On Mon, 1 Aug 2016, at 10:20, Mike West wrote:<br></div> <blockquote type="cite"><div dir="ltr"><div>On Mon, Aug 1, 2016 at 9:14 AM, Denis Ah-Kang <span dir="ltr"><<a href="mailto:[email protected]">[email protected]</a>></span> wrote:<br></div> <div><div defang_data-gmailquote="yes"><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex;" defang_data-gmailquote="yes"><div>The day has finally come. With the official release of the new<br></div> <div> pubrules [1], we now require people to switch the TR links to https.<br></div> <div> The spec generators like Bikeshed and Respec have been updated to handle<br></div> <div> that switch so if you are using these tools, you probably have nothing<br></div> <div> to do.<br></div> <div> As usual, if you want to make sure your documents are ready to be<br></div> <div> published, you should check them with pubrules [2].<br></div> <div> <br></div> <div> Feel free to report issues on irc (#pub) or github [3].<br></div> </blockquote><div><br></div> <div>Thanks for getting this done!<br></div> <div><br></div> <div>I filed <a href="https://github.com/tabatkins/bikeshed/issues/767">https://github.com/tabatkins/bikeshed/issues/767</a> against Bikeshed to correct one error I found (and update WebAppSec's templates), but was otherwise able to publish an update to <a href="https://www.w3.org/TR/CSP3/">https://www.w3.org/TR/CSP3/</a> this morning without issue.<br></div> </div> </div> </div> </blockquote><div><br></div> <div>And the latest update of CSP3 showed up as expected in Specref: <a href="http://www.specref.org/?q=CSP3">http://www.specref.org/?q=CSP3</a><br><br>Sounds like we're all good on the Specref side.</div> <div><br></div> <div>--tobie<br></div> </body> </html> --_----------=_147004863029638813--