Comment 7 for bug 1393952
Revision history for this message
| Julian Edwards (julian-edwards) wrote Re: [Bug 1393952] Re: feature req: api call to get current running version of maas | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
On Wednesday 19 Nov 2014 00:00:40 you wrote:
> > That doesn't answer the question of versions though, which may change
> > when capabilities do not. There may be some other semantic change
> > which is implicit in a version bump.
>
> Explicitly signalling semantic changes is what that view is meant for.
> It was designed so that people would not use version numbers and not
> come to depend on implicit behaviour changes.
>
> Capabilities can be turned on and off. Version numbers can only move
> forwards. There's no way to signal via a version number that something
> that once was available is no longer available. Instead, all clients
> must be updated.
>
> > We can add the version/revision info in the capabilities structre
> > easily enough.
>
> Please see if you can avoid doing that.
Honestly, I can see the benefit of both approaches. If we provide both, is it
*that* bad? People using the API are not stupid and will understand that
looking at the capability is better, but on occasion the version will be more
useful.