)]}'
{"resolutions/20140402-defcore-designated-sections-guidelines":[{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"3ba945d12d4310954f78d7e6ba1066fc9ff8bc02","unresolved":false,"context_lines":[{"line_number":2,"context_line":"for \"designated sections\" of code, as part of the DefCore effort."},{"line_number":3,"context_line":""},{"line_number":4,"context_line":"Sections of code should generally be DESIGNATED when:"},{"line_number":5,"context_line":"- code provides the project API, or"},{"line_number":6,"context_line":"- code is shared and provides common functionality for all options, or"},{"line_number":7,"context_line":"- code implements logic that is critical for cross-platform operation"},{"line_number":8,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAWH%2F9vpA%3D","line":5,"updated":"2014-04-02 12:48:42.000000000","message":"indicate external API only?","commit_id":"2942ad0773c531986ec78566e328101f89fd31ea"},{"author":{"_account_id":616,"name":"Mark Washenberger","email":"mark.washenberger@markwash.net","username":"markwash"},"change_message_id":"96f8dc35193d0175508db9722ff4011ab1b7d313","unresolved":false,"context_lines":[{"line_number":2,"context_line":"for \"designated sections\" of code, as part of the DefCore effort."},{"line_number":3,"context_line":""},{"line_number":4,"context_line":"Sections of code should generally be DESIGNATED when:"},{"line_number":5,"context_line":"- code provides the project API, or"},{"line_number":6,"context_line":"- code is shared and provides common functionality for all options, or"},{"line_number":7,"context_line":"- code implements logic that is critical for cross-platform operation"},{"line_number":8,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAWH%2F9tf8%3D","line":5,"in_reply_to":"AAAAWH%2F9vaU%3D","updated":"2014-04-02 16:30:32.000000000","message":"Just curious, is REST really a required component of these guidelines? What if a project had an external RPC API, would the guidelines need to be any different?","commit_id":"2942ad0773c531986ec78566e328101f89fd31ea"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"36972e51a199dcca4e3596280f3a57f1220008d9","unresolved":false,"context_lines":[{"line_number":2,"context_line":"for \"designated sections\" of code, as part of the DefCore effort."},{"line_number":3,"context_line":""},{"line_number":4,"context_line":"Sections of code should generally be DESIGNATED when:"},{"line_number":5,"context_line":"- code provides the project API, or"},{"line_number":6,"context_line":"- code is shared and provides common functionality for all options, or"},{"line_number":7,"context_line":"- code implements logic that is critical for cross-platform operation"},{"line_number":8,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAWH%2F9vaU%3D","line":5,"in_reply_to":"AAAAWH%2F9vpA%3D","updated":"2014-04-02 13:20:14.000000000","message":"Yes, I think we should be explicit here and say \"external REST API\" because that\u0027s what we mean but it isn\u0027t clear without the historical context.","commit_id":"2942ad0773c531986ec78566e328101f89fd31ea"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"36972e51a199dcca4e3596280f3a57f1220008d9","unresolved":false,"context_lines":[{"line_number":9,"context_line":"Sections of code should generally NOT be DESIGNATED when:"},{"line_number":10,"context_line":"- code interfaces to vendor-specific functions, or"},{"line_number":11,"context_line":"- project design explicitly intended this section to be replaceable, or"},{"line_number":12,"context_line":"- code extends the API in a new or different way, or"},{"line_number":13,"context_line":"- code is deprecated, or expected to be deprecated"},{"line_number":14,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAWH%2F9vXs%3D","line":12,"updated":"2014-04-02 13:20:14.000000000","message":"\"external REST API\"","commit_id":"2942ad0773c531986ec78566e328101f89fd31ea"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"3ba945d12d4310954f78d7e6ba1066fc9ff8bc02","unresolved":false,"context_lines":[{"line_number":10,"context_line":"- code interfaces to vendor-specific functions, or"},{"line_number":11,"context_line":"- project design explicitly intended this section to be replaceable, or"},{"line_number":12,"context_line":"- code extends the API in a new or different way, or"},{"line_number":13,"context_line":"- code is deprecated, or expected to be deprecated"},{"line_number":14,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAWH%2F9vnw%3D","line":13,"updated":"2014-04-02 12:48:42.000000000","message":"or expected to be deprecated within a single release (I sense we need a time period to indicate how long deployers have to get off of to-be-deprecated code)","commit_id":"2942ad0773c531986ec78566e328101f89fd31ea"},{"author":{"_account_id":1561,"name":"Russell Bryant","email":"rbryant@redhat.com","username":"russellb"},"change_message_id":"b8e35328b7523d43a8a9321ae4d73a2217bbd04b","unresolved":false,"context_lines":[{"line_number":10,"context_line":"- code interfaces to vendor-specific functions, or"},{"line_number":11,"context_line":"- project design explicitly intended this section to be replaceable, or"},{"line_number":12,"context_line":"- code extends the API in a new or different way, or"},{"line_number":13,"context_line":"- code is deprecated, or expected to be deprecated"},{"line_number":14,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAWH%2F9vPQ%3D","line":13,"in_reply_to":"AAAAWH%2F9vTg%3D","updated":"2014-04-02 13:24:03.000000000","message":"agree that it seems better to leave the deprecation timeline detail elsewhere.  As far as principles go, \"don\u0027t require code that is deprecated\" seems to be enough.","commit_id":"2942ad0773c531986ec78566e328101f89fd31ea"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"36972e51a199dcca4e3596280f3a57f1220008d9","unresolved":false,"context_lines":[{"line_number":10,"context_line":"- code interfaces to vendor-specific functions, or"},{"line_number":11,"context_line":"- project design explicitly intended this section to be replaceable, or"},{"line_number":12,"context_line":"- code extends the API in a new or different way, or"},{"line_number":13,"context_line":"- code is deprecated, or expected to be deprecated"},{"line_number":14,"context_line":""}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAWH%2F9vTg%3D","line":13,"in_reply_to":"AAAAWH%2F9vnw%3D","updated":"2014-04-02 13:20:14.000000000","message":"According to https://etherpad.openstack.org/p/DefCoreTestCriteria tests are \"required stable for \u003e2 releases\". I don\u0027t know if that implies a change to our internal code deprecation policy (maybe only in cases where it changes the behavior covered by a test?). In any case, I\u0027m not sure how many different places we want to describe the deprecation timeline. If we simply say here we don\u0027t consider deprecated code to be core, can we cover the deprecation policy elsewhere?","commit_id":"2942ad0773c531986ec78566e328101f89fd31ea"}]}