On Tue, Aug 08, 2017 at 08:50:55AM -0500, Eric Blake wrote: > On 08/07/2017 07:08 PM, John Snow wrote: > > > > > > On 08/03/2017 12:33 PM, Eric Blake wrote: > >> Not sure if this should go through Kevin's block tree, Paolo's > >> miscellaneous patches, or if I should just do a pull request > >> myself (since patch 4 includes a change to qemu-nbd) > >> > > > > > Nothing to keep the commands from going out of order again, it looks > > like -- can this be added as a comment or otherwise scripted as a > > ./hey_it_looks_like_you_are_about_to_release_qemu.sh script that makes > > sure we've dotted the 'i's and crossed the 't's? > > We don't add subcommands to qemu-img all that frequently; I think a > comment is okay without having to figure out where to script things. > > > > > Lastly, Didn't we fix the certificate issue? (I thought Jeff had) -- and > > even if not, it's still the correct address to send people to IMO. Let > > people report to us if the SSL certificate appears to be broken. > > That can be a followup-patch. >
Probably no need for one, really. We force redirect to SSL, so the http:// versions will still end up https://. And to confirm - the SSL certificates are now all in order. The issue on the website I think you were referencing in that commit message is because we still had two URL resources pulling in non-ssl assets (Google fonts, and jquery), so browsers blocked those mixed requests. But that has been updated. -Jeff
