3 release policy

[M Farkas-Dyck]

On 21/10/2015, John Wiegley <johnw at newartisans.com> wrote:
> Since warnings are intended to mean "This could be a problem, but might not
> be, be warned", there should be a case-by-case way of answering it and
> saying
> "I know this isn't a problem". I think a pragma for disabling a particular
> warning at certain code location would be a good addition to our current
> disabling mechanisms?

I hope we won't warn about unused warning suppression...