API freeze for 2.4 and trunk open for 2.5

[Robert Collins]

On Mon, Jul 11, 2011 at 9:30 PM, Martin Pool <mbp at canonical.com> wrote:
> I think when this was put in Robert had the idea of defining separate
> api versions per module or even per class, but I think in Python that
> would be more trouble than it's worth, because we'd be highly likely
> to miss dependencies that could only be found by testing.
>
> In short I suggest just setting api_minimum_version = version_info[:2]
> and be done.

So IIRC there were two separate dimensions here, one was, as you say,
handling regions of the API which haven't changed, the other was, if
we don't break compat, being able to be compatible with older
releases.

I guess the new API compatibility policy for development speaks to the
latter point, and the concept of submodules not breaking API in a
release hasn't really been made use of.

Anyhow, thats just data - I've no objection to this being simplified or removed.

-Rob