- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Jun 2018 11:25:07 +0000
- To: public-webauthn@w3.org
>so I spose the working model that we have now is a reasonable compromise: where some of us are using up-to-date bikeshed locally and will catch leading-edge bikeshed-evolution-induced warnings and errors and we can figure them out without the mainline editors' draft spec travisCI builds gratuitously breaking. It turns out it's possible to do both in the same Travis build, but allow the leading-edge job to fail without failing the build. I'm not entirely sure how visible any failures in that would be - perhaps you'd need to explicitly go to the Travis build status page to see them - but I think it might be useful. PR incoming. -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/issues/936#issuecomment-396210678 using your GitHub account
Received on Monday, 11 June 2018 11:25:10 UTC