X-RT-Original-Encoding: utf-8 Date: Tue, 17 Oct 2017 20:36:46 +0000 X-RT-Incoming-Encryption: Not encrypted Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by bugs.isc.org (Postfix) with ESMTPS id 895FFD78B0A for ; Tue, 17 Oct 2017 20:36:46 +0000 (UTC) Received: by bikeshed.isc.org (Postfix, from userid 10292) id 1CB3F216C1E; Tue, 17 Oct 2017 20:36:46 +0000 (UTC) From each@isc.org Tue Oct 17 20:36:46 2017 CC: To: "Stephen Morris via RT" content-type: text/plain; charset="utf-8" Content-Disposition: inline Message-ID: <20171017203646.GA77972@isc.org> From: "Evan Hunt" Subject: Re: [ISC-Bugs #46302] Documentation issues in 9.12.0b1 X-Original-To: bind9-public@bugs.isc.org In-Reply-To: MIME-Version: 1.0 Delivered-To: bind9-public@bugs.isc.org User-Agent: Mutt/1.5.23 (2014-03-12) References: X-RT-Interface: Email Return-Path: RT-Message-ID: Content-Length: 2739 > README > === README is generated from README.md. Formatting suggestions, such as the one about the semicolon and the period, are unfortunately not going to be addressable without fixing pandoc. I would probably simplify things to use the line numbers from README.md instead of README when referring to problems, but of course that requires pulling it from the tarball or git repo, though. Or you could cut and paste the context of the change you want made, so it's easier to me to find the place. I'll take care of the suggestions that I can. > RELEASE-NOTES-bind-9.12.0b1.txt > === > (5) The version should be 9.12.0b1, not 9.12.0 (although the version is > correct for the final release). It says that these are the release notes for version 9.12.0b1, and that 9.12.0 is the version that's under development. IMHO it's correct and understandable as it is. > (53) The cache has been removed, but the acache-enable and > acache-cleaning-interval options have been deprecated? Does this mean > that they are still accepted in the configuration file but no longer have > an effect? If so, this should be stated. They generate a warning, but not a failure, when used. If that isn't clear enough, please suggest other wording. > (60) additional-from-cache and additional-from-auth have been deprecated. > With reference to the previous comment, does this mean they would (but > will be removed in a future release) or that they no longer have an > effect but are retained for configuration file compatibility? Correct. > (225) We have added the new-zones-directory keyword. If not implemented > in 9.12.0, a future version of BIND 9 should check the directory pointed > to by new-zones-directory (if specified) is writable. Created ticket 46308. > > RELEASE-NOTES-bind-9.12.0b1.pdf > === > New Features/"nsec3hash -r": the word NSEC3PARAM extends into the right-hand margin instead of triggering a new line. Again, unfortunately, I'm not sure what we can do about latex bugs. This might get better if and when we switch to a different documentation system. > Bv9ARM.pdf > === > (Page 62) In the description of print-time, the values "yes" and "no" in the paragraph should be in the same font as the other options; at the moment they are in bold. They're while the others are