)]}'
{"doc/source/index.rst":[{"author":{"_account_id":9420,"name":"Matthew Gilliard","email":"matthew.gilliard@hp.com","username":"gilliard"},"change_message_id":"392b15c7e2ee2130d204d153ee5c7a2196adc579","unresolved":false,"context_lines":[{"line_number":64,"context_line":"     gets in the release notes."},{"line_number":65,"context_line":"   - The deprecation cycle is typically the first client release *after* the"},{"line_number":66,"context_line":"     next *full* Nova server release so that there is at least six months of"},{"line_number":67,"context_line":"     deprecation."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"  2. Once the change is approved, have a member of the `nova-release`_ team"},{"line_number":70,"context_line":"     release a new version of python-novaclient."}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a016987_1457abcb","line":67,"updated":"2015-05-26 13:49:34.000000000","message":"If we\u0027re deciding policy in this patch, then an alternative is: We could make the client change 6 months after the deprecation notice is added, uncoupled from the main release cycle.\n\nOr is there precedent for this already?","commit_id":"9e40e2e99a02dcd405795562fe809e83d33a7ec3"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"67f20ecf14646fafcfc72e8f98c5c2d741f0a2f7","unresolved":false,"context_lines":[{"line_number":64,"context_line":"     gets in the release notes."},{"line_number":65,"context_line":"   - The deprecation cycle is typically the first client release *after* the"},{"line_number":66,"context_line":"     next *full* Nova server release so that there is at least six months of"},{"line_number":67,"context_line":"     deprecation."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"  2. Once the change is approved, have a member of the `nova-release`_ team"},{"line_number":70,"context_line":"     release a new version of python-novaclient."}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a016987_2fbed0d4","line":67,"in_reply_to":"7a016987_1457abcb","updated":"2015-05-26 14:07:36.000000000","message":"There isn\u0027t precedent.  We have other deprecated (renamed) CLIs in novaclient but we haven\u0027t laid down a policy for removing deprecated CLIs/APIs from the client before, so this is the first time.\n\nThe problem with a 6 month deprecation cycle in the client, as I see it, is release notes - the clients don\u0027t really have release notes like the server releases do.  We have a schedule for when the server releases come out and people should be looking at those, but not so much for the client releases - those just go to the mailing list.\n\nSo I wanted ample time to get this in the release notes for Liberty and then have enough time in a full release (M) to deprecate before removal.\n\nCarrying this code isn\u0027t too much of a problem right now, but breaking people using these CLIs/APIs would be costly if done too soon so I\u0027m inclined to err on the side of being conservative in the deprecation cycle here.","commit_id":"9e40e2e99a02dcd405795562fe809e83d33a7ec3"},{"author":{"_account_id":9420,"name":"Matthew Gilliard","email":"matthew.gilliard@hp.com","username":"gilliard"},"change_message_id":"56d2b9d936aa52467c259b472fea4eaa70d5f8e6","unresolved":false,"context_lines":[{"line_number":64,"context_line":"     gets in the release notes."},{"line_number":65,"context_line":"   - The deprecation cycle is typically the first client release *after* the"},{"line_number":66,"context_line":"     next *full* Nova server release so that there is at least six months of"},{"line_number":67,"context_line":"     deprecation."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"  2. Once the change is approved, have a member of the `nova-release`_ team"},{"line_number":70,"context_line":"     release a new version of python-novaclient."}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a016987_cf017c3b","line":67,"in_reply_to":"7a016987_2fbed0d4","updated":"2015-05-26 14:15:28.000000000","message":"That\u0027s fine - it\u0027s easy and sensible to err on the side of long deprecation times. The release-note point is good, too.","commit_id":"9e40e2e99a02dcd405795562fe809e83d33a7ec3"},{"author":{"_account_id":679,"name":"Kevin L. Mitchell","email":"klmitch@mit.edu","username":"klmitch"},"change_message_id":"e04c412ac55ca4e36fc6869fb0a913851979a50b","unresolved":false,"context_lines":[{"line_number":77,"context_line":"     development. The current version of python-novaclient at the time was"},{"line_number":78,"context_line":"     2.25.0. Once the change was merged, python-novaclient 2.26.0 was released."},{"line_number":79,"context_line":"     Since there was less than six months before 2015.2 would be released, the"},{"line_number":80,"context_line":"     deprecation cycle ran through the 2016.1 Nova server release."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Indices and tables"},{"line_number":83,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a016987_1f41fb39","line":80,"updated":"2015-05-26 18:17:36.000000000","message":"This is great for the commands; I wonder if we should say something about the API, though?","commit_id":"9e40e2e99a02dcd405795562fe809e83d33a7ec3"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"568fab279f2db9da925ce1505d8ef49dd5ee3dfa","unresolved":false,"context_lines":[{"line_number":77,"context_line":"     development. The current version of python-novaclient at the time was"},{"line_number":78,"context_line":"     2.25.0. Once the change was merged, python-novaclient 2.26.0 was released."},{"line_number":79,"context_line":"     Since there was less than six months before 2015.2 would be released, the"},{"line_number":80,"context_line":"     deprecation cycle ran through the 2016.1 Nova server release."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Indices and tables"},{"line_number":83,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a016987_ed8ac019","line":80,"in_reply_to":"7a016987_1f41fb39","updated":"2015-05-27 21:38:36.000000000","message":"So, I thought about that when writing this, but I\u0027m not aware of any other python APIs within novaclient that we\u0027d be removing, so would we be documenting a process for a thing that\u0027s only going to happen once?  Since we can\u0027t drop nova APIs, that wouldn\u0027t happen in the client - so the only thing we can drop is using other project\u0027s APIs, and I\u0027m not aware of anything else in the client that does that besides the problematic volume API stuff.","commit_id":"9e40e2e99a02dcd405795562fe809e83d33a7ec3"},{"author":{"_account_id":679,"name":"Kevin L. Mitchell","email":"klmitch@mit.edu","username":"klmitch"},"change_message_id":"68eed179adab5bd3db70cc88cc9a3021a5ed3fb9","unresolved":false,"context_lines":[{"line_number":77,"context_line":"     development. The current version of python-novaclient at the time was"},{"line_number":78,"context_line":"     2.25.0. Once the change was merged, python-novaclient 2.26.0 was released."},{"line_number":79,"context_line":"     Since there was less than six months before 2015.2 would be released, the"},{"line_number":80,"context_line":"     deprecation cycle ran through the 2016.1 Nova server release."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Indices and tables"},{"line_number":83,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7a016987_96457c44","line":80,"in_reply_to":"7a016987_ed8ac019","updated":"2015-05-28 15:51:33.000000000","message":"I\u0027m not certain that we \"can\u0027t\" drop nova APIs, although I agree with you that it is highly unlikely; the deprecation cycle would probably be 2 years minimum for something like that.  However, I can imagine replacing cruddy nova APIs with pretty ones.  (Can\u0027t really think of any good examples at the moment…beyond something like tasks, which wouldn\u0027t actually eliminate the existing resources :)  That said, it\u0027s just a thought; we can always add that in a later change if we decide such a policy is warranted.","commit_id":"9e40e2e99a02dcd405795562fe809e83d33a7ec3"}]}