api_minimum_version not been bumped.

[Gary van der Merwe]

On Mon, Sep 28, 2009 at 8:48 PM, Martin Pool <mbp at canonical.com> wrote:
> I'm curious too whether the minimum_api_version has actually been
> useful for you in general, as opposed to just checking the actual
> bzrlib version.

I guess not.

For qbzr we want to define a required minimum version of bzr, but not
a maximum version. e.g. qbzr 0.15 will require bzr >= 1.18. We won't
have a required maximum for 2 reasons:
* Because this is seems to be a BIG irritation for users when they
upgrade bzr. It also prevents users from testing qbzr with new
versions of bzr, and hence submitting us bug reports, and hence
getting the bugs fixed.

* While new qbzr code often does not work with old bzr code (the
latest qbzr trunk requires a new version of the ui_factory code), old
qbzr code often work with new bzr code. Luks pointed out to me the rev
1 or qbzr, which contains a implementation of qcommit, works perfectly
with the latests version of bzr.


minimum_api_version I guess would be helpful if we defined a max
required version (because we would have to update the required
versions less often,) but since we only have a minimum bzr version,
this is not the case. So I'm going to actually just check bzrlib's
version_info, and not api_minimum_version, in which case the initial
point of this mail thread is invalid.

Gary