PSC Vote: Keeping old NEWS in the news file for non-EOL versions

[Greg Troxel]

> About the only pieces of news I would be willing to dispense with are
> those occasional orphan alpha/beta release blocks which could be
> either removed, if they are just memorializing bug fixes, or rolled
> into the appropriate final release if they are “important”.

Agreed.  When 3.6.0 final comes out, I think it's just as well that
alpha/beta stuff is gone, and good that there is one block that
describes all user-visible (where users engage in compliation from
source, so compiler requirements changes, etc.!) changes since 3.5.0 (or
the 3.5.0 branchpoint).

Personally I'd just write the 3.6.0 news for the first alpha, beta or rc
(whichever comes first), and then adjust it and change the headline in
the future.   Basically my view is that these are drafts for 3.6.0 and
once 3.6.0 is released, they are not of long-term interest.

> And yeah, like strk I think bug fix entries are important and again,
> since they only appear in patch releases, and only on the relevant
> stable branches, they are correctly ring fenced for the right
> people. If you are on a stable branch, you care about bug fixes in
> that branch.

I don't really mind that bugfixes are there.  I'd prefer they'd be
clearly separated, after the real NEWS, so they're ignorable.