[maemo-developers] Why can't Nokia/Maemo release consistent versions for an upgrade?

[From: tz]

Over the past few months I've been asking to the point of annoyance
what to do about bluez-utils-test since it is Maemo supported,
therefore has dependencies on the official version.

So with the most recent upgrade my application is now completely uninstallable.

On the tablet after the upgrade is:

bluez-utils-3.28-0osso6.

The only thing in any repository (including source) is labeled osso7!

If only for the GPL, where is the exact source corresponding to osso6?

I can't (without falsifying versions) build an osso6 version of
bluez-utils-test.

Upgrading bluez-utils to osso7 breaks osso-software-version-rx44
(which is dependent on osso6).  Perhaps this is OK, but I'd rather not
force all users to have to uninstall this metapackage (does it happen
automatically)?

I'm also having problems  with the SDK - I can't even do apt-get
source to get anything but osso4 there - I have to download the
components manually.

Worse, no one can install the most recent version of my program since
for some reason application manager can't resolve the dependencies.
The program is only available as a deb (at http://www.zdez.org), but
it sits there and lists python2.5-gnome and python2.5-bluez in the
Problems tabs.  They aren't "user" so can't be installed
manually/separately, but are in extras.  apt-get install will work
from the command line, but application manager won't.

Is there any way Nokia might release an upgrade of such magnitude to a
-devel area first so we can test it and undo any breakage BEFORE the
users upgrade and break everything?

Is there a reason they aren't providing source to the GPL components
of the upgrade?  Only older or newer ones (the latter for the sdk)?

I am really trying hard to play by the rules, but it seems futile
since Nokia comes out of the bluez with upgrades that break everything
I'm doing and aren't easily fixed.