"what's new" document

[Robert Collins]

On Wed, Aug 18, 2010 at 7:59 PM, Ben Finney <ben+bazaar at benfinney.id.au> wrote:
> Robert Collins <robertc at robertcollins.net> writes:
>
>> Firstly, this is harder on users. They have to chase points - a change
>> in 2.3 which started in 2.0 will require three additional lookups -
>> assuming only one point release at each point.

*pointers*.

> I don't understand what this means. What is a “point” in your
> terminology? How are points different from changes?
>
> I would only expect the “What's New” document to describe changes since
> the previous released “What's New” document. If I'm a user upgrading
> from a version that's out of date by several versions, I read the
> “What's New” document for each version released since then.

This isn't talking about whats new, its talking about NEWS, as per
Martins email.
If you're upgrading from 2.3.0 to 2.3.1 in my example, you also need to read
2.2.5->2.2.6     (in NEWS-2.2, referred to by the 2.3.1 NEWS)
2.1.11->2.1.12 (in NEWS-2.1, referred to by 2.2.6 NEWS and maybe 2.3.1 NEWS)
2.0.17->2.0.18 (in NEWS-2.0, referred to by 2.1.12 NEWS, maybe 2.2.6
and 2.3.1 depending on what Martin has in mind)

-Rob