© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hello Jeremy Staley,
1. The reason of why I have not add the code to glance (including test case) for support both 0.1.4's and 0.1.7 like the approach you proposed "switching on the package version info to determine which behavior it should expect" is that this dynamic logic will causes glance-{api, registry} API provided non-consistent result to end user, it says when deployer using 0.1.7 then the "changes-since" filter param for the image-list API will support yyyy-mm-dd param (no time part), but when deployer using 0.1.4 then that same request will raise an exception. This's unreasonable to me.
2. Your concern "you're proposing everyone should start to require a newer version than is present in Ubuntu." is make sense to me. So there is a second choice to fixes this issue (even I personally don't like go this way), as I mentioned in my comments #3 we can cap or skip iso8601 version 0.1.7 (<0.1.7 or !=0.1.7), do you think this is OK to you/other projects?
Any thoughts others?