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

[Regina Obe]

> > 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”.
> 

You and victory bah.  You want to put back the 3000 lines of precious text in 3.7.0 or shall we just say
from this point forward we won't be removing precious history? 

> 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.
>

Yah I'm fine with removing those after they are done.  On alpha/beta/rc I try to put only changes (not part of patch releases) since the last alpha/beta/rc , followed by the full release notes in a 3.6.0dev <no date) for example because those will never
go in release notes of .0 if they are just bug fixes and I think those are important to have in RCs/betas/alphas otherwise
how will testers diligently testing those rcs/beta/alphas know what's changed?  And I assume the only people that care about
alphas/betas/rcs are those that have been testing along the way.


Can we at least agree to remove it from the docs (e.g. html/pdf), it makes them painlessly long.
For that I'd actually only want the past micros of the version being released.

Thanks,
Regina