Right now any warning causes the book to fail to build. This is a lovely way for things to be but as part of the transition to Asciidoctor we'd like to migrate our docs to be more "asciidoctor native". I propose we manage this process by enhancing the warnings infrastructure to allow a per-book configuration to ignore some warnings with a "ratchet" that we can "tighten" when we fix warnings. The idea here is that some book will have some warnings from the Asciidoctor conversion and those warnings shouldn't cause the book to fail to build. If someone adds docs that would create additional warnings the build should fail. If someone fixes some warnings they should be forced to "mark them fixed" so they never get worse again.
Right now any warning causes the book to fail to build. This is a lovely way for things to be but as part of the transition to Asciidoctor we'd like to migrate our docs to be more "asciidoctor native". I propose we manage this process by enhancing the warnings infrastructure to allow a per-book configuration to ignore some warnings with a "ratchet" that we can "tighten" when we fix warnings. The idea here is that some book will have some warnings from the Asciidoctor conversion and those warnings shouldn't cause the book to fail to build. If someone adds docs that would create additional warnings the build should fail. If someone fixes some warnings they should be forced to "mark them fixed" so they never get worse again.