)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"9474f41ef7c7b5dc897595b7a04065c663ef69d4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"13a8c1c4_ea29e0a1","updated":"2023-03-01 14:44:30.000000000","message":"I think what is proposed here is much more complicated than just having releases being designated as SLURP or not. I really don\u0027t understand the confusion being presented either, as \"between SLURP releases\" seems to very clearly indicate that you need two of them. A single sentence explaining that the first SLURP release doesn\u0027t imply you can upgrade from N-2 would be sufficient and much less complicated, IMHO.","commit_id":"69fdd150b6066039c64ca6658d0cc09788c7d3fd"}],"resolutions/20220210-release-cadence-adjustment.rst":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"4be755b561bfbb56b01ebafff569b7122f528282","unresolved":true,"context_lines":[{"line_number":148,"context_line":""},{"line_number":149,"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\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":150,"context_line":"Release Type        Supported   EM"},{"line_number":151,"context_line":"A       SLU base    X,Y,Z       W"},{"line_number":152,"context_line":"B       non-SLU     Y,Z,A       W,X"},{"line_number":153,"context_line":"C       SLU release A,B,C       W,X,Y,Z"},{"line_number":154,"context_line":"D       non-SLU     A,B,C,D     X,Y,Z"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9020ab54_27fbbbc1","line":151,"range":{"start_line":151,"start_character":8,"end_line":151,"end_character":16},"updated":"2023-03-01 10:11:10.000000000","message":"just to be clear since we do not guarentee that you can upgrade form yoga\nacross all project i think its incorrefct to refer to 2023.1 as a SLURP release in the previous wording.\n\nmy reading of the orginal wording is a SLURP release is a release that guarentees you can upgrading to it via the SLURP process which is not requried form yoga to antelope as it is a \"dress rehearsal\" only enven if we are going to try and keep that working.","commit_id":"7fd1c897fb5569129c883aa1c418f01324b364a7"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"9500996319b59d5083252ad4a1d3545e88000b0c","unresolved":true,"context_lines":[{"line_number":148,"context_line":""},{"line_number":149,"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\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":150,"context_line":"Release Type        Supported   EM"},{"line_number":151,"context_line":"A       SLU base    X,Y,Z       W"},{"line_number":152,"context_line":"B       non-SLU     Y,Z,A       W,X"},{"line_number":153,"context_line":"C       SLU release A,B,C       W,X,Y,Z"},{"line_number":154,"context_line":"D       non-SLU     A,B,C,D     X,Y,Z"}],"source_content_type":"text/x-rst","patch_set":1,"id":"36a3a38e_15daeafb","line":151,"range":{"start_line":151,"start_character":8,"end_line":151,"end_character":16},"in_reply_to":"9020ab54_27fbbbc1","updated":"2023-05-17 11:23:37.000000000","message":"Yeah, 2023.1 is kind of special case and we can mark it here as \"SLURP base\" or something like that.","commit_id":"7fd1c897fb5569129c883aa1c418f01324b364a7"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"9474f41ef7c7b5dc897595b7a04065c663ef69d4","unresolved":true,"context_lines":[{"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 Upgrade 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"},{"line_number":58,"context_line":"always have. Deployments wishing to move to a one year upgrade cycle will"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fec43160_4b03dca4","side":"PARENT","line":55,"range":{"start_line":55,"start_character":27,"end_line":55,"end_character":51},"updated":"2023-03-01 14:44:30.000000000","message":"IMHO, this is the key to question here. \"Between\" means you need two of them, so there\u0027s really no concern about yoga, since it was *not* a SLURP release. A single sentence here saying something about the chicken-and-egg problem would be sufficient I think.","commit_id":"016e72f5350d2d4fb3d046c34ba11b2caf791a36"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"7ac82066c25218929e92ebe2e441f5f425a1b952","unresolved":true,"context_lines":[{"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 Upgrade 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"},{"line_number":58,"context_line":"always have. Deployments wishing to move to a one year upgrade cycle will"}],"source_content_type":"text/x-rst","patch_set":2,"id":"e7e3fb1a_07a54a26","side":"PARENT","line":55,"range":{"start_line":55,"start_character":27,"end_line":55,"end_character":51},"in_reply_to":"6d7d2c30_3f73ace9","updated":"2023-03-02 11:39:06.000000000","message":"by the way i feel its very imporant that we do not declare Antelope a SLURP\nrelease in any of our marketing matials, preludes or releasenotes.\n\nthis is why im proposing this resolution amendmet and why im doing it now.","commit_id":"016e72f5350d2d4fb3d046c34ba11b2caf791a36"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"9500996319b59d5083252ad4a1d3545e88000b0c","unresolved":true,"context_lines":[{"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 Upgrade 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"},{"line_number":58,"context_line":"always have. Deployments wishing to move to a one year upgrade cycle will"}],"source_content_type":"text/x-rst","patch_set":2,"id":"2f3cad87_06d06e81","side":"PARENT","line":55,"range":{"start_line":55,"start_character":27,"end_line":55,"end_character":51},"in_reply_to":"79ee217f_963a493d","updated":"2023-05-17 11:23:37.000000000","message":"with LTS version of Ubuntu I think that things were a bit different as LTS is related to the support lenght, not only to the upgrade process.\nIn our case SLURP releases are going to be supported for the same amount of time as non SLURP ones, right? It\u0027s just that You can upgrade from one SLURP to next one, skipping non SLURP which is between.\nAnd now, there is this special case which is 2023.1 - IMO technically it\u0027s not SLURP as Sean said but it\u0027s \"SLURP starting release\" or something like that 😊","commit_id":"016e72f5350d2d4fb3d046c34ba11b2caf791a36"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"8cc762e2a24746485c788c742c6c7b4dc9cb8e06","unresolved":true,"context_lines":[{"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 Upgrade 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"},{"line_number":58,"context_line":"always have. Deployments wishing to move to a one year upgrade cycle will"}],"source_content_type":"text/x-rst","patch_set":2,"id":"79ee217f_963a493d","side":"PARENT","line":55,"range":{"start_line":55,"start_character":27,"end_line":55,"end_character":51},"in_reply_to":"e7e3fb1a_07a54a26","updated":"2023-03-02 14:45:27.000000000","message":"I feel it\u0027s very important that we *do* declare it a SLURP release. \n\nIt means people will know that 2023.1 will be a good one to make sure they hit, so that if they want to skip 2023.2 they can. The first LTS release of Ubuntu didn\u0027t involve any new support promises for existing releases that were old but suddenly now supported or upgradeable-from, it meant that *that* release would be supported for longer and that the *next* LTS would be allowed as a direct upgrade.\n\nObviously any marketing materials that explain what it is should do so accurately, as this document does, and not indicate that it changes anything about older releases, only future ones.","commit_id":"016e72f5350d2d4fb3d046c34ba11b2caf791a36"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"9bbe9e80e3a7204c0521e31308fe149f0a51794d","unresolved":true,"context_lines":[{"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 Upgrade 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"},{"line_number":58,"context_line":"always have. Deployments wishing to move to a one year upgrade cycle will"}],"source_content_type":"text/x-rst","patch_set":2,"id":"6d7d2c30_3f73ace9","side":"PARENT","line":55,"range":{"start_line":55,"start_character":27,"end_line":55,"end_character":51},"in_reply_to":"fec43160_4b03dca4","updated":"2023-03-02 11:35:33.000000000","message":"yes.\n\nwe could just add somehing liek this\n\nWhile 2023.1 Antelope is not a SLURP release becasue skip level upgrades are only experimenatlly supported form yoga as a dress rehersal it is considered a SLURP release in the context of upgrading to 2024.1 which will be the first fully supported SLURP upgrade.","commit_id":"016e72f5350d2d4fb3d046c34ba11b2caf791a36"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"9474f41ef7c7b5dc897595b7a04065c663ef69d4","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 \"SLU (Skip Level Upgrade)\" release."},{"line_number":55,"context_line":"Upgrades will be supported between a SLU base release and the next SLU release."},{"line_number":56,"context_line":"Each SLU release will be SLU base release for the next SLU release."},{"line_number":57,"context_line":"In addition upgrades between adjacent major releases will continue to be"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1c42f364_4365c0d2","line":54,"range":{"start_line":54,"start_character":20,"end_line":54,"end_character":23},"updated":"2023-03-01 14:44:30.000000000","message":"Why are you changing the acronym? We had a long drawn out conversation (and even a vote) about it, so please don\u0027t change it.","commit_id":"69fdd150b6066039c64ca6658d0cc09788c7d3fd"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"9bbe9e80e3a7204c0521e31308fe149f0a51794d","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 \"SLU (Skip Level Upgrade)\" release."},{"line_number":55,"context_line":"Upgrades will be supported between a SLU base release and the next SLU release."},{"line_number":56,"context_line":"Each SLU release will be SLU base release for the next SLU release."},{"line_number":57,"context_line":"In addition upgrades between adjacent major releases will continue to be"}],"source_content_type":"text/x-rst","patch_set":2,"id":"41b71937_065ec585","line":54,"range":{"start_line":54,"start_character":20,"end_line":54,"end_character":23},"in_reply_to":"1c42f364_4365c0d2","updated":"2023-03-02 11:35:33.000000000","message":"i was not aware of that.\ni personally really hate the one that has been choseen as its rahter clunky so i cahnged it as i did not think it had been given much tough based on what was used.\n\nobvtiously that was wrong given this context but\n\n\"Skip Level Upgrade Release Process release\" sound much less natural then \n\"Skip Level Upgrade release\" to my ears and the fact that peopel will call it a slurp release instead actuly make it worse.","commit_id":"69fdd150b6066039c64ca6658d0cc09788c7d3fd"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"9500996319b59d5083252ad4a1d3545e88000b0c","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 \"SLU (Skip Level Upgrade)\" release."},{"line_number":55,"context_line":"Upgrades will be supported between a SLU base release and the next SLU release."},{"line_number":56,"context_line":"Each SLU release will be SLU base release for the next SLU release."},{"line_number":57,"context_line":"In addition upgrades between adjacent major releases will continue to be"}],"source_content_type":"text/x-rst","patch_set":2,"id":"c429ecd4_cd9a1438","line":54,"range":{"start_line":54,"start_character":20,"end_line":54,"end_character":23},"in_reply_to":"41b71937_065ec585","updated":"2023-05-17 11:23:37.000000000","message":"there was discussion about it long time ago. We had voting and that\u0027s what won (with just one vote IIRC) 😊","commit_id":"69fdd150b6066039c64ca6658d0cc09788c7d3fd"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"9474f41ef7c7b5dc897595b7a04065c663ef69d4","unresolved":true,"context_lines":[{"line_number":59,"context_line":"the six-month cycle will deploy every release (\"SLU\" and \"not-SLU\")"},{"line_number":60,"context_line":"as they always have. Deployments wishing to move to a one year upgrade cycle will"},{"line_number":61,"context_line":"synchronize on a \"SLU\" release, and then skip the following \"not-SLU\""},{"line_number":62,"context_line":"release, upgrading when the subsequent \"SLU\" is released."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"Our letter-based release naming scheme is about to wrap back around to"},{"line_number":65,"context_line":"A, so the proposal is that the \"new A\" release be the first one where"}],"source_content_type":"text/x-rst","patch_set":2,"id":"a0be96a7_5da9acfe","line":62,"updated":"2023-03-01 14:44:30.000000000","message":"IMHO, This is much more complicated to read and understand, with releases first being a target and then a base, etc. None of that is necessary to understand that you can go from SLURP to the next.","commit_id":"69fdd150b6066039c64ca6658d0cc09788c7d3fd"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"701b7f497ce031525bc7241475b41fe85a51e2b1","unresolved":true,"context_lines":[{"line_number":59,"context_line":"the six-month cycle will deploy every release (\"SLU\" and \"not-SLU\")"},{"line_number":60,"context_line":"as they always have. Deployments wishing to move to a one year upgrade cycle will"},{"line_number":61,"context_line":"synchronize on a \"SLU\" release, and then skip the following \"not-SLU\""},{"line_number":62,"context_line":"release, upgrading when the subsequent \"SLU\" is released."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"Our letter-based release naming scheme is about to wrap back around to"},{"line_number":65,"context_line":"A, so the proposal is that the \"new A\" release be the first one where"}],"source_content_type":"text/x-rst","patch_set":2,"id":"e3b03936_538e65a0","line":62,"in_reply_to":"a0be96a7_5da9acfe","updated":"2023-03-01 14:50:36.000000000","message":"Yeah we could just add a detail below saying that even if a SLURP release exists, it can\u0027t be possible to not skip-level-upgrade to it, if the other release is not.","commit_id":"69fdd150b6066039c64ca6658d0cc09788c7d3fd"}]}