On Tue, Jan 3, 2017 at 3:22 PM, Amber "Hawkie" Brown < email@example.com> wrote:
We have, in the past, fixed up historic NEWS files in later releases (e.g. the one which removed 2.6 support). We could always roll these changes into a post1, but, that seems like a lot of effort. Maybe we could put errata on the blog?
With a link to the blog post in the NEWS file? Cold checking blog was below "read git history and try to correlate with the issue tracker" on my list of how to track down this change.