Shawn Walker wrote:
Tom Mueller wrote:
All I'm looking for is that we acknowledge that this really is an
incompatible change to ImageInterface. We have to acknowledge
incompatible changes if we are to avoid them in the future.
As you've pointed out, the API has never clearly defined what a
'progresstracker' is, and only asks for one. And as I already
mentioned, yes, the usage of the progresstracker of the API could be
considered to be changing incompatibly.
However, the catch is that the "incompatibly" part is wholly dependent
on the definition of the ProgressTracker class, whether a client is even
using that class.
Despite all of this, in terms of pkg.client.api.version, the api is
*not* incompatibly changing. I'm not willing to increment the minimum
pkg.client.api.version because of a lack of clarity in the documentation
or architecture of the progresstracker or because of the need for
clarification in the API documentation.
As currently defined by pkg.client.api, this change is not an
incompatible one. If that definition is wrong, then it can always be
corrected.
After a team discussion about this earlier today, the consensus was that:
* this is an incompatible change, but not one that the client api
currently accounts for or cares about, and thus is not reflected in the
pkg.client.api.version or in docs/client_api_versions.txt
* that pkg.client.api does not yet fully represent a completely boundary
between producer and consumer
* that, eventually, this will need to be part of the client api so that
there are clear boundaries
Bug 8343 was filed to address some of the issues raised.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
