On May 24, 2013, at 7:09 AM, Brett Cannon <brett@python.org> wrote:
I think that's overly complicated. I don't see why we need anything more than simply NEWS/3.4, NEWS/3.3, etc. and just split the files per feature release since that's the interest (and merge) boundary.
+1 from me. This is a straight-forward solution to the merge problem
and it recognizes that users don't really need to look across merge