)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6d1bb3bc3114f838e0ef4ad060a505dd9822d404","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"479f3472_0988ff86","updated":"2022-03-08 23:07:58.000000000","message":"few comments, mainly 1 comment where I got confused if deprecation is for 1 tick release or 2 tick release. explained inline. ","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":30491,"name":"Radosław Piliszek","display_name":"Radek","email":"radek@piliszek.it","username":"yoctozepto","status":"self-employed techologist, collaborating mostly with 7bulls.com"},"change_message_id":"87717b4064d27b5b66460a4a600e881be49b72dd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e353ec7e_bddc6e3b","updated":"2022-03-07 17:16:23.000000000","message":"thank you for this! some nits to resolve inline","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":30491,"name":"Radosław Piliszek","display_name":"Radek","email":"radek@piliszek.it","username":"yoctozepto","status":"self-employed techologist, collaborating mostly with 7bulls.com"},"change_message_id":"c13974a610ac4698460c49be0be996bdfabc3e77","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"84707c07_3d020c21","updated":"2022-03-09 16:49:57.000000000","message":"even cooler!","commit_id":"1b3ba23cb3c7a3ee5d5f2b7dc3f9ea9ff15f4841"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"867941c6e0895fefa362e139fe11ddd2f8a68793","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"17a04264_1e56f105","updated":"2022-03-09 17:02:02.000000000","message":"lgtm thanks. It is clear and covering most of the cases and if there is any specific project wise case that can be added later or in project side documents.","commit_id":"1b3ba23cb3c7a3ee5d5f2b7dc3f9ea9ff15f4841"}],"doc/source/deprecation.rst":[{"author":{"_account_id":30491,"name":"Radosław Piliszek","display_name":"Radek","email":"radek@piliszek.it","username":"yoctozepto","status":"self-employed techologist, collaborating mostly with 7bulls.com"},"change_message_id":"87717b4064d27b5b66460a4a600e881be49b72dd","unresolved":true,"context_lines":[{"line_number":42,"context_line":"   continues to work as-is)."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"#. A migration path will be documented for current users of the feature. An"},{"line_number":45,"context_line":"   email thread will be started on openstack-operators to determine how many"},{"line_number":46,"context_line":"   people are using the deprecated API or feature, and how costly the migration"},{"line_number":47,"context_line":"   plan is to implement. A migration path may be \"stop using that feature\":"},{"line_number":48,"context_line":"   the cost is then very related to the number of people using the feature"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5feef8fd_b14b3005","line":45,"range":{"start_line":45,"start_character":35,"end_line":45,"end_character":54},"updated":"2022-03-07 17:16:23.000000000","message":"openstack-discuss","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"cb9034a279636d062b3f4a8d6828f660fa1bd3ff","unresolved":false,"context_lines":[{"line_number":42,"context_line":"   continues to work as-is)."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"#. A migration path will be documented for current users of the feature. An"},{"line_number":45,"context_line":"   email thread will be started on openstack-operators to determine how many"},{"line_number":46,"context_line":"   people are using the deprecated API or feature, and how costly the migration"},{"line_number":47,"context_line":"   plan is to implement. A migration path may be \"stop using that feature\":"},{"line_number":48,"context_line":"   the cost is then very related to the number of people using the feature"}],"source_content_type":"text/x-rst","patch_set":1,"id":"02641828_adbfc9f8","line":45,"range":{"start_line":45,"start_character":35,"end_line":45,"end_character":54},"in_reply_to":"5feef8fd_b14b3005","updated":"2022-03-07 17:39:50.000000000","message":"Ack","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6d1bb3bc3114f838e0ef4ad060a505dd9822d404","unresolved":true,"context_lines":[{"line_number":56,"context_line":"#. Based on that data, an obsolescence date will be set. At the very"},{"line_number":57,"context_line":"   minimum the feature (or API, or configuration option) should be"},{"line_number":58,"context_line":"   marked deprecated (and still be supported) in the next \"tick\""},{"line_number":59,"context_line":"   release branch, *and* for at least three months linear time.  For"},{"line_number":60,"context_line":"   example, a feature deprecated in the 2023 tick release should still"},{"line_number":61,"context_line":"   appear in the 2024 tick release that stable branch and cannot be"},{"line_number":62,"context_line":"   removed before the beginning of the 2024 tock development cycle."}],"source_content_type":"text/x-rst","patch_set":1,"id":"d8bf1edc_e8b66cc1","line":59,"range":{"start_line":59,"start_character":19,"end_line":59,"end_character":65},"updated":"2022-03-08 23:07:58.000000000","message":"this does not seems to be necessary now because as per tick-\u003etick cycle for deprecation and removal, none of the deprecation to removal can happen within 3 month. This was there as per old model of single cycle deprecation policy when we could deprecate the things at the very end of cycle and remove at the very start of next cycle.","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"e6d19afac19b30c2c35b2eb1418c96e4e9a2f19b","unresolved":true,"context_lines":[{"line_number":56,"context_line":"#. Based on that data, an obsolescence date will be set. At the very"},{"line_number":57,"context_line":"   minimum the feature (or API, or configuration option) should be"},{"line_number":58,"context_line":"   marked deprecated (and still be supported) in the next \"tick\""},{"line_number":59,"context_line":"   release branch, *and* for at least three months linear time.  For"},{"line_number":60,"context_line":"   example, a feature deprecated in the 2023 tick release should still"},{"line_number":61,"context_line":"   appear in the 2024 tick release that stable branch and cannot be"},{"line_number":62,"context_line":"   removed before the beginning of the 2024 tock development cycle."}],"source_content_type":"text/x-rst","patch_set":1,"id":"53a58db8_8c6376af","line":59,"range":{"start_line":59,"start_character":19,"end_line":59,"end_character":65},"in_reply_to":"1da414f0_98f6bd8a","updated":"2022-03-09 15:22:12.000000000","message":"ok, let\u0027s keep it then. +1 on soften it.","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"39fa89650bc893f193636b73576ca40ef23a0d5b","unresolved":false,"context_lines":[{"line_number":56,"context_line":"#. Based on that data, an obsolescence date will be set. At the very"},{"line_number":57,"context_line":"   minimum the feature (or API, or configuration option) should be"},{"line_number":58,"context_line":"   marked deprecated (and still be supported) in the next \"tick\""},{"line_number":59,"context_line":"   release branch, *and* for at least three months linear time.  For"},{"line_number":60,"context_line":"   example, a feature deprecated in the 2023 tick release should still"},{"line_number":61,"context_line":"   appear in the 2024 tick release that stable branch and cannot be"},{"line_number":62,"context_line":"   removed before the beginning of the 2024 tock development cycle."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a1414a7_a75bbd29","line":59,"range":{"start_line":59,"start_character":19,"end_line":59,"end_character":65},"in_reply_to":"53a58db8_8c6376af","updated":"2022-03-09 16:25:46.000000000","message":"Done","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"707660e62c732af72a3d6f67ec1ab719fd238f4b","unresolved":true,"context_lines":[{"line_number":56,"context_line":"#. Based on that data, an obsolescence date will be set. At the very"},{"line_number":57,"context_line":"   minimum the feature (or API, or configuration option) should be"},{"line_number":58,"context_line":"   marked deprecated (and still be supported) in the next \"tick\""},{"line_number":59,"context_line":"   release branch, *and* for at least three months linear time.  For"},{"line_number":60,"context_line":"   example, a feature deprecated in the 2023 tick release should still"},{"line_number":61,"context_line":"   appear in the 2024 tick release that stable branch and cannot be"},{"line_number":62,"context_line":"   removed before the beginning of the 2024 tock development cycle."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1da414f0_98f6bd8a","line":59,"range":{"start_line":59,"start_character":19,"end_line":59,"end_character":65},"in_reply_to":"d8bf1edc_e8b66cc1","updated":"2022-03-09 14:46:23.000000000","message":"Okay, up to you. I left it because it seems to clarify the lack of \"instantaneous non-support\" we discussed at one point. Meaning, the very instant that a tick comes out, we don\u0027t need to immediately consider the outgoing one unsupported. Perhaps I can just soften this to \"and at least until after the following is released...\" or something.","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6d1bb3bc3114f838e0ef4ad060a505dd9822d404","unresolved":true,"context_lines":[{"line_number":57,"context_line":"   minimum the feature (or API, or configuration option) should be"},{"line_number":58,"context_line":"   marked deprecated (and still be supported) in the next \"tick\""},{"line_number":59,"context_line":"   release branch, *and* for at least three months linear time.  For"},{"line_number":60,"context_line":"   example, a feature deprecated in the 2023 tick release should still"},{"line_number":61,"context_line":"   appear in the 2024 tick release that stable branch and cannot be"},{"line_number":62,"context_line":"   removed before the beginning of the 2024 tock development cycle."},{"line_number":63,"context_line":"   Ideally, features should not be deprecated in a tock release"},{"line_number":64,"context_line":"   because operators deploying only tick releases should not be"},{"line_number":65,"context_line":"   required to read release notes for releases they are not required"}],"source_content_type":"text/x-rst","patch_set":1,"id":"85176eb9_cfea6001","line":62,"range":{"start_line":60,"start_character":1,"end_line":62,"end_character":67},"updated":"2022-03-08 23:07:58.000000000","message":"is this correct or just me reading it confusing?\n\nFrom the above example I am reading like we we need to keep things deprecated for two tick release and remove in tock release after the 2nd tick (feature deprecated in 2023 tick ... cannot be removed before 2024 tock development)?\n\nLet me know if I am correct with below understanding:\n\n- No deprecation or removal in tock release\n- Any feature deprecated in tick-1 release has to be supported-but-deprecated in stable/tick-1 and stay same in next tock release. It can be removed in start of the tick-2 development cycle. So users see the deprecation notes in tock-1 and before upgrading to tick-2 they take care of it.\n\nIf my understanding is correct then we can rephrase it to something like\n\n example, a feature deprecated in the 2023 tick release should still\n   appear in the 2023 tick release and stable/\u003ctick\u003e branch and cannot be\n   removed before the beginning of the 2024 tick development cycle.","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"707660e62c732af72a3d6f67ec1ab719fd238f4b","unresolved":true,"context_lines":[{"line_number":57,"context_line":"   minimum the feature (or API, or configuration option) should be"},{"line_number":58,"context_line":"   marked deprecated (and still be supported) in the next \"tick\""},{"line_number":59,"context_line":"   release branch, *and* for at least three months linear time.  For"},{"line_number":60,"context_line":"   example, a feature deprecated in the 2023 tick release should still"},{"line_number":61,"context_line":"   appear in the 2024 tick release that stable branch and cannot be"},{"line_number":62,"context_line":"   removed before the beginning of the 2024 tock development cycle."},{"line_number":63,"context_line":"   Ideally, features should not be deprecated in a tock release"},{"line_number":64,"context_line":"   because operators deploying only tick releases should not be"},{"line_number":65,"context_line":"   required to read release notes for releases they are not required"}],"source_content_type":"text/x-rst","patch_set":1,"id":"8c82ad7a_2f425eda","line":62,"range":{"start_line":60,"start_character":1,"end_line":62,"end_character":67},"in_reply_to":"85176eb9_cfea6001","updated":"2022-03-09 14:46:23.000000000","message":"No, you\u0027re right. I think I was just doing the math here (changing dates and release names from where they were in the original document) without much thought.","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"39fa89650bc893f193636b73576ca40ef23a0d5b","unresolved":false,"context_lines":[{"line_number":57,"context_line":"   minimum the feature (or API, or configuration option) should be"},{"line_number":58,"context_line":"   marked deprecated (and still be supported) in the next \"tick\""},{"line_number":59,"context_line":"   release branch, *and* for at least three months linear time.  For"},{"line_number":60,"context_line":"   example, a feature deprecated in the 2023 tick release should still"},{"line_number":61,"context_line":"   appear in the 2024 tick release that stable branch and cannot be"},{"line_number":62,"context_line":"   removed before the beginning of the 2024 tock development cycle."},{"line_number":63,"context_line":"   Ideally, features should not be deprecated in a tock release"},{"line_number":64,"context_line":"   because operators deploying only tick releases should not be"},{"line_number":65,"context_line":"   required to read release notes for releases they are not required"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ad4ce8ed_6ebfff3b","line":62,"range":{"start_line":60,"start_character":1,"end_line":62,"end_character":67},"in_reply_to":"8c82ad7a_2f425eda","updated":"2022-03-09 16:25:46.000000000","message":"Done","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6d1bb3bc3114f838e0ef4ad060a505dd9822d404","unresolved":true,"context_lines":[{"line_number":60,"context_line":"   example, a feature deprecated in the 2023 tick release should still"},{"line_number":61,"context_line":"   appear in the 2024 tick release that stable branch and cannot be"},{"line_number":62,"context_line":"   removed before the beginning of the 2024 tock development cycle."},{"line_number":63,"context_line":"   Ideally, features should not be deprecated in a tock release"},{"line_number":64,"context_line":"   because operators deploying only tick releases should not be"},{"line_number":65,"context_line":"   required to read release notes for releases they are not required"},{"line_number":66,"context_line":"   to deploy.  Features included in a tock release but not a tick"}],"source_content_type":"text/x-rst","patch_set":1,"id":"a42f401b_2d7d7417","line":63,"range":{"start_line":63,"start_character":3,"end_line":63,"end_character":10},"updated":"2022-03-08 23:07:58.000000000","message":"we should make it very clear with \"shall not\" otherwise we might have mixed types of adoption in different projects which can confuse users more.\n\nBut if we want to allow any specific deprecation in tock due to a new feature or so then can we add a line here saying we should link the tock deprecated/upgrade release notes in the next tick release too so that operators doing tick-\u003etick notice them easily?","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"e6d19afac19b30c2c35b2eb1418c96e4e9a2f19b","unresolved":true,"context_lines":[{"line_number":60,"context_line":"   example, a feature deprecated in the 2023 tick release should still"},{"line_number":61,"context_line":"   appear in the 2024 tick release that stable branch and cannot be"},{"line_number":62,"context_line":"   removed before the beginning of the 2024 tock development cycle."},{"line_number":63,"context_line":"   Ideally, features should not be deprecated in a tock release"},{"line_number":64,"context_line":"   because operators deploying only tick releases should not be"},{"line_number":65,"context_line":"   required to read release notes for releases they are not required"},{"line_number":66,"context_line":"   to deploy.  Features included in a tock release but not a tick"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ec9b9e80_774156fa","line":63,"range":{"start_line":63,"start_character":3,"end_line":63,"end_character":10},"in_reply_to":"5c7bbb15_678175f4","updated":"2022-03-09 15:22:12.000000000","message":"ok, mentioning \u0027notice in following tick as well\u0027 will works for me.","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"707660e62c732af72a3d6f67ec1ab719fd238f4b","unresolved":true,"context_lines":[{"line_number":60,"context_line":"   example, a feature deprecated in the 2023 tick release should still"},{"line_number":61,"context_line":"   appear in the 2024 tick release that stable branch and cannot be"},{"line_number":62,"context_line":"   removed before the beginning of the 2024 tock development cycle."},{"line_number":63,"context_line":"   Ideally, features should not be deprecated in a tock release"},{"line_number":64,"context_line":"   because operators deploying only tick releases should not be"},{"line_number":65,"context_line":"   required to read release notes for releases they are not required"},{"line_number":66,"context_line":"   to deploy.  Features included in a tock release but not a tick"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5c7bbb15_678175f4","line":63,"range":{"start_line":63,"start_character":3,"end_line":63,"end_character":10},"in_reply_to":"a42f401b_2d7d7417","updated":"2022-03-09 14:46:23.000000000","message":"Yeah, I don\u0027t want to make this sound like it\u0027s restricting things too much, so I want people to be able to deprecate in a tock if they absolutely have to, but with the notice in the following tick as well. That might be too complicated to articulate here, but I\u0027ll change some words and see.","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"39fa89650bc893f193636b73576ca40ef23a0d5b","unresolved":false,"context_lines":[{"line_number":60,"context_line":"   example, a feature deprecated in the 2023 tick release should still"},{"line_number":61,"context_line":"   appear in the 2024 tick release that stable branch and cannot be"},{"line_number":62,"context_line":"   removed before the beginning of the 2024 tock development cycle."},{"line_number":63,"context_line":"   Ideally, features should not be deprecated in a tock release"},{"line_number":64,"context_line":"   because operators deploying only tick releases should not be"},{"line_number":65,"context_line":"   required to read release notes for releases they are not required"},{"line_number":66,"context_line":"   to deploy.  Features included in a tock release but not a tick"}],"source_content_type":"text/x-rst","patch_set":1,"id":"8529efa7_840a7d24","line":63,"range":{"start_line":63,"start_character":3,"end_line":63,"end_character":10},"in_reply_to":"ec9b9e80_774156fa","updated":"2022-03-09 16:25:46.000000000","message":"Done","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6d1bb3bc3114f838e0ef4ad060a505dd9822d404","unresolved":true,"context_lines":[{"line_number":63,"context_line":"   Ideally, features should not be deprecated in a tock release"},{"line_number":64,"context_line":"   because operators deploying only tick releases should not be"},{"line_number":65,"context_line":"   required to read release notes for releases they are not required"},{"line_number":66,"context_line":"   to deploy.  Features included in a tock release but not a tick"},{"line_number":67,"context_line":"   release may be deprecated in the next release of any type and must"},{"line_number":68,"context_line":"   stay in place at least 3 months after being deprecated before being"},{"line_number":69,"context_line":"   removed in a release of any type."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Note that this delay is a required minimum. For significant features, it is"},{"line_number":72,"context_line":"recommended that the deprecated feature appears at least in the next *two*"}],"source_content_type":"text/x-rst","patch_set":1,"id":"b9acd7e0_dd5aad08","line":69,"range":{"start_line":66,"start_character":15,"end_line":69,"end_character":36},"updated":"2022-03-08 23:07:58.000000000","message":"cannot understand this example, is this same for the case where deprecation could happen at the end of cycle and remove at the very start of the cycle?\n\nIf so then it is not valid anymore as I mentioned in my first comment(L59) otherwise can you please elaborate it in detail.","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"e6d19afac19b30c2c35b2eb1418c96e4e9a2f19b","unresolved":true,"context_lines":[{"line_number":63,"context_line":"   Ideally, features should not be deprecated in a tock release"},{"line_number":64,"context_line":"   because operators deploying only tick releases should not be"},{"line_number":65,"context_line":"   required to read release notes for releases they are not required"},{"line_number":66,"context_line":"   to deploy.  Features included in a tock release but not a tick"},{"line_number":67,"context_line":"   release may be deprecated in the next release of any type and must"},{"line_number":68,"context_line":"   stay in place at least 3 months after being deprecated before being"},{"line_number":69,"context_line":"   removed in a release of any type."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Note that this delay is a required minimum. For significant features, it is"},{"line_number":72,"context_line":"recommended that the deprecated feature appears at least in the next *two*"}],"source_content_type":"text/x-rst","patch_set":1,"id":"e5c21232_49303431","line":69,"range":{"start_line":66,"start_character":15,"end_line":69,"end_character":36},"in_reply_to":"b94bfd73_92b8224f","updated":"2022-03-09 15:22:12.000000000","message":"ok, I think we can be explicit here for experimental feature as special case here. and Suggest not to do this for non-experimental interface/config.","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"707660e62c732af72a3d6f67ec1ab719fd238f4b","unresolved":true,"context_lines":[{"line_number":63,"context_line":"   Ideally, features should not be deprecated in a tock release"},{"line_number":64,"context_line":"   because operators deploying only tick releases should not be"},{"line_number":65,"context_line":"   required to read release notes for releases they are not required"},{"line_number":66,"context_line":"   to deploy.  Features included in a tock release but not a tick"},{"line_number":67,"context_line":"   release may be deprecated in the next release of any type and must"},{"line_number":68,"context_line":"   stay in place at least 3 months after being deprecated before being"},{"line_number":69,"context_line":"   removed in a release of any type."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Note that this delay is a required minimum. For significant features, it is"},{"line_number":72,"context_line":"recommended that the deprecated feature appears at least in the next *two*"}],"source_content_type":"text/x-rst","patch_set":1,"id":"b94bfd73_92b8224f","line":69,"range":{"start_line":66,"start_character":15,"end_line":69,"end_character":36},"in_reply_to":"b9acd7e0_dd5aad08","updated":"2022-03-09 14:46:23.000000000","message":"Well, I think I left this here to consider the following situation:\n\n1. New experimental feature introduced in tock\n2. Following tick it is decided that we should not pursue, so it shows up for the first time in a tick as deprecated\n3. The next tock is should be allowed for removal because it only ever showed up in a tick as deprecated\n\nI think that\u0027s in line with what the original words were intending, basically minimum feature lifetime. I wouldn\u0027t want people to feel like this now commits them to a substantial amount of lifecycle for an aborted experimental feature, over what we have now.\n\nThoughts?","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"39fa89650bc893f193636b73576ca40ef23a0d5b","unresolved":false,"context_lines":[{"line_number":63,"context_line":"   Ideally, features should not be deprecated in a tock release"},{"line_number":64,"context_line":"   because operators deploying only tick releases should not be"},{"line_number":65,"context_line":"   required to read release notes for releases they are not required"},{"line_number":66,"context_line":"   to deploy.  Features included in a tock release but not a tick"},{"line_number":67,"context_line":"   release may be deprecated in the next release of any type and must"},{"line_number":68,"context_line":"   stay in place at least 3 months after being deprecated before being"},{"line_number":69,"context_line":"   removed in a release of any type."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Note that this delay is a required minimum. For significant features, it is"},{"line_number":72,"context_line":"recommended that the deprecated feature appears at least in the next *two*"}],"source_content_type":"text/x-rst","patch_set":1,"id":"393f6d95_97cd06df","line":69,"range":{"start_line":66,"start_character":15,"end_line":69,"end_character":36},"in_reply_to":"e5c21232_49303431","updated":"2022-03-09 16:25:46.000000000","message":"Done","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":30491,"name":"Radosław Piliszek","display_name":"Radek","email":"radek@piliszek.it","username":"yoctozepto","status":"self-employed techologist, collaborating mostly with 7bulls.com"},"change_message_id":"87717b4064d27b5b66460a4a600e881be49b72dd","unresolved":true,"context_lines":[{"line_number":68,"context_line":"   stay in place at least 3 months after being deprecated before being"},{"line_number":69,"context_line":"   removed in a release of any type."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Note that this delay is a required minimum. For significant features, it is"},{"line_number":72,"context_line":"recommended that the deprecated feature appears at least in the next *two*"},{"line_number":73,"context_line":"tick release branches."},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"4f2472ec_247e2713","line":71,"range":{"start_line":71,"start_character":26,"end_line":71,"end_character":35},"updated":"2022-03-07 17:16:23.000000000","message":"recommended/suggested","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"39fa89650bc893f193636b73576ca40ef23a0d5b","unresolved":false,"context_lines":[{"line_number":68,"context_line":"   stay in place at least 3 months after being deprecated before being"},{"line_number":69,"context_line":"   removed in a release of any type."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Note that this delay is a required minimum. For significant features, it is"},{"line_number":72,"context_line":"recommended that the deprecated feature appears at least in the next *two*"},{"line_number":73,"context_line":"tick release branches."},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"42d5ff41_10b1421c","line":71,"range":{"start_line":71,"start_character":26,"end_line":71,"end_character":35},"in_reply_to":"018d1d65_2651016f","updated":"2022-03-09 16:25:46.000000000","message":"Done","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6d1bb3bc3114f838e0ef4ad060a505dd9822d404","unresolved":true,"context_lines":[{"line_number":68,"context_line":"   stay in place at least 3 months after being deprecated before being"},{"line_number":69,"context_line":"   removed in a release of any type."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Note that this delay is a required minimum. For significant features, it is"},{"line_number":72,"context_line":"recommended that the deprecated feature appears at least in the next *two*"},{"line_number":73,"context_line":"tick release branches."},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"018d1d65_2651016f","line":71,"range":{"start_line":71,"start_character":26,"end_line":71,"end_character":35},"in_reply_to":"311ace32_9f357412","updated":"2022-03-08 23:07:58.000000000","message":"yeah, I will keep it as it is even it is not tag things anymore but mentioning it required will help to have consistent deprecation policy in openstack.","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"cb9034a279636d062b3f4a8d6828f660fa1bd3ff","unresolved":true,"context_lines":[{"line_number":68,"context_line":"   stay in place at least 3 months after being deprecated before being"},{"line_number":69,"context_line":"   removed in a release of any type."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Note that this delay is a required minimum. For significant features, it is"},{"line_number":72,"context_line":"recommended that the deprecated feature appears at least in the next *two*"},{"line_number":73,"context_line":"tick release branches."},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"d54a2c38_066a884a","line":71,"range":{"start_line":71,"start_character":26,"end_line":71,"end_character":35},"in_reply_to":"4f2472ec_247e2713","updated":"2022-03-07 17:39:50.000000000","message":"You\u0027re saying that because this becomes a suggested guideline and not a \"you must do this if you assert this tag\"? I guess to me, I\u0027d rather keep the language strong and forgive violations, as opposed to making it sound like a soft suggestion.\n\nMaybe we should get some other opinions?","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"efd21b005f7deaba30df349da294f3b3e74aa6a0","unresolved":true,"context_lines":[{"line_number":68,"context_line":"   stay in place at least 3 months after being deprecated before being"},{"line_number":69,"context_line":"   removed in a release of any type."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Note that this delay is a required minimum. For significant features, it is"},{"line_number":72,"context_line":"recommended that the deprecated feature appears at least in the next *two*"},{"line_number":73,"context_line":"tick release branches."},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"311ace32_9f357412","line":71,"range":{"start_line":71,"start_character":26,"end_line":71,"end_character":35},"in_reply_to":"b5b755be_c6816430","updated":"2022-03-07 17:56:30.000000000","message":"Ack, I softened a number of statements in here during the conversion, but left this one because it seemed legit.\n\nBut yeah, let\u0027s see what others have to say.","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"},{"author":{"_account_id":30491,"name":"Radosław Piliszek","display_name":"Radek","email":"radek@piliszek.it","username":"yoctozepto","status":"self-employed techologist, collaborating mostly with 7bulls.com"},"change_message_id":"8639a1693285aaf1e9d9055250af86c708556e43","unresolved":true,"context_lines":[{"line_number":68,"context_line":"   stay in place at least 3 months after being deprecated before being"},{"line_number":69,"context_line":"   removed in a release of any type."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Note that this delay is a required minimum. For significant features, it is"},{"line_number":72,"context_line":"recommended that the deprecated feature appears at least in the next *two*"},{"line_number":73,"context_line":"tick release branches."},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"b5b755be_c6816430","line":71,"range":{"start_line":71,"start_character":26,"end_line":71,"end_character":35},"in_reply_to":"d54a2c38_066a884a","updated":"2022-03-07 17:42:00.000000000","message":"Yeah. I don\u0027t have a strong opinion on this. I just wanted it to sound slightly softer but perhaps less than my suggestions. I welcome any ideas to improve this wording.","commit_id":"c71eeac20a6008f767a132bdfb7fa11d7af957b7"}]}