)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"a8d603671f41dd3b3911ce18e4103c82fdbd3030","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b758af1e_25da728f","updated":"2022-05-03 16:56:48.000000000","message":"\u003e Patch Set 1:\n\u003e \n\u003e Based on what I understood about the feedback we got from legal counsel, this seems like an unnecessarily pedantic application of that feedback. Using the terms adjacent to one another in headlines, marketing collateral and the like is the real concern. Descriptive use in technical prose about release process doesn\u0027t rise to that level of attention, and so we ought to be free to use whatever flows best within the document here. Maybe avoid putting the words \"tick\" and \"tock\" next to one another in page titles, it doesn\u0027t seem like this specific change is warranted.\n\u003e \n\u003e If you\u0027re still concerned and want to clear this document with the foundation staff, Jonathan indicated to me that he would be happy to provide more direct feedback on it.\n\nSure, What I heard from Wes is not only using them together in page title but in anywhere. Like this resolution used it (which I am changing now) and same was published in few site/articles which is problematic. for example: https://techcrunch.com/2022/03/30/openstackl-aunches-yoga-its-25th-release/\n\nFrom that I think we need to avoid using them together in documentation, page title or anywhere public facing documentation.\n\nBut let\u0027s add them in review to confirm it or if anything more we need to fix.","commit_id":"64ac8595ef865da62abeb8291312cddb4c7ab9c8"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"7348f3018cfedc9adb2435f4259ee0659feae9f7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e8874239_f85b11ed","updated":"2022-05-04 13:47:49.000000000","message":"Agree -- the issue is in using the two words close together. Whether an hyphen or a comma separates them is really irrelevant.\n\nWhich is the core of the issue: it\u0027s quite difficult to explain the scheme (the regular cycling through two states) without putting the two words next together... This is why some suggested to use a completely different set of names to convey the same sense of regularity.\n\nI understand that major/minor has extra baggage, spring/fall has a hemisphere problem. But maybe names like odd/even, day/night, ping/pong, whiff/whaff can convey the same idea without creating a potential issue down the road. You can upgrade between two ping releases, or from ping to pong and pong to ping.","commit_id":"64ac8595ef865da62abeb8291312cddb4c7ab9c8"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"8c205764638b8410a8d3295b46873dcd76e3b27a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"481040fd_f14732e9","updated":"2022-05-04 14:08:10.000000000","message":"I am not a huge fan of tick tock or ping pong.  Do I have a better suggestion?  No.  So, I think we are probably best taking the feedback on tick tock and going to ping pong as I think it communicates, as best we can, what we are trying to do with our release cycles.","commit_id":"64ac8595ef865da62abeb8291312cddb4c7ab9c8"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"e6221dbd6c7e0260d774577c1efb80ba067ed73b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7c88b12f_d40cf0e7","updated":"2022-05-03 16:31:03.000000000","message":"LOL lawyers, but.. sure :D","commit_id":"64ac8595ef865da62abeb8291312cddb4c7ab9c8"},{"author":{"_account_id":16708,"name":"Kendall Nelson","display_name":"Kendall (diablo_rojo)","email":"kennelson11@gmail.com","username":"kjnelson"},"change_message_id":"3d9bf3e7b4141afb28b78469ecdeb3ca3b0701d9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"18c2f323_df17df34","updated":"2022-05-10 15:11:35.000000000","message":"Looks good to me. ","commit_id":"64ac8595ef865da62abeb8291312cddb4c7ab9c8"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b3219d62d8c27519e3b7d9225c2544a0277f30e3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"af75b0ef_b2cc777f","updated":"2022-05-03 16:58:14.000000000","message":"not sure if Wes using gerrit as I did not find him.","commit_id":"64ac8595ef865da62abeb8291312cddb4c7ab9c8"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"ae7f9d5ac7f091399053d83a4f8e20b7ff11bc71","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"2e08b7d7_6f037540","in_reply_to":"157f8a7d_a18539d3","updated":"2022-05-04 16:04:46.000000000","message":"You mean to use \"Skip-Level Upgrade Release Process (SLURP)\" in documentation like here ? (that is why it will e easy to ref ?) and use SLU in the release page or SLURP?\n\nOpenStack 2023.1 AA (SLU) or OpenStack 2023.1 AA (SLURP)?\n\nI am also thinking if that is ok from communicating the releasenote things, for example, \"Communicate the non-SLURP release deprecated/upgradeable release notes to SLURP release too\" I think that should be ok. I mean when tock was recognized by \u0027tock\u0027 and now it can be recognized by not having \"SLU\" tag in that.","commit_id":"64ac8595ef865da62abeb8291312cddb4c7ab9c8"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"61fe142ec16a96b862808776409a7122f4383545","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c4eff6c3_89e6d490","in_reply_to":"2e08b7d7_6f037540","updated":"2022-05-04 16:13:28.000000000","message":"\u003e You mean to use \"Skip-Level Upgrade Release Process (SLURP)\" in documentation like here ? (that is why it will e easy to ref ?) and use SLU in the release page or SLURP?\n\nI meant \"SLU\" is not as easy to pronounce or say as something like \"SLURP\" which is more like a word.\n\n\u003e OpenStack 2023.1 AA (SLU) or OpenStack 2023.1 AA (SLURP)?\n\nThe latter. I just added two letters to your suggestion to make it easier to say as a word, but otherwise fine with that proposal.\n\n\u003e I am also thinking if that is ok from communicating the releasenote things, for example, \"Communicate the non-SLURP release deprecated/upgradeable release notes to SLURP release too\" I think that should be ok. I mean when tock was recognized by \u0027tock\u0027 and now it can be recognized by not having \"SLU\" tag in that.\n\nYep, I understand and I also think that\u0027s okay. I think it\u0027s slightly nicer to say \"tock\" or \"pong\" compared to \"non-SLURP\" or \"not a SLURP\". However, for the people that say they can\u0027t remember which is which, \"SLURP\" and \"non-SLURP\" will likely be much easier to remember which is the special release, vs. \"tick\" or \"ping\".","commit_id":"64ac8595ef865da62abeb8291312cddb4c7ab9c8"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"857532542518f2be776a13eb189e6f5ff8d11ce7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"157f8a7d_a18539d3","in_reply_to":"38c891f1_d6692d12","updated":"2022-05-04 15:32:07.000000000","message":"If we do that, perhaps Skip-Level Upgrade Release Process (SLURP) so that it\u0027s easy to reference.\n\nI also thought about \"fast/slow\" and \"long/short\". The benefit of choosing something less \"binary\" is that we can alter that cadence (i.e. more releases between SLURP releases) in the future if we want.\n\nI think it\u0027s pretty clear from this and other naming discussions going on at the moment that we\u0027re not going to please everyone with whatever we choose :/","commit_id":"64ac8595ef865da62abeb8291312cddb4c7ab9c8"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"f7440026041efdb16d55153a8560785060ea87f0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"8637677b_73a06612","in_reply_to":"c4eff6c3_89e6d490","updated":"2022-05-04 16:31:31.000000000","message":"cool, sounds good to me.","commit_id":"64ac8595ef865da62abeb8291312cddb4c7ab9c8"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"67369daef470b4ab637cc2541b73a53428106993","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"fc884a72_b0feef34","in_reply_to":"e8874239_f85b11ed","updated":"2022-05-04 13:51:31.000000000","message":"ping and pong have very similar characteristics to tick and tock, and also share the same second letter, so it should be very easy to convert documentation and mental state. So, that\u0027d be my vote of everything I\u0027ve heard so far as an alternative.","commit_id":"64ac8595ef865da62abeb8291312cddb4c7ab9c8"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"c17b403ce766b3e019bbc8b3fb73c42723b1c8c6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"38c891f1_d6692d12","in_reply_to":"fc884a72_b0feef34","updated":"2022-05-04 15:04:36.000000000","message":"I did not mean to separate them with commas but with quotes I think they are used as separate like \u0027tick\u0027 \u0027tock\u0027 are not same as \u0027tick tock\u0027 but if they are same thing from legal perspective then ok.\n\nas we need to use them as tag and not a name as such how about using \u0027SLU\u0027 (Skip Level Upgradable) for tick(current name) release and do not use anything for tock release? and in documentation like this resolution of anywhere we can use \u0027SLU\u0027 and \u0027non-SLU\u0027 as name?\n\nFor example: release page/any other doc can tag the release like:\n- OpenStack 2023.1 AA (SLU)\n- OpenStack 2023.2 BB\n- OpenStack 2024.1 CC (SLU)","commit_id":"64ac8595ef865da62abeb8291312cddb4c7ab9c8"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"3728ee1c152915276bcf0c8cbab7049342d73878","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"4abbd56e_6da3965e","updated":"2022-05-14 16:58:44.000000000","message":"Caught two ticks that you missed; otherwise this looks great.","commit_id":"aa10b2f557875ebce479d2cdbbf7c4609a013e2b"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"e6d2b64d02e087f7c2ce9852eb3405c977301900","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"c4357cdd_7b8e8a69","updated":"2022-05-19 18:52:34.000000000","message":"A few wording suggestions in-line.  Otherwise, I think this looks good.","commit_id":"340683abcbe245e1bf490145b680fba9dfb88def"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"09f1a00bd60b7ff65b196cfa67fee27afdbea19b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"ab19bf8b_48df807c","updated":"2022-05-20 12:47:08.000000000","message":"Can be done on a separate patchset, I guess.","commit_id":"340683abcbe245e1bf490145b680fba9dfb88def"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"b5df4e43a194d7be6ccf7349b7696b9d44976697","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"5ba1e0bb_5ab7e672","updated":"2022-05-19 18:45:29.000000000","message":"LGTM.","commit_id":"340683abcbe245e1bf490145b680fba9dfb88def"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"1ffadfc702be81014ed50abc59ba660dce30326e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"3b4c1236_14b83985","updated":"2022-05-20 12:43:45.000000000","message":"Small nit: all the sequence examples are relying on letters instead of numbers. I agree it\u0027s a lot clearer that way, but that may become confusing if our documentation is supposed to prioritize the use of numbers?","commit_id":"340683abcbe245e1bf490145b680fba9dfb88def"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"64f36b6bb84fda32af37752e68f163b1a8e4ef09","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"1ba18835_481205bd","in_reply_to":"3b4c1236_14b83985","updated":"2022-05-20 17:50:47.000000000","message":"yeah, that is because we did this resolution before release name things settle down or as you know, even we are still discussing how to use both name and number in development process. Once that is sorted out I will update those here.","commit_id":"340683abcbe245e1bf490145b680fba9dfb88def"}],"resolutions/20220210-release-cadence-adjustment.rst":[{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"53bb93bcf74ea31333d0b2529bf2a8fd3f555551","unresolved":true,"context_lines":[{"line_number":51,"context_line":"The fundamental change comes to the expectation that upgrades are only"},{"line_number":52,"context_line":"supported between adjacent coordinated releases. The TC will designate"},{"line_number":53,"context_line":"major releases in a new arrangement, such that every other release will be"},{"line_number":54,"context_line":"considered to be a \"SLURP (Skip Level Upgarde Release Process)\" release."},{"line_number":55,"context_line":"Upgrades will be supported between \"SLURP\" releases, in addition to between"},{"line_number":56,"context_line":"adjacent major releases (as they are today). Deployments wishing to stay on"},{"line_number":57,"context_line":"the six-month cycle will deploy every \"SLURP\" and \"not-SLURP\" release as they"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ec3ecfd0_ba1af9fd","line":54,"range":{"start_line":54,"start_character":38,"end_line":54,"end_character":45},"updated":"2022-05-16 15:21:43.000000000","message":"Upgrade","commit_id":"aa10b2f557875ebce479d2cdbbf7c4609a013e2b"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bcf34d00d56ae4f66d920c96eef9d1f2d4d26715","unresolved":false,"context_lines":[{"line_number":51,"context_line":"The fundamental change comes to the expectation that upgrades are only"},{"line_number":52,"context_line":"supported between adjacent coordinated releases. The TC will designate"},{"line_number":53,"context_line":"major releases in a new arrangement, such that every other release will be"},{"line_number":54,"context_line":"considered to be a \"SLURP (Skip Level Upgarde Release Process)\" release."},{"line_number":55,"context_line":"Upgrades will be supported between \"SLURP\" releases, in addition to between"},{"line_number":56,"context_line":"adjacent major releases (as they are today). Deployments wishing to stay on"},{"line_number":57,"context_line":"the six-month cycle will deploy every \"SLURP\" and \"not-SLURP\" release as they"}],"source_content_type":"text/x-rst","patch_set":3,"id":"b3f2e57d_ed946b5b","line":54,"range":{"start_line":54,"start_character":38,"end_line":54,"end_character":45},"in_reply_to":"ec3ecfd0_ba1af9fd","updated":"2022-05-16 15:46:12.000000000","message":"Done","commit_id":"aa10b2f557875ebce479d2cdbbf7c4609a013e2b"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"3728ee1c152915276bcf0c8cbab7049342d73878","unresolved":true,"context_lines":[{"line_number":78,"context_line":""},{"line_number":79,"context_line":"#. **Testing**: Just as we test and guarantee that upgrades are"},{"line_number":80,"context_line":"   supported between adjacent releases today, we will *also* test and"},{"line_number":81,"context_line":"   guarantee that upgrades between two tick releases are supported."},{"line_number":82,"context_line":"   Upgrades are tested for most projects today with grenade. A"},{"line_number":83,"context_line":"   skip-level job will be maintained in the grenade repository that"},{"line_number":84,"context_line":"   tests a normal configuration between the last two \"SLURP\""}],"source_content_type":"text/x-rst","patch_set":3,"id":"1e25658a_43f547db","line":81,"range":{"start_line":81,"start_character":39,"end_line":81,"end_character":43},"updated":"2022-05-14 16:58:44.000000000","message":"\"SLURP\"","commit_id":"aa10b2f557875ebce479d2cdbbf7c4609a013e2b"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bcf34d00d56ae4f66d920c96eef9d1f2d4d26715","unresolved":false,"context_lines":[{"line_number":78,"context_line":""},{"line_number":79,"context_line":"#. **Testing**: Just as we test and guarantee that upgrades are"},{"line_number":80,"context_line":"   supported between adjacent releases today, we will *also* test and"},{"line_number":81,"context_line":"   guarantee that upgrades between two tick releases are supported."},{"line_number":82,"context_line":"   Upgrades are tested for most projects today with grenade. A"},{"line_number":83,"context_line":"   skip-level job will be maintained in the grenade repository that"},{"line_number":84,"context_line":"   tests a normal configuration between the last two \"SLURP\""}],"source_content_type":"text/x-rst","patch_set":3,"id":"15910233_f8e8d644","line":81,"range":{"start_line":81,"start_character":39,"end_line":81,"end_character":43},"in_reply_to":"1e25658a_43f547db","updated":"2022-05-16 15:46:12.000000000","message":"Done","commit_id":"aa10b2f557875ebce479d2cdbbf7c4609a013e2b"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"3728ee1c152915276bcf0c8cbab7049342d73878","unresolved":true,"context_lines":[{"line_number":123,"context_line":"   release before moving to one that drops compatibility. The"},{"line_number":124,"context_line":"   \"SLURP\", \"not-SLURP\" arrangement described in this resolution would require"},{"line_number":125,"context_line":"   attention to those migrations to make sure they happen"},{"line_number":126,"context_line":"   (automatically or manually) on the source tick before upgrading to"},{"line_number":127,"context_line":"   the target \"SLURP\", for example."},{"line_number":128,"context_line":"#. **Communication**: We will use \"SLURP\" word to designate a SLURP release"},{"line_number":129,"context_line":"   in release page, release notes page or any other place we want to communicate"}],"source_content_type":"text/x-rst","patch_set":3,"id":"16352f88_de9e2445","line":126,"range":{"start_line":126,"start_character":45,"end_line":126,"end_character":49},"updated":"2022-05-14 16:58:44.000000000","message":"\"SLURP\"","commit_id":"aa10b2f557875ebce479d2cdbbf7c4609a013e2b"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bcf34d00d56ae4f66d920c96eef9d1f2d4d26715","unresolved":false,"context_lines":[{"line_number":123,"context_line":"   release before moving to one that drops compatibility. The"},{"line_number":124,"context_line":"   \"SLURP\", \"not-SLURP\" arrangement described in this resolution would require"},{"line_number":125,"context_line":"   attention to those migrations to make sure they happen"},{"line_number":126,"context_line":"   (automatically or manually) on the source tick before upgrading to"},{"line_number":127,"context_line":"   the target \"SLURP\", for example."},{"line_number":128,"context_line":"#. **Communication**: We will use \"SLURP\" word to designate a SLURP release"},{"line_number":129,"context_line":"   in release page, release notes page or any other place we want to communicate"}],"source_content_type":"text/x-rst","patch_set":3,"id":"12dc1c8b_0dbc1414","line":126,"range":{"start_line":126,"start_character":45,"end_line":126,"end_character":49},"in_reply_to":"16352f88_de9e2445","updated":"2022-05-16 15:46:12.000000000","message":"Done","commit_id":"aa10b2f557875ebce479d2cdbbf7c4609a013e2b"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"1ffadfc702be81014ed50abc59ba660dce30326e","unresolved":true,"context_lines":[{"line_number":59,"context_line":"synchronize on a \"SLURP\" release, and then skip the following \"not-SLURP\""},{"line_number":60,"context_line":"release, upgrading when the subsequent \"SLURP\" is released."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Our letter-based release naming scheme is about to wrap back around to"},{"line_number":63,"context_line":"A, so the proposal is that the \"new A\" release be the first one where"},{"line_number":64,"context_line":"we enforce this scheme. Y-\u003eA should be a \"dress rehearsal\" where we"},{"line_number":65,"context_line":"have the jobs enabled to help smoke out any issues, but where hard"},{"line_number":66,"context_line":"guarantees are not yet made."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"Occasionally, individual releases are chosen by a large number of"},{"line_number":69,"context_line":"deployers and distributors by chance, which results in a larger than"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ea40a39b_5c00f016","line":66,"range":{"start_line":62,"start_character":0,"end_line":66,"end_character":28},"updated":"2022-05-20 12:43:45.000000000","message":"Should that paragraph be updated to using numbers instead of letters?","commit_id":"340683abcbe245e1bf490145b680fba9dfb88def"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"1ffadfc702be81014ed50abc59ba660dce30326e","unresolved":true,"context_lines":[{"line_number":89,"context_line":"   not be tested nor required. On a given \"not-SLURP\" release, the only"},{"line_number":90,"context_line":"   upgrade path will be to the following release (which would be a \"SLURP\")."},{"line_number":91,"context_line":"   This is unchanged from today."},{"line_number":92,"context_line":"#. **Intervals**: Upgrades that span more than one \"SLURP\" cycle are not"},{"line_number":93,"context_line":"   tested or required. For example to move from \"SLURP A\" to \"SLURP E\" will"},{"line_number":94,"context_line":"   still require an FFU style arrangement, but where \"SLURP C\" is the"},{"line_number":95,"context_line":"   only intermediate step required."},{"line_number":96,"context_line":"#. **Deprecations**: Projects currently deprecate features and config"},{"line_number":97,"context_line":"   for at least one cycle before removal. This change affects *when*"},{"line_number":98,"context_line":"   that can happen, so that no required changes occur in a \"not-SLURP\""}],"source_content_type":"text/x-rst","patch_set":4,"id":"13c79812_ed1d582a","line":95,"range":{"start_line":92,"start_character":0,"end_line":95,"end_character":35},"updated":"2022-05-20 12:43:45.000000000","message":"Should that paragraph be updated to use numbers instead of letters?","commit_id":"340683abcbe245e1bf490145b680fba9dfb88def"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"e6d2b64d02e087f7c2ce9852eb3405c977301900","unresolved":true,"context_lines":[{"line_number":126,"context_line":"   (automatically or manually) on the source \"SLURP\" before upgrading to"},{"line_number":127,"context_line":"   the target \"SLURP\", for example."},{"line_number":128,"context_line":"#. **Communication**: We will use \"SLURP\" word to designate a SLURP release"},{"line_number":129,"context_line":"   in release page, release notes page or any other place we want to communicate"},{"line_number":130,"context_line":"   it. We can also use its full form \"Skip Level Upgrade Release Process\""},{"line_number":131,"context_line":"   if needed. A \"not-SLURP\" release will not be designated with anything and"},{"line_number":132,"context_line":"   not having \"SLURP\" word is enough to communicate that this is not \"SLURP\""}],"source_content_type":"text/x-rst","patch_set":4,"id":"8dab3a1a_8df4d545","line":129,"range":{"start_line":129,"start_character":2,"end_line":129,"end_character":18},"updated":"2022-05-19 18:52:34.000000000","message":"on the release page,","commit_id":"340683abcbe245e1bf490145b680fba9dfb88def"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"e6d2b64d02e087f7c2ce9852eb3405c977301900","unresolved":true,"context_lines":[{"line_number":129,"context_line":"   in release page, release notes page or any other place we want to communicate"},{"line_number":130,"context_line":"   it. We can also use its full form \"Skip Level Upgrade Release Process\""},{"line_number":131,"context_line":"   if needed. A \"not-SLURP\" release will not be designated with anything and"},{"line_number":132,"context_line":"   not having \"SLURP\" word is enough to communicate that this is not \"SLURP\""},{"line_number":133,"context_line":"   release. Also, the number schema in the release naming process will help all"},{"line_number":134,"context_line":"   of us to relate which release is \"SLURP\"."},{"line_number":135,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"14bc2bff_aad82763","line":132,"range":{"start_line":132,"start_character":65,"end_line":132,"end_character":76},"updated":"2022-05-19 18:52:34.000000000","message":"not a \"SLURP\"","commit_id":"340683abcbe245e1bf490145b680fba9dfb88def"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"e6d2b64d02e087f7c2ce9852eb3405c977301900","unresolved":true,"context_lines":[{"line_number":129,"context_line":"   in release page, release notes page or any other place we want to communicate"},{"line_number":130,"context_line":"   it. We can also use its full form \"Skip Level Upgrade Release Process\""},{"line_number":131,"context_line":"   if needed. A \"not-SLURP\" release will not be designated with anything and"},{"line_number":132,"context_line":"   not having \"SLURP\" word is enough to communicate that this is not \"SLURP\""},{"line_number":133,"context_line":"   release. Also, the number schema in the release naming process will help all"},{"line_number":134,"context_line":"   of us to relate which release is \"SLURP\"."},{"line_number":135,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"673327d6_c34a6225","line":132,"range":{"start_line":132,"start_character":7,"end_line":132,"end_character":26},"updated":"2022-05-19 18:52:34.000000000","message":"the \"SLURP\" designation","commit_id":"340683abcbe245e1bf490145b680fba9dfb88def"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"1ffadfc702be81014ed50abc59ba660dce30326e","unresolved":true,"context_lines":[{"line_number":136,"context_line":"Example sequence"},{"line_number":137,"context_line":"----------------"},{"line_number":138,"context_line":""},{"line_number":139,"context_line":"Assuming that A is the first release of this new arrangement,"},{"line_number":140,"context_line":"the following examples help demonstrate the support lifecycle"},{"line_number":141,"context_line":"expectation."},{"line_number":142,"context_line":""},{"line_number":143,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d \u003d\u003d\u003d\u003d\u003d \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":144,"context_line":"Release Type   Supported  EM"},{"line_number":145,"context_line":"A       SLURP  X,Y,Z      W"},{"line_number":146,"context_line":"B              Y,Z,A      W,X"},{"line_number":147,"context_line":"C       SLURP  A,B,C      W,X,Y,Z"},{"line_number":148,"context_line":"D              A,B,C,D    X,Y,Z"},{"line_number":149,"context_line":"E       SLURP  C,D,E      Y,Z,A,B"},{"line_number":150,"context_line":"F              C,D,E,F    Z,A,B"},{"line_number":151,"context_line":"G       SLURP  E,F,G      A,B,C"},{"line_number":152,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d \u003d\u003d\u003d\u003d\u003d \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":153,"context_line":""},{"line_number":154,"context_line":"(EM releases are arbitrarily pruned in the above example for brevity,"},{"line_number":155,"context_line":"but no such change in how long they may be supported is made in this"}],"source_content_type":"text/x-rst","patch_set":4,"id":"eb89e877_bca01acb","line":152,"range":{"start_line":139,"start_character":0,"end_line":152,"end_character":34},"updated":"2022-05-20 12:43:45.000000000","message":"Should that paragraph be updated to use numbers instead of letters?","commit_id":"340683abcbe245e1bf490145b680fba9dfb88def"}]}