)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bad956de34f8988ff78b1f396193e77c9f50cc2e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f506d1fe_10498cb7","updated":"2023-07-18 16:11:03.000000000","message":"I agree with the proposal overall and this is what we agreed in TC meeting. Thanks Kristi for updating.\n\nA Few comments and my main point is to define the \u0027transitioning the unmaintained to EOL\u0027 policy also. One suggestion inline","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"961e5ae907712a509d498334e95a83358bb316f3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b6ac4e17_07f5eb26","updated":"2023-07-19 14:12:23.000000000","message":"I was thinking about this again, and there seem to be some discrepancies between what was said at yesterday\u0027s TC meeting and what\u0027s in this doc.  I wrote up my understanding of how this is supposed to work in an etherpad (sorry, JayF):\n\nhttps://etherpad.opendev.org/p/openstack-unmaintained-workflow","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"440283c036d86f65ebebcf924cfcb0ee4d2f3980","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"0bf7d173_4fda8f2b","updated":"2023-07-20 08:02:32.000000000","message":"Left a few comments but there is already a long list of other ones...","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"e556c99b05d1eadc35e496a01723d408159c663e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"491ca406_f4aba55e","updated":"2023-07-18 17:51:29.000000000","message":"Left some questions and comments inline.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"14567554859abc3f1701bf9397f424852c1d968f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c21e0796_63093fb0","updated":"2023-07-18 14:34:25.000000000","message":"Much happier with this proposal than the last one, so thanks. I think we need to nail down the constant renewal process, or define a EOL (and potential resurrection of post-EOL branches) policy/timeline if not.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"548d8266e1d1f0e08d001919179702361e502b6c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"0d739b63_6f63dab6","in_reply_to":"43633420_ca14f2da","updated":"2023-07-18 17:08:36.000000000","message":"Yeah, it is very difficult to get the external help until upstream is already maintaining. This impression to operators is not good but at some point we also failed to communicate the expectation in better way. Let\u0027s see if this new policy will solve that. But Thanks Elod for all your effort to keep them working as much as possible.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"d0f690cc18340463b78d6f2a64a63503391c5f05","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"400c4613_63cdd1f6","in_reply_to":"b6ac4e17_07f5eb26","updated":"2023-07-19 16:26:23.000000000","message":"at the time of writing this the current content looks ok to me as a baseline of how thigns could evovle.\n\ni think this readonly link\nhttps://etherpad.opendev.org/p/r.761310e647af81b57b3823941372707e\nor this one woudl act as a permalink\nhttps://etherpad.opendev.org/p/openstack-unmaintained-workflow/timeslider#583","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"988b172facc8942ed284dfa42dca01bb03cc8453","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"43633420_ca14f2da","in_reply_to":"f506d1fe_10498cb7","updated":"2023-07-18 16:58:17.000000000","message":"Yepp, thanks Kristi, for dealing with this.\nI understand the pain around EM and accept the will of the community, but I\u0027m a bit sad that EM haven\u0027t reached the goal we wanted with it, as EM did not attract more maintainers.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bc7a1b28665f31563af0d94cff057814eef0553e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"dc579fdf_c4684335","updated":"2023-07-24 17:32:09.000000000","message":"I am not sure of we are doing voting on this, if yes then i can.\n\nThis almost looks good except \u0027Unmaintained -\u003e EOL\u0027 policy which is little strict. Keeping only 2 unmaintained branches does not provide much value to people on older branch and want to maintain them. I think moving to EOL policy can be time-based for example after 4 years (or 3 maybe) of release.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"d2c5d3c2cc0dcf129851e6c40b3acf1e5f7a40a7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"48f182b3_12d2bcca","updated":"2023-07-24 12:46:00.000000000","message":"The latest revision:\n\n1. Changes length of unmaintained branches to 3 years \u003d 2 unmaintained branches. This mostly aligns with the length of support for Ubuntu and Python which is 5 years ( -2 years depending on OpenStack release timing).\n2. Reintroduces the opt-in mechanism for the second unmaintained branch, makes the first one automatic.\n3. Mentions group membership decisions done by a Unmaintained branch liaison that is assigned by the PTL.\n4. Changes wording of CI to mention at most monthly periodic frequence and removes restriction on tempest testing.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"0b1a871c09114c94a618b181e8b48ea35675d0b4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"eb49df94_dae7b107","updated":"2023-07-24 14:50:57.000000000","message":"This incorporates all the issues we\u0027ve discussed so far.  A few suggestions for clarification noted inline.\n\nDon\u0027t know if this will help anyone else, but I sketched out how this works over the next several cycles: https://etherpad.opendev.org/p/openstack-unmaintained-timeframe","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"6b216eecc55a67955c724b95ee205220ef8e2f4c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"60744b0a_b28a8456","updated":"2023-07-24 16:47:04.000000000","message":"This looks better to me. One minor (non-vote-influencing) question inline and several of the other editing comments look reasonable.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"c452a27b38902ea40ec4985af55814c93adbd425","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"9ba01c3b_b238a68e","updated":"2023-07-24 19:08:19.000000000","message":"thanks for clarification on counting the time on releases. 1 last comment inline otherwise this looks good to me","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"27cf98d70e44e714a7348340a706c9a7859fe7e0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"06d989a6_a1a2e6e5","in_reply_to":"dc579fdf_c4684335","updated":"2023-07-24 18:42:34.000000000","message":"2 unmaintained SLURP branches would mean ~3 years from release. 1.5 years of supports and 2 years for the two SLURPs.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b045392e0ebf263def9a714dc4f8b8c00a1988ce","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"2e3dd77c_a8d96326","updated":"2023-07-24 20:14:27.000000000","message":"lgtm for SLURP policy. I just realize that we need to mention policy about releases before SLURP concept.","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"541cb95447a7e0d04d28fb7910c315e0cc1cf960","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"8cd8683f_34af149e","updated":"2023-07-24 21:08:25.000000000","message":"this lgtm, thanks. 1 comment to mention opt-in in-charge as \u0027 Unmaintained branch liaison\u0027 for consistency","commit_id":"58d525e1ba1f80537ea73a2623449ad2a4554d2d"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"aafec39dcc164c07f0a8f853ad57192c4cf4110f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"c7e3d540_9ffe7125","updated":"2023-08-01 16:04:42.000000000","message":"I agree with the spirit of this proposal, but I\u0027d like to see some of the language in comments incorporated directly into the text.  In particular, these comments:\n\nJayF comment Jul 25, 2023, 6:12:06 PM UTC-04:00\n\u003e So I spoke with Kristi some about this concern, discovered this should be possible:\n\u003e - Upon the 18 month anniversary of a branch, the unmaintained/ version of that branch is cut\n\u003e - The PTL can then, upon that branch being created, put out a call for interested parties to be the unmaintained branch liason (I still don\u0027t like PTL being the pivot here)\n\u003e - If nobody answers that call in say, 2 weeks, the unmaintained/ branch can be closed early and EOL\u0027d.\n\nKristi comment Jul 25, 2023, 6:21:54 PM UTC-04:00\n\u003e Want to make clear there is no language here that prohibits a ptl/unmaintained liaison from dropping a branch earlier if there is no interest in it, or for whatever reason they take that decision.\n\nThe reason I\u0027d like this spelled out explicitly is because of this JayF comment:\n\u003e I find it difficult to believe that a majority of the TC will be OK with a project team going this route, after asking the Cinder team to stop doing basically exactly this.\n\nI agree with Jay\u0027s perception here, because there was nothing in the old EM description that prohibited Cinder from EOLing all current EM branches, yet when we did, people freaked out.  Which was all to the good, because it has brought us to the point of replacing the old EM policy with an Unmaintained policy that makes things more clear.  Still, I\u0027d like to see Kristi\u0027s point that nothing prohibits a project from dropping an Unmaintained branch early, be made explicit in the text of this proposal.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"3cf057f3e8643a61d5e63de7322066393544a9fd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"ad79ef82_b9b8ee1e","updated":"2023-07-25 18:40:38.000000000","message":"I will have trouble voting RC+1 to a proposal that still places *any* responsibility for unmaintained/ branches on project teams, including PTLs.\n\nIf we\u0027re going to have a unmaintained branch; don\u0027t make me (as a PTL) decide what the bar is to be a core on it -- I don\u0027t want to draw that line, and if I draw it, it won\u0027t be as flexible as folks would hope, I suspect.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5988a0f45fb21f45fe8f798dff0c1b5b62d76f43","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"4811cdee_d65a018f","updated":"2023-07-25 14:49:28.000000000","message":"Question inline.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"b8fcecc9ab9b1bd2210479431c55f0d0cc6e378f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"8b586ecf_71eb8df3","updated":"2023-07-24 21:19:37.000000000","message":"Question inline.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"3dba644dd933a48a3d0965c80a5e697e9b239d14","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"e1ed1065_9e1d82bd","updated":"2023-07-25 08:23:44.000000000","message":"im generally ok with this as proposed.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b0b989e364f4533c39961e597cf3f25cf500012d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"1f198025_786e51ba","updated":"2023-07-25 00:39:11.000000000","message":"this lgtm, thanks Kristi for the updates.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"e818300c2485edd2276694e99b8e1bff45777b04","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"53777024_b7b0c6d3","in_reply_to":"c7e3d540_9ffe7125","updated":"2023-08-01 17:00:45.000000000","message":"Fair point, I also agree on incorporating the above explicitly and will do so today.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"d4741ead4680635eeb4c639527967c0d74080102","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"04b432e6_90ee26b5","in_reply_to":"c7e3d540_9ffe7125","updated":"2023-08-01 17:00:49.000000000","message":"sure, we can mention that explicitly if that make the process clear, no harm in being very explicit on things.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"40853868fa10b03943efdcbe30de89cc2dd9f625","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":7,"id":"ec851381_a3668cfa","updated":"2023-08-09 07:01:41.000000000","message":"Just to make my comment visible, I will -1 right now.\n\nWe\u0027re talking a lot about opting-in and opting-out, while never say what this does mean. My assumption that this will done through releases team process.\n\nSo will we cover/add reference to that process once it will be ready in a follow-up, or maybe it\u0027s worth to add a statement, that this is up to releases team (with help of TC and other interested parties) to come up with a process right away?","commit_id":"6181213985a477f5849e59d37685d9a8527bbb49"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"63747e3de5f0ff4e82480e577923e4454583d503","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"5dce4769_5290def1","updated":"2023-08-08 18:27:56.000000000","message":"My concerns have been addressed.  This is a definite improvement on the Extended Maintenance experiment!","commit_id":"6181213985a477f5849e59d37685d9a8527bbb49"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"043fc66c9f603ab508cbe3d2e98ea06a0253c363","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"4be5a78f_6e25f50e","updated":"2023-08-08 14:44:30.000000000","message":"This still doesn\u0027t extract the PTL from having UM-related responsibilities, but I think the recent edits represent a good compromise.","commit_id":"6181213985a477f5849e59d37685d9a8527bbb49"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"28d3e1bc6e7b1120cba3f10c73ea9f74800775fd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"6bec26ac_e332f672","updated":"2023-08-09 11:00:12.000000000","message":"i ack\u0027d or marked resoved alot of the old comments form patchset 2/3 just to clean up the doc.\n\none comment inline but im ok with the over all direction","commit_id":"6181213985a477f5849e59d37685d9a8527bbb49"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"9daf1f17d67f0274e63c5a3651f249ac9effa1e8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"f47d6ac9_ba616e7c","updated":"2023-08-08 19:12:28.000000000","message":"lgtm, minor change from previous version which is good explicit explanation.","commit_id":"6181213985a477f5849e59d37685d9a8527bbb49"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"e0fce1e2bd528fc2caa27eafe8785c844b2158fb","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":7,"id":"8263115c_33b4fe8a","in_reply_to":"228c8d00_88bcd7a8","updated":"2023-08-22 13:26:20.000000000","message":"This process will be documented in the project team guide. I\u0027m adding an agenda item in today\u0027s meeting to discuss the next steps in implementing this resolution. In the meanwhile, I\u0027m moving forward with merging it.","commit_id":"6181213985a477f5849e59d37685d9a8527bbb49"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"dc901095030ee2e70b310e6c791e6129a1db5aaf","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":7,"id":"228c8d00_88bcd7a8","in_reply_to":"ec851381_a3668cfa","updated":"2023-08-09 07:03:52.000000000","message":"s/what this does mean/how this should be done/","commit_id":"6181213985a477f5849e59d37685d9a8527bbb49"}],"resolutions/20230707-extended-maintenance-new-requirements.rst":[{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"d3e056002c0fdd7a04565a703b9ee2fe7a590070","unresolved":true,"context_lines":[{"line_number":18,"context_line":"  maintained and may not receive security or bug fixes, or are in"},{"line_number":19,"context_line":"  a state of not being able to merge those fixes if proposed."},{"line_number":20,"context_line":"- There is a false expectation from users and operators that these branches"},{"line_number":21,"context_line":"  are in a state of maintenance from the project team and receiving the above."},{"line_number":22,"context_line":"- Project teams have felt a responsibility themselves to attempt to maintain"},{"line_number":23,"context_line":"  these branches due to the above expectation, in the absence of external"},{"line_number":24,"context_line":"  actors (operators, users, vendors, etc.)"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da9b01eb_7bff326e","line":21,"range":{"start_line":21,"start_character":11,"end_line":21,"end_character":31},"updated":"2023-07-18 16:10:30.000000000","message":"rather: state of fully maintained\n\nEM does not mean that **every** bugfix will be backported and merged. only the ones that **someone** proposes and **stable maintainers** of the project reviews them. I think this was the main misconception, this was not emphasized enough.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"d3e056002c0fdd7a04565a703b9ee2fe7a590070","unresolved":true,"context_lines":[{"line_number":21,"context_line":"  are in a state of maintenance from the project team and receiving the above."},{"line_number":22,"context_line":"- Project teams have felt a responsibility themselves to attempt to maintain"},{"line_number":23,"context_line":"  these branches due to the above expectation, in the absence of external"},{"line_number":24,"context_line":"  actors (operators, users, vendors, etc.)"},{"line_number":25,"context_line":"- These branches are taking attention and resources away from maintained"},{"line_number":26,"context_line":"  branches and new development."},{"line_number":27,"context_line":"- There are no clear processes for transitioning a branch from EM to EOL, and"}],"source_content_type":"text/x-rst","patch_set":1,"id":"4ecea9bb_4bbd9fdb","line":24,"updated":"2023-07-18 16:10:30.000000000","message":"note: Project teams actually EOL\u0027d their old branches where they decided to not to waste resource / time on it. The problem is more with QA repositories as those cannot be EOL\u0027d as long as there are other projects that are using that old branch.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"b2b79abab41ffeb8d24c48075ee1868005184263","unresolved":true,"context_lines":[{"line_number":24,"context_line":"  actors (operators, users, vendors, etc.)"},{"line_number":25,"context_line":"- These branches are taking attention and resources away from maintained"},{"line_number":26,"context_line":"  branches and new development."},{"line_number":27,"context_line":"- There are no clear processes for transitioning a branch from EM to EOL, and"},{"line_number":28,"context_line":"  due to the project being manual, the interdependencies in testing between"},{"line_number":29,"context_line":"  projects, and the burden and goodwill required to transition a project from"},{"line_number":30,"context_line":"  EM to EOL, only 3 branches have done so in the 5 years since the introduction"}],"source_content_type":"text/x-rst","patch_set":1,"id":"f9655cea_a0212bf3","line":27,"range":{"start_line":27,"start_character":2,"end_line":27,"end_character":72},"updated":"2023-07-18 17:44:31.000000000","message":"This is most confusing part in whole EM idea, as it is really weird of how de-synced projects are in transitioning between EM -\u003e EOL.\n\nFrom compliance perspective, once branch is EM-ed as operator I need to constantly monitor if any of projects have moved to EOL from EM, and if they did, do region upgrade ASAP, which in fact impacts planning and priorities.\n\nSo as end-user not having a contract with RedHat, EMs are pretty much useless with current policy of EM -\u003e EOL transition.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"14567554859abc3f1701bf9397f424852c1d968f","unresolved":true,"context_lines":[{"line_number":25,"context_line":"- These branches are taking attention and resources away from maintained"},{"line_number":26,"context_line":"  branches and new development."},{"line_number":27,"context_line":"- There are no clear processes for transitioning a branch from EM to EOL, and"},{"line_number":28,"context_line":"  due to the project being manual, the interdependencies in testing between"},{"line_number":29,"context_line":"  projects, and the burden and goodwill required to transition a project from"},{"line_number":30,"context_line":"  EM to EOL, only 3 branches have done so in the 5 years since the introduction"},{"line_number":31,"context_line":"  of the policy."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9ae29827_8140d814","line":28,"range":{"start_line":28,"start_character":13,"end_line":28,"end_character":20},"updated":"2023-07-18 14:34:25.000000000","message":"\"process\" ?","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"d2c5d3c2cc0dcf129851e6c40b3acf1e5f7a40a7","unresolved":false,"context_lines":[{"line_number":25,"context_line":"- These branches are taking attention and resources away from maintained"},{"line_number":26,"context_line":"  branches and new development."},{"line_number":27,"context_line":"- There are no clear processes for transitioning a branch from EM to EOL, and"},{"line_number":28,"context_line":"  due to the project being manual, the interdependencies in testing between"},{"line_number":29,"context_line":"  projects, and the burden and goodwill required to transition a project from"},{"line_number":30,"context_line":"  EM to EOL, only 3 branches have done so in the 5 years since the introduction"},{"line_number":31,"context_line":"  of the policy."}],"source_content_type":"text/x-rst","patch_set":1,"id":"2604ea76_7f0745a7","line":28,"range":{"start_line":28,"start_character":13,"end_line":28,"end_character":20},"in_reply_to":"9ae29827_8140d814","updated":"2023-07-24 12:46:00.000000000","message":"Done","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"d3e056002c0fdd7a04565a703b9ee2fe7a590070","unresolved":true,"context_lines":[{"line_number":28,"context_line":"  due to the project being manual, the interdependencies in testing between"},{"line_number":29,"context_line":"  projects, and the burden and goodwill required to transition a project from"},{"line_number":30,"context_line":"  EM to EOL, only 3 branches have done so in the 5 years since the introduction"},{"line_number":31,"context_line":"  of the policy."},{"line_number":32,"context_line":"- There are currently 7 extended maintenance branches and this is starting"},{"line_number":33,"context_line":"  to also affect the good operation of the QA infrastructure."},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1e8ecf10_72118230","line":31,"updated":"2023-07-18 16:10:30.000000000","message":"I understand that mostly PTLs, who have to deal with EOL\u0027ing, are aware of the EOL\u0027ing (steps/process) [1] (and that it is not detailed enough), and rest of the community has some grey fog around the real meaning of EM.\n\nNote: there is some mismatch here: EOL\u0027ing a **series** and EOL\u0027ing a **stable branch of a project** are **not** the same thing.\n- we have 3 **series** that is completely EOL\u0027d (ocata, pike, queens)\n- some of the projects have been EOL\u0027d newer branches (per project!) up to victoria (rocky, stein, train, ussuri, victoria)\n\n[1] https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-life","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"440283c036d86f65ebebcf924cfcb0ee4d2f3980","unresolved":true,"context_lines":[{"line_number":28,"context_line":"  due to the project being manual, the interdependencies in testing between"},{"line_number":29,"context_line":"  projects, and the burden and goodwill required to transition a project from"},{"line_number":30,"context_line":"  EM to EOL, only 3 branches have done so in the 5 years since the introduction"},{"line_number":31,"context_line":"  of the policy."},{"line_number":32,"context_line":"- There are currently 7 extended maintenance branches and this is starting"},{"line_number":33,"context_line":"  to also affect the good operation of the QA infrastructure."},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"f16230a3_bad3c0f2","line":31,"in_reply_to":"1e8ecf10_72118230","updated":"2023-07-20 08:02:32.000000000","message":"Most of the difficulties when EOLing is to make sure that the other projects CI jobs are not getting issues if they try to use the EOLed project, but yah.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"d3e056002c0fdd7a04565a703b9ee2fe7a590070","unresolved":true,"context_lines":[{"line_number":30,"context_line":"  EM to EOL, only 3 branches have done so in the 5 years since the introduction"},{"line_number":31,"context_line":"  of the policy."},{"line_number":32,"context_line":"- There are currently 7 extended maintenance branches and this is starting"},{"line_number":33,"context_line":"  to also affect the good operation of the QA infrastructure."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Goals"},{"line_number":36,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":1,"id":"52d817c5_91a5e2b8","line":33,"updated":"2023-07-18 16:10:30.000000000","message":"yes, this is clearly the biggest problem of EM. Active QA developers \u0026 maintainers number is too low, and an EM branch is really dependent on the QA repositories (devstack, tempest, grenade).","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"440283c036d86f65ebebcf924cfcb0ee4d2f3980","unresolved":true,"context_lines":[{"line_number":30,"context_line":"  EM to EOL, only 3 branches have done so in the 5 years since the introduction"},{"line_number":31,"context_line":"  of the policy."},{"line_number":32,"context_line":"- There are currently 7 extended maintenance branches and this is starting"},{"line_number":33,"context_line":"  to also affect the good operation of the QA infrastructure."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Goals"},{"line_number":36,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":1,"id":"cf2450ba_b4fb67d0","line":33,"in_reply_to":"128f2c15_edf2fc6e","updated":"2023-07-20 08:02:32.000000000","message":"+1, honestly that\u0027s a long number of EM branches.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"14915d7a321a0d667e4a6c5728258660b52c3186","unresolved":true,"context_lines":[{"line_number":30,"context_line":"  EM to EOL, only 3 branches have done so in the 5 years since the introduction"},{"line_number":31,"context_line":"  of the policy."},{"line_number":32,"context_line":"- There are currently 7 extended maintenance branches and this is starting"},{"line_number":33,"context_line":"  to also affect the good operation of the QA infrastructure."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Goals"},{"line_number":36,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":1,"id":"128f2c15_edf2fc6e","line":33,"in_reply_to":"306e46fb_615d1d1a","updated":"2023-07-18 18:01:13.000000000","message":"yeah, I was mostly doing the EM testing pinning of Tempest and making test work on old tempest and as these branches are growing in number I am loosing my motivation.  QA team still facing fewer contributor and is in upstream opportunity for many years but no help.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"b2b79abab41ffeb8d24c48075ee1868005184263","unresolved":true,"context_lines":[{"line_number":30,"context_line":"  EM to EOL, only 3 branches have done so in the 5 years since the introduction"},{"line_number":31,"context_line":"  of the policy."},{"line_number":32,"context_line":"- There are currently 7 extended maintenance branches and this is starting"},{"line_number":33,"context_line":"  to also affect the good operation of the QA infrastructure."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Goals"},{"line_number":36,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":1,"id":"306e46fb_615d1d1a","line":33,"in_reply_to":"52d817c5_91a5e2b8","updated":"2023-07-18 17:44:31.000000000","message":"+1, we\u0027re leaving EMs for too long.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"bfc80a1220a0337ab007dda7ebf87a320cd2d4bb","unresolved":true,"context_lines":[{"line_number":30,"context_line":"  EM to EOL, only 3 branches have done so in the 5 years since the introduction"},{"line_number":31,"context_line":"  of the policy."},{"line_number":32,"context_line":"- There are currently 7 extended maintenance branches and this is starting"},{"line_number":33,"context_line":"  to also affect the good operation of the QA infrastructure."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Goals"},{"line_number":36,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":1,"id":"a6aaf364_99cca847","line":33,"in_reply_to":"cf2450ba_b4fb67d0","updated":"2023-07-24 14:26:14.000000000","message":"Just for reference for the coming generations for Neutron these are for example (24. July 2023):\nstable/2023.1\nstable/zed\nstable/yoga\nstable/xena\nstable/wallaby\nstable/victoria\nstable/ussuri","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"d3e056002c0fdd7a04565a703b9ee2fe7a590070","unresolved":true,"context_lines":[{"line_number":39,"context_line":""},{"line_number":40,"context_line":"- We need better communication with regards to the status of these branches,"},{"line_number":41,"context_line":"  and of them not being maintained by or being the responsibility of the"},{"line_number":42,"context_line":"  project teams."},{"line_number":43,"context_line":"- There is still value and desire in allowing a collaborating ground to"},{"line_number":44,"context_line":"  backport fixes beyond just the officially maintained releases."},{"line_number":45,"context_line":"- There is a need for a clear step-by-step process when transitioning a branch"}],"source_content_type":"text/x-rst","patch_set":1,"id":"8904eae4_1d986007","line":42,"updated":"2023-07-18 16:10:30.000000000","message":"Better communication is clearly needed.\n\nnote: I think that there is no such actor as *external maintainer*. a maintainer has to somewhat become part of a (project) maintainer group.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"d2c5d3c2cc0dcf129851e6c40b3acf1e5f7a40a7","unresolved":false,"context_lines":[{"line_number":39,"context_line":""},{"line_number":40,"context_line":"- We need better communication with regards to the status of these branches,"},{"line_number":41,"context_line":"  and of them not being maintained by or being the responsibility of the"},{"line_number":42,"context_line":"  project teams."},{"line_number":43,"context_line":"- There is still value and desire in allowing a collaborating ground to"},{"line_number":44,"context_line":"  backport fixes beyond just the officially maintained releases."},{"line_number":45,"context_line":"- There is a need for a clear step-by-step process when transitioning a branch"}],"source_content_type":"text/x-rst","patch_set":1,"id":"53a7fa9c_79e50785","line":42,"in_reply_to":"64511d88_20ff2195","updated":"2023-07-24 12:46:00.000000000","message":"Done","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"e556c99b05d1eadc35e496a01723d408159c663e","unresolved":true,"context_lines":[{"line_number":39,"context_line":""},{"line_number":40,"context_line":"- We need better communication with regards to the status of these branches,"},{"line_number":41,"context_line":"  and of them not being maintained by or being the responsibility of the"},{"line_number":42,"context_line":"  project teams."},{"line_number":43,"context_line":"- There is still value and desire in allowing a collaborating ground to"},{"line_number":44,"context_line":"  backport fixes beyond just the officially maintained releases."},{"line_number":45,"context_line":"- There is a need for a clear step-by-step process when transitioning a branch"}],"source_content_type":"text/x-rst","patch_set":1,"id":"64511d88_20ff2195","line":42,"in_reply_to":"8904eae4_1d986007","updated":"2023-07-18 17:51:29.000000000","message":"Elod has a good point.  Maybe restate this as:\n\nWe need better communication with regard to the status of these branches, specifically, that it is not (and has not been) the responsibility of the project core team to maintain them.  In other words, it is not the responsibility of each project\u0027s core team to review, approve, or merge changes, or to keep the CI gates running on these branches.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"14567554859abc3f1701bf9397f424852c1d968f","unresolved":true,"context_lines":[{"line_number":40,"context_line":"- We need better communication with regards to the status of these branches,"},{"line_number":41,"context_line":"  and of them not being maintained by or being the responsibility of the"},{"line_number":42,"context_line":"  project teams."},{"line_number":43,"context_line":"- There is still value and desire in allowing a collaborating ground to"},{"line_number":44,"context_line":"  backport fixes beyond just the officially maintained releases."},{"line_number":45,"context_line":"- There is a need for a clear step-by-step process when transitioning a branch"},{"line_number":46,"context_line":"  through these statuses."}],"source_content_type":"text/x-rst","patch_set":1,"id":"740cd73f_8e75d4dc","line":43,"range":{"start_line":43,"start_character":48,"end_line":43,"end_character":68},"updated":"2023-07-18 14:34:25.000000000","message":"\"collaborating ground\" sounds awkward to me. Perhaps \"room to collaborate\" or \"collaboration space\".","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"440283c036d86f65ebebcf924cfcb0ee4d2f3980","unresolved":true,"context_lines":[{"line_number":40,"context_line":"- We need better communication with regards to the status of these branches,"},{"line_number":41,"context_line":"  and of them not being maintained by or being the responsibility of the"},{"line_number":42,"context_line":"  project teams."},{"line_number":43,"context_line":"- There is still value and desire in allowing a collaborating ground to"},{"line_number":44,"context_line":"  backport fixes beyond just the officially maintained releases."},{"line_number":45,"context_line":"- There is a need for a clear step-by-step process when transitioning a branch"},{"line_number":46,"context_line":"  through these statuses."}],"source_content_type":"text/x-rst","patch_set":1,"id":"a7e051bb_e196253f","line":43,"range":{"start_line":43,"start_character":48,"end_line":43,"end_character":68},"in_reply_to":"740cd73f_8e75d4dc","updated":"2023-07-20 08:02:32.000000000","message":"Agreed with Dan here.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"d2c5d3c2cc0dcf129851e6c40b3acf1e5f7a40a7","unresolved":false,"context_lines":[{"line_number":40,"context_line":"- We need better communication with regards to the status of these branches,"},{"line_number":41,"context_line":"  and of them not being maintained by or being the responsibility of the"},{"line_number":42,"context_line":"  project teams."},{"line_number":43,"context_line":"- There is still value and desire in allowing a collaborating ground to"},{"line_number":44,"context_line":"  backport fixes beyond just the officially maintained releases."},{"line_number":45,"context_line":"- There is a need for a clear step-by-step process when transitioning a branch"},{"line_number":46,"context_line":"  through these statuses."}],"source_content_type":"text/x-rst","patch_set":1,"id":"71da8173_9aeaf83f","line":43,"range":{"start_line":43,"start_character":48,"end_line":43,"end_character":68},"in_reply_to":"a7e051bb_e196253f","updated":"2023-07-24 12:46:00.000000000","message":"Done","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"440283c036d86f65ebebcf924cfcb0ee4d2f3980","unresolved":true,"context_lines":[{"line_number":42,"context_line":"  project teams."},{"line_number":43,"context_line":"- There is still value and desire in allowing a collaborating ground to"},{"line_number":44,"context_line":"  backport fixes beyond just the officially maintained releases."},{"line_number":45,"context_line":"- There is a need for a clear step-by-step process when transitioning a branch"},{"line_number":46,"context_line":"  through these statuses."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"This resolution therefore attempts to preserve the ability for backports to be"}],"source_content_type":"text/x-rst","patch_set":1,"id":"a425552c_3cbd6a61","line":45,"range":{"start_line":45,"start_character":22,"end_line":45,"end_character":50},"updated":"2023-07-20 08:02:32.000000000","message":"but the process for EOLing is already documented, what do you exactly mean about a \"process\" ?","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"cef78caedc3a06f564a776dda2083594c3c20ea7","unresolved":true,"context_lines":[{"line_number":42,"context_line":"  project teams."},{"line_number":43,"context_line":"- There is still value and desire in allowing a collaborating ground to"},{"line_number":44,"context_line":"  backport fixes beyond just the officially maintained releases."},{"line_number":45,"context_line":"- There is a need for a clear step-by-step process when transitioning a branch"},{"line_number":46,"context_line":"  through these statuses."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"This resolution therefore attempts to preserve the ability for backports to be"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fbfdd6bb_52537a4c","line":45,"range":{"start_line":45,"start_character":22,"end_line":45,"end_character":50},"in_reply_to":"a425552c_3cbd6a61","updated":"2023-07-20 08:46:59.000000000","message":"Same question/comment here: will this process change?","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"14567554859abc3f1701bf9397f424852c1d968f","unresolved":true,"context_lines":[{"line_number":43,"context_line":"- There is still value and desire in allowing a collaborating ground to"},{"line_number":44,"context_line":"  backport fixes beyond just the officially maintained releases."},{"line_number":45,"context_line":"- There is a need for a clear step-by-step process when transitioning a branch"},{"line_number":46,"context_line":"  through these statuses."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"This resolution therefore attempts to preserve the ability for backports to be"},{"line_number":49,"context_line":"proposed and merged to unmaintained branches, while improving communication"}],"source_content_type":"text/x-rst","patch_set":1,"id":"8eda27ff_c7770c19","line":46,"range":{"start_line":46,"start_character":16,"end_line":46,"end_character":24},"updated":"2023-07-18 14:34:25.000000000","message":"\"phases\" or \"cycles of life\" ?","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"440283c036d86f65ebebcf924cfcb0ee4d2f3980","unresolved":true,"context_lines":[{"line_number":43,"context_line":"- There is still value and desire in allowing a collaborating ground to"},{"line_number":44,"context_line":"  backport fixes beyond just the officially maintained releases."},{"line_number":45,"context_line":"- There is a need for a clear step-by-step process when transitioning a branch"},{"line_number":46,"context_line":"  through these statuses."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"This resolution therefore attempts to preserve the ability for backports to be"},{"line_number":49,"context_line":"proposed and merged to unmaintained branches, while improving communication"}],"source_content_type":"text/x-rst","patch_set":1,"id":"d372051f_f48a2677","line":46,"range":{"start_line":46,"start_character":16,"end_line":46,"end_character":24},"in_reply_to":"8eda27ff_c7770c19","updated":"2023-07-20 08:02:32.000000000","message":"+1","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"d2c5d3c2cc0dcf129851e6c40b3acf1e5f7a40a7","unresolved":false,"context_lines":[{"line_number":43,"context_line":"- There is still value and desire in allowing a collaborating ground to"},{"line_number":44,"context_line":"  backport fixes beyond just the officially maintained releases."},{"line_number":45,"context_line":"- There is a need for a clear step-by-step process when transitioning a branch"},{"line_number":46,"context_line":"  through these statuses."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"This resolution therefore attempts to preserve the ability for backports to be"},{"line_number":49,"context_line":"proposed and merged to unmaintained branches, while improving communication"}],"source_content_type":"text/x-rst","patch_set":1,"id":"a8d47823_6fa220f3","line":46,"range":{"start_line":46,"start_character":16,"end_line":46,"end_character":24},"in_reply_to":"d372051f_f48a2677","updated":"2023-07-24 12:46:00.000000000","message":"Done","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"440283c036d86f65ebebcf924cfcb0ee4d2f3980","unresolved":true,"context_lines":[{"line_number":45,"context_line":"- There is a need for a clear step-by-step process when transitioning a branch"},{"line_number":46,"context_line":"  through these statuses."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"This resolution therefore attempts to preserve the ability for backports to be"},{"line_number":49,"context_line":"proposed and merged to unmaintained branches, while improving communication"},{"line_number":50,"context_line":"around the responsibilities and defining clearer processes."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"The first branch this policy will apply to is stable/yoga. A sister resolution"},{"line_number":53,"context_line":"will be proposed concerning what to do with the current branches under"}],"source_content_type":"text/x-rst","patch_set":1,"id":"709fd1d9_2dbb0de5","line":50,"range":{"start_line":48,"start_character":0,"end_line":50,"end_character":59},"updated":"2023-07-20 08:02:32.000000000","message":"IMO that\u0027s the most important to say in this resolution.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bad956de34f8988ff78b1f396193e77c9f50cc2e","unresolved":true,"context_lines":[{"line_number":49,"context_line":"proposed and merged to unmaintained branches, while improving communication"},{"line_number":50,"context_line":"around the responsibilities and defining clearer processes."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"The first branch this policy will apply to is stable/yoga. A sister resolution"},{"line_number":53,"context_line":"will be proposed concerning what to do with the current branches under"},{"line_number":54,"context_line":"extended maintenance."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Unmaintained branches"},{"line_number":57,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ca51deb5_48ebe9cc","line":54,"range":{"start_line":52,"start_character":0,"end_line":54,"end_character":21},"updated":"2023-07-18 16:11:03.000000000","message":"we are applying it to all the existing branches right? either they are in EM or Maintained. We said we can create new branch for EM with new name and then delete the exiting one. for all future EM (stable/yoga onwards) branches we will name them with this new resolution. \n\nWith this line it seems we are keeping all existing EM as it is and will apply new policy from all future EMs. Maybe we can remove this line to avoid confusion.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"e556c99b05d1eadc35e496a01723d408159c663e","unresolved":true,"context_lines":[{"line_number":49,"context_line":"proposed and merged to unmaintained branches, while improving communication"},{"line_number":50,"context_line":"around the responsibilities and defining clearer processes."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"The first branch this policy will apply to is stable/yoga. A sister resolution"},{"line_number":53,"context_line":"will be proposed concerning what to do with the current branches under"},{"line_number":54,"context_line":"extended maintenance."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"Unmaintained branches"},{"line_number":57,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"e60ce5c9_534ee2e0","line":54,"range":{"start_line":52,"start_character":0,"end_line":54,"end_character":21},"in_reply_to":"ca51deb5_48ebe9cc","updated":"2023-07-18 17:51:29.000000000","message":"I think lines 52-54 should come later in this document, because it is not yet clear what \"this policy\" is (I think you\u0027ll be explaining that in the next section).","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"5abb4cffed738e8b9ab17ddb38536ee9f4cc4726","unresolved":true,"context_lines":[{"line_number":56,"context_line":"Unmaintained branches"},{"line_number":57,"context_line":"---------------------"},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":60,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":61,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, ex."},{"line_number":62,"context_line":"  unmaintained/train."}],"source_content_type":"text/x-rst","patch_set":1,"id":"df97bcbe_fb7431e1","line":59,"updated":"2023-07-18 14:36:05.000000000","message":"I like that new name. IMO it reflects better the intention of it.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"b2b79abab41ffeb8d24c48075ee1868005184263","unresolved":true,"context_lines":[{"line_number":56,"context_line":"Unmaintained branches"},{"line_number":57,"context_line":"---------------------"},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":60,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":61,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, ex."},{"line_number":62,"context_line":"  unmaintained/train."}],"source_content_type":"text/x-rst","patch_set":1,"id":"238abed6_3d9aebf6","line":59,"range":{"start_line":59,"start_character":63,"end_line":59,"end_character":75},"updated":"2023-07-18 17:44:31.000000000","message":"TBH I don\u0027t. I\u0027m not sure what better name can be given, but unmaintained means same as EOL kinda - something you should never-ever-ever use on production.\nIf any auditor will see you\u0027re using unmaintained software - you will hit consequences.\n\nEven Deprecated or Obsolete would be better, but dunno.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"440283c036d86f65ebebcf924cfcb0ee4d2f3980","unresolved":true,"context_lines":[{"line_number":56,"context_line":"Unmaintained branches"},{"line_number":57,"context_line":"---------------------"},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":60,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":61,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, ex."},{"line_number":62,"context_line":"  unmaintained/train."}],"source_content_type":"text/x-rst","patch_set":1,"id":"8acb6aa0_3e36066f","line":59,"range":{"start_line":59,"start_character":63,"end_line":59,"end_character":75},"in_reply_to":"238abed6_3d9aebf6","updated":"2023-07-20 08:02:32.000000000","message":"I\u0027d rather prefer Unmaintained than Deprecated. People can consume those branches if they want, but they need to fix their own problems. Deprecated sends a different signal, which is \u0027soon-to-be-deleted\u0027 which could be confusing for some fresh new Unmaintained branch.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"d2c5d3c2cc0dcf129851e6c40b3acf1e5f7a40a7","unresolved":true,"context_lines":[{"line_number":56,"context_line":"Unmaintained branches"},{"line_number":57,"context_line":"---------------------"},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":60,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":61,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, ex."},{"line_number":62,"context_line":"  unmaintained/train."}],"source_content_type":"text/x-rst","patch_set":1,"id":"03d9d784_418b0173","line":59,"range":{"start_line":59,"start_character":63,"end_line":59,"end_character":75},"in_reply_to":"8acb6aa0_3e36066f","updated":"2023-07-24 12:46:00.000000000","message":"I chose Unmaintained because on https://releases.openstack.org we already use that terminology for EM branches when saying \"Next phase: Unmaintained\" meaning complete EOL, and for the phase when we still support them as \"Maintained\". In other words, the term maintained is well understood by consumers of OpenStack and creates symmetry in using the opposite rather than introducing new terminology.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"440283c036d86f65ebebcf924cfcb0ee4d2f3980","unresolved":true,"context_lines":[{"line_number":56,"context_line":"Unmaintained branches"},{"line_number":57,"context_line":"---------------------"},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":60,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":61,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, ex."},{"line_number":62,"context_line":"  unmaintained/train."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3bc1531a_4311d5f0","line":59,"in_reply_to":"df97bcbe_fb7431e1","updated":"2023-07-20 08:02:32.000000000","message":"+1","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"e556c99b05d1eadc35e496a01723d408159c663e","unresolved":true,"context_lines":[{"line_number":58,"context_line":""},{"line_number":59,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":60,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":61,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, ex."},{"line_number":62,"context_line":"  unmaintained/train."},{"line_number":63,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-maint\" ex."},{"line_number":64,"context_line":"  \"keystone-unmaintained-maint\" will have +2/+W on these branches. This group"}],"source_content_type":"text/x-rst","patch_set":1,"id":"18cfbccc_81474eab","line":61,"range":{"start_line":61,"start_character":60,"end_line":61,"end_character":63},"updated":"2023-07-18 17:51:29.000000000","message":"This would be better as \"for example,\" or \"e.g.,\" (although in the Anne Gentle days, the docs team preference was not to use latin abbreviations).","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"d2c5d3c2cc0dcf129851e6c40b3acf1e5f7a40a7","unresolved":false,"context_lines":[{"line_number":58,"context_line":""},{"line_number":59,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":60,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":61,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, ex."},{"line_number":62,"context_line":"  unmaintained/train."},{"line_number":63,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-maint\" ex."},{"line_number":64,"context_line":"  \"keystone-unmaintained-maint\" will have +2/+W on these branches. This group"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5dbb348c_e65cbf1c","line":61,"range":{"start_line":61,"start_character":60,"end_line":61,"end_character":63},"in_reply_to":"18cfbccc_81474eab","updated":"2023-07-24 12:46:00.000000000","message":"Done","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bad956de34f8988ff78b1f396193e77c9f50cc2e","unresolved":true,"context_lines":[{"line_number":60,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":61,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, ex."},{"line_number":62,"context_line":"  unmaintained/train."},{"line_number":63,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-maint\" ex."},{"line_number":64,"context_line":"  \"keystone-unmaintained-maint\" will have +2/+W on these branches. This group"},{"line_number":65,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":66,"context_line":"  membership is separate of that group."}],"source_content_type":"text/x-rst","patch_set":1,"id":"7947131d_9e05588f","line":63,"range":{"start_line":63,"start_character":28,"end_line":63,"end_character":56},"updated":"2023-07-18 16:11:03.000000000","message":"this name seems confusing with \u0027unmaintained\u0027 and \u0027maint\u0027 both in the name\n\nHow about \"\u003cproject\u003e-unmaintained-core\" ?","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"440283c036d86f65ebebcf924cfcb0ee4d2f3980","unresolved":true,"context_lines":[{"line_number":60,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":61,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, ex."},{"line_number":62,"context_line":"  unmaintained/train."},{"line_number":63,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-maint\" ex."},{"line_number":64,"context_line":"  \"keystone-unmaintained-maint\" will have +2/+W on these branches. This group"},{"line_number":65,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":66,"context_line":"  membership is separate of that group."}],"source_content_type":"text/x-rst","patch_set":1,"id":"826257e7_5ad82882","line":63,"range":{"start_line":63,"start_character":28,"end_line":63,"end_character":56},"in_reply_to":"060c6dc0_42c5b1b2","updated":"2023-07-20 08:02:32.000000000","message":"+1","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"e556c99b05d1eadc35e496a01723d408159c663e","unresolved":true,"context_lines":[{"line_number":60,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":61,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, ex."},{"line_number":62,"context_line":"  unmaintained/train."},{"line_number":63,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-maint\" ex."},{"line_number":64,"context_line":"  \"keystone-unmaintained-maint\" will have +2/+W on these branches. This group"},{"line_number":65,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":66,"context_line":"  membership is separate of that group."}],"source_content_type":"text/x-rst","patch_set":1,"id":"060c6dc0_42c5b1b2","line":63,"range":{"start_line":63,"start_character":28,"end_line":63,"end_character":56},"in_reply_to":"7947131d_9e05588f","updated":"2023-07-18 17:51:29.000000000","message":"I like gmann\u0027s suggestion, it takes advantage of the openstack convention that members of a core team are granted the ability to merge changes.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"d2c5d3c2cc0dcf129851e6c40b3acf1e5f7a40a7","unresolved":false,"context_lines":[{"line_number":60,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":61,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, ex."},{"line_number":62,"context_line":"  unmaintained/train."},{"line_number":63,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-maint\" ex."},{"line_number":64,"context_line":"  \"keystone-unmaintained-maint\" will have +2/+W on these branches. This group"},{"line_number":65,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":66,"context_line":"  membership is separate of that group."}],"source_content_type":"text/x-rst","patch_set":1,"id":"7ab6fe21_8b98047a","line":63,"range":{"start_line":63,"start_character":28,"end_line":63,"end_character":56},"in_reply_to":"826257e7_5ad82882","updated":"2023-07-24 12:46:00.000000000","message":"Done","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"14567554859abc3f1701bf9397f424852c1d968f","unresolved":true,"context_lines":[{"line_number":63,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-maint\" ex."},{"line_number":64,"context_line":"  \"keystone-unmaintained-maint\" will have +2/+W on these branches. This group"},{"line_number":65,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."}],"source_content_type":"text/x-rst","patch_set":1,"id":"e01e7940_3c630adb","line":66,"range":{"start_line":66,"start_character":25,"end_line":66,"end_character":27},"updated":"2023-07-18 14:34:25.000000000","message":"\"from\"","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"d2c5d3c2cc0dcf129851e6c40b3acf1e5f7a40a7","unresolved":false,"context_lines":[{"line_number":63,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-maint\" ex."},{"line_number":64,"context_line":"  \"keystone-unmaintained-maint\" will have +2/+W on these branches. This group"},{"line_number":65,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."}],"source_content_type":"text/x-rst","patch_set":1,"id":"c1b79b64_638299fe","line":66,"range":{"start_line":66,"start_character":25,"end_line":66,"end_character":27},"in_reply_to":"e01e7940_3c630adb","updated":"2023-07-24 12:46:00.000000000","message":"Done","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"8575c56445582de881a805b728d9527ee4e3a248","unresolved":true,"context_lines":[{"line_number":65,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."}],"source_content_type":"text/x-rst","patch_set":1,"id":"27a2e194_24fc88bc","line":68,"updated":"2023-07-18 16:41:38.000000000","message":"we cannot skip non-slurp release either while the non-slurp release is still maintianed.\n\nwhen the non slurp release is EM/unmaintianed i woudl still think very carfully before allowing an intermdiary branch to be skipped.\n\nwe likely either shoudl not allow that or close the branch\nthe chance for divergence and regressiosn if we are not consitent is pretty high when backporting with skips.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"e556c99b05d1eadc35e496a01723d408159c663e","unresolved":true,"context_lines":[{"line_number":65,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."}],"source_content_type":"text/x-rst","patch_set":1,"id":"c58469a0_c31547a0","line":68,"in_reply_to":"27a2e194_24fc88bc","updated":"2023-07-18 17:51:29.000000000","message":"I agree entirely with Sean.  Let\u0027s keep this simple.  I think we want the release team\u0027s backport policies to apply to these unmaintained branches; I am against rewriting the backport policies at this time.\n\nIt follows that if someone wants to keep unmaintained/wallaby open for changes, they must also agree to maintain xena and yoga.  You may want to mention that so that people clearly understand the cost of keeping a branch from going to EOL.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"440283c036d86f65ebebcf924cfcb0ee4d2f3980","unresolved":true,"context_lines":[{"line_number":65,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."}],"source_content_type":"text/x-rst","patch_set":1,"id":"24a0ead4_e173ac21","line":68,"in_reply_to":"84b5a313_01da40cd","updated":"2023-07-20 08:02:32.000000000","message":"See my other point below, I think we need to let the ship sail and assume that Unmaintained branches will have very minimal testing.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"09756e71332c280c0c7cba3950e3861dd168c59d","unresolved":true,"context_lines":[{"line_number":65,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."}],"source_content_type":"text/x-rst","patch_set":1,"id":"d346bd58_60de5cb6","line":68,"in_reply_to":"b4b426e8_ba3779d0","updated":"2023-07-18 19:11:56.000000000","message":"yes that adresses most of my concerns with skipign release.\n\ntheh other concerns i have are ortoganal around not trying to maintain Operating system version that are nolonger supported by there distobution vendor.\n\nhttps://endoflife.date/ubuntu\ni.e. 18.04 went eol 31 May 2023 without a paid supprot contract so i think we should EOL branches that rely on 18.04 which is anything pre victoria\n\nthat is a topic i guess we can adress seperatly form the general cadance.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"67cc661bc33c1bda59452d784bf88f83374fbfff","unresolved":true,"context_lines":[{"line_number":65,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."}],"source_content_type":"text/x-rst","patch_set":1,"id":"b4b426e8_ba3779d0","line":68,"in_reply_to":"c58469a0_c31547a0","updated":"2023-07-18 18:46:15.000000000","message":"This was just discussed in the TC meeting and a number of people (myself included) are in favor of the following proposal. I *think* that it\u0027s in line with Sean\u0027s comment here, specifically about closing any branch before we allow skipping it for backports.\n\nThe idea is that non-SLURP releases would never be eligible for Unmaintained status. Meaning those releases go straight to EOL when they exit the Maintained phase. That limits the number of branches we have in the long-tail Unmaintained phase and also encourages more distributions to rally around and choose the SLURP releases. It would mean that once a non-SLURP goes to EOL, backports to the previous SLURP could be done directly, since the intermediate is now EOL and the branch is deleted. This will reduce the overhead required to get backports to something old but important (like Wallaby currently), will reduce the amount of renewing we have to do (i.e. everything between Wallaby and master) each six months, and the number of CI jobs we have to keep working. We can/should keep the requirement that all SLURPS between the oldest and current have to be in Unmaintained or Maintained state, i.e. no EOL\u0027d SLURP releases between the oldest and current.\n\nSean, are you okay with that?","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"e645f6fe68f63761a9d1d542fc407c78b6b53879","unresolved":true,"context_lines":[{"line_number":65,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."}],"source_content_type":"text/x-rst","patch_set":1,"id":"dde4d1c3_6cef794f","line":68,"in_reply_to":"d346bd58_60de5cb6","updated":"2023-07-18 19:14:36.000000000","message":"I think we\u0027ve been kinda keeping the base OS thing separate from this, although there\u0027s a nod to it in the \"your tests must be working\" stuff.\n\nI know infra has a concern about the age of the base images we\u0027re required to keep. Kristi, I kinda think it might be good to keep that separate, but perhaps we should have a bullet in this document about the max TTL of an unmaintained release being constrained to \"can run on a supported base OS platform\". That dovetails with the \"must have at least one tempest job\" desire expressed here as well.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"2c344f4e69e0384236972e1b48d8a05100f8e36e","unresolved":true,"context_lines":[{"line_number":65,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."}],"source_content_type":"text/x-rst","patch_set":1,"id":"84b5a313_01da40cd","line":68,"in_reply_to":"dde4d1c3_6cef794f","updated":"2023-07-18 19:17:38.000000000","message":"I agree on most of the point but instead of \"must\" I will suggest to recomemnd that. or say if there is no Tempest jobs running the it is kind of indication to move them to EOL so if anyone want to keep them in unmaintained phase for long then keep at least one tempest job working there","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"5abb4cffed738e8b9ab17ddb38536ee9f4cc4726","unresolved":true,"context_lines":[{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a8e4d8c_0a6e0f58","line":69,"updated":"2023-07-18 14:36:05.000000000","message":"what if the CI will not be in the good shape at the end of the cycle? Will it mean that it will automatically go to EOL?","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"bfc80a1220a0337ab007dda7ebf87a320cd2d4bb","unresolved":true,"context_lines":[{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"}],"source_content_type":"text/x-rst","patch_set":1,"id":"636746da_c745293e","line":69,"in_reply_to":"2845c0ff_9d023979","updated":"2023-07-24 14:26:14.000000000","message":"agree with Sean and Sylvain here, setting up a minimal coverage with some static checks, unit tests jobs, and some minimal tempest should be enough for basic checks before merging anything","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"d3e056002c0fdd7a04565a703b9ee2fe7a590070","unresolved":true,"context_lines":[{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3548cd6b_8a12a642","line":69,"in_reply_to":"3a8e4d8c_0a6e0f58","updated":"2023-07-18 16:10:30.000000000","message":"good question, as that is not a given, that a CI is in good shape **even** when a project is in \u0027maintained\u0027 phase.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"8575c56445582de881a805b728d9527ee4e3a248","unresolved":true,"context_lines":[{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"}],"source_content_type":"text/x-rst","patch_set":1,"id":"6e9f9ae4_1e0b35b4","line":69,"in_reply_to":"3a8e4d8c_0a6e0f58","updated":"2023-07-18 16:41:38.000000000","message":"i guess there are two options. if the ci is not fixed the coverage could be reduced provided a minimal level is still functioning. i.e. if one job broke for a specific edgecase e.g. nova-lvm but there is sufficet test coverage in general then that job coudl be removed to restore the ci to good standing\n\notherwise if there is not suffcent test coverage then i think we would eol the branch at that point.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bad956de34f8988ff78b1f396193e77c9f50cc2e","unresolved":true,"context_lines":[{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"}],"source_content_type":"text/x-rst","patch_set":1,"id":"f3b1f241_751b22a3","line":69,"in_reply_to":"3a8e4d8c_0a6e0f58","updated":"2023-07-18 16:11:03.000000000","message":"well, not really. As it is currently that EM testing are best effort so it can be depends on the maintainers of those branches that how much testing they can keep or just unit/pep8 testing also enough if they feel that is enough for some backport things. As it says it is not maintained by upstream so we do not need to worry about commitment of testing.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"e556c99b05d1eadc35e496a01723d408159c663e","unresolved":true,"context_lines":[{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"}],"source_content_type":"text/x-rst","patch_set":1,"id":"a07b31a4_4b4e884c","line":69,"in_reply_to":"6e9f9ae4_1e0b35b4","updated":"2023-07-18 17:51:29.000000000","message":"We need to state clearly what the CI expectations are, otherwise it\u0027s impossible to know what \"in good standing\" means.  I was holding out for a tempest job, but I think I\u0027m losing that battle.  So we should at least say:\n\n- unit tests for python runtimes supported by that branch as indicated in [x].\n- pep8 tests\n\nNo docs? No api-ref? No releasenotes?  (just asking)\n\n\n[x] https://governance.openstack.org/tc/reference/runtimes/","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"43720d9ef96a78729ae7079ea25fdd413a47e6d5","unresolved":true,"context_lines":[{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ab96c82d_660d6bc0","line":69,"in_reply_to":"a07b31a4_4b4e884c","updated":"2023-07-18 18:46:09.000000000","message":"the tox jobs are cheap and break far less then tempest so i would expect the standard tox jobs including docs/releasenotes \nand as i said i woudl hope for at least one tempest josb\n\ne.g. on nova tempest-intergrated-compute\n\nhttps://github.com/openstack/tempest/blob/master/zuul.d/integrated-gate.yaml#L137-L157\nhttps://github.com/openstack/tempest/blob/master/tox.ini#L201C2-L214\n\nthat will provide a minimal baseline \n\ni would actully prefer a multinode job for nova spericicaly but i dont think we need to test everything.\n\nwe can rely on the functional test for move operations that without multi node testing or grenade (which i dont think we shoudl require) you really cant know if its usabel in production so we would have to set expectioant that \nuser need to validate that themselves.\n\nif we decied that tempest is not require then we need to call that out explcitly in this resolution.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"440283c036d86f65ebebcf924cfcb0ee4d2f3980","unresolved":true,"context_lines":[{"line_number":66,"context_line":"  membership is separate of that group."},{"line_number":67,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"}],"source_content_type":"text/x-rst","patch_set":1,"id":"2845c0ff_9d023979","line":69,"in_reply_to":"ab96c82d_660d6bc0","updated":"2023-07-20 08:02:32.000000000","message":"Honestly, if we were being honest, we\u0027d say that CI coverage is not required on unmaintained branches. Of course, like Sean said, at least running unit testing with *one* single Tempest job as non-voting would be a nobrainer and would prevent stupid backport mistakes.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bad956de34f8988ff78b1f396193e77c9f50cc2e","unresolved":true,"context_lines":[{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":1,"id":"88df0a1b_bc0a3af2","line":71,"range":{"start_line":71,"start_character":45,"end_line":71,"end_character":66},"updated":"2023-07-18 16:11:03.000000000","message":"we can have full tempest testing as we have currently by pinning the tempest there. May be we can just say no periodic jobs","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"5abb4cffed738e8b9ab17ddb38536ee9f4cc4726","unresolved":true,"context_lines":[{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":1,"id":"054136f2_bdc91aaf","line":71,"updated":"2023-07-18 14:36:05.000000000","message":"what do You mean by that? There will be no full tempest testing in unmaintained branches at all? Or there will be limited number of jobs like that?","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"86c430e02212ea95708817c2cace0b721415f250","unresolved":true,"context_lines":[{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":1,"id":"29189714_ada07e83","line":71,"in_reply_to":"0484b5b2_446127c4","updated":"2023-07-19 07:22:52.000000000","message":"I agree with Sean here. We have seen that e.g. in neutron stadium projects where we first get rid of the periodic jobs in older branches but then we had so few patches there that we really didn\u0027t know about current state of the project. So we added weekly periodic jobs to at least check once a week if the CI of a project is working fine or we have some issue to fix there. I think that this could be good trade off between resource usage and being more or less up to date with the current state of the branch.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"d3e056002c0fdd7a04565a703b9ee2fe7a590070","unresolved":true,"context_lines":[{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":1,"id":"278cd92f_d39223c3","line":71,"in_reply_to":"054136f2_bdc91aaf","updated":"2023-07-18 16:10:30.000000000","message":"I think if we want to keep some value in the existence of these branches we have to keep some level of testing. Though I understand that testing (legacy zuul jobs) gives the most pain to maintainers / infra team.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"8575c56445582de881a805b728d9527ee4e3a248","unresolved":true,"context_lines":[{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ef44d4e1_312321bd","line":71,"in_reply_to":"054136f2_bdc91aaf","updated":"2023-07-18 16:41:38.000000000","message":"am actullly i think perodic and tempest are kind of table stacks.\non older banches with infrequest changes preodics become more imporant.\n\nso at least the weekly jobs are likely imporant to keep.\n\nif we dont have tempest at all then the branch shoudl not stay open.\n\nnova has quite advance funtional test but i would not condier that to be suffient ot consider the ci to be in good standing.\n\nwe may not need nova-lvm nova-ceph nova multi cell ectra\nbut we need to have at least one tempest job for the service project at least.\n\nclients are proably ok with unit/fucntional tests.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"306f411241e2a6210cef34579e5ecf84be7b8ceb","unresolved":true,"context_lines":[{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":1,"id":"bbbeb402_1e9ebecc","line":71,"range":{"start_line":71,"start_character":45,"end_line":71,"end_character":66},"in_reply_to":"188788df_ee3af33e","updated":"2023-07-19 13:39:54.000000000","message":"Yes, however I would like to note that we\u0027re supposed to be aggressively removing broken jobs in these branches today, yet it\u0027s pretty common (I can think of one case recently) where we jumped through hoops to backport stuff to devstack (et al) to keep jobs working :)","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"306f411241e2a6210cef34579e5ecf84be7b8ceb","unresolved":true,"context_lines":[{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9f0085df_ce6d1b04","line":71,"in_reply_to":"29189714_ada07e83","updated":"2023-07-19 13:39:54.000000000","message":"Well, I\u0027m reflecting the concern from infra, raised by fungi, that we have lots of very old branches running periodic jobs all the time, using resources, and which very rarely see any changes proposed. Perhaps if we could move those to monthly or something like that it would address that concern to some degree.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"ebed816ed2ccb9842022f3d289fe3572af8116a4","unresolved":true,"context_lines":[{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":1,"id":"0484b5b2_446127c4","line":71,"in_reply_to":"4cfa50f7_85077c43","updated":"2023-07-18 17:39:08.000000000","message":"im kind of thinking keeping the tempest-integrated-\u003cservice\u003e job\nwoudl make sense as a minium.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"43720d9ef96a78729ae7079ea25fdd413a47e6d5","unresolved":true,"context_lines":[{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":1,"id":"a79ca4f2_88bb68b0","line":71,"range":{"start_line":71,"start_character":45,"end_line":71,"end_character":66},"in_reply_to":"88df0a1b_bc0a3af2","updated":"2023-07-18 18:46:09.000000000","message":"i guess i am less pushed about keeping perodic then i tought on reflection\n\noptional tempest with a recommendation to remvoe  agressively jobs if they are broken or limit the jobs on unmaintianed branchs i guess woudl better help preseve the ci resouces.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"86c430e02212ea95708817c2cace0b721415f250","unresolved":true,"context_lines":[{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":1,"id":"188788df_ee3af33e","line":71,"range":{"start_line":71,"start_character":45,"end_line":71,"end_character":66},"in_reply_to":"a79ca4f2_88bb68b0","updated":"2023-07-19 07:22:52.000000000","message":"+1 to what Sean said","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"7afbdb3173a536b0a891a9d190621b0222833a59","unresolved":true,"context_lines":[{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":1,"id":"4cfa50f7_85077c43","line":71,"in_reply_to":"bbecb27b_a1df8865","updated":"2023-07-18 16:59:38.000000000","message":"yes, so those tempest jobs can go away naturally due to OS base image not supported or any other requirements like contstraints stop thew running. but let\u0027s just say that unmaintained branches does not need to have periodic jobs everything else is best effort by the maintainters.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"cdb9ff30f4e79a1674fd2aef2668dc6b605ab8fd","unresolved":true,"context_lines":[{"line_number":68,"context_line":"  and the current maintained releases."},{"line_number":69,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":70,"context_line":"  However this is a best-effort CI and to preserve resources for maintained"},{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":1,"id":"bbecb27b_a1df8865","line":71,"in_reply_to":"ef44d4e1_312321bd","updated":"2023-07-18 16:54:40.000000000","message":"\"At least one tempest job\" maybe. We discussed getting rid of the periodics because they spend a ton of CI time running regularly even though nothing has changed in the project branch for months. There\u0027s also the concern of tempest jobs that use OS base images that infra no longer wants to support. Unmaintained is unmaintained, which to me means not fully tested. I think that dropping tempest tests from a very old branch that can\u0027t even run on a supported OS base image is fine with me. Probably means it can be EOLed but ...","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"14567554859abc3f1701bf9397f424852c1d968f","unresolved":true,"context_lines":[{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"}],"source_content_type":"text/x-rst","patch_set":1,"id":"52ec1057_760d0a38","line":74,"updated":"2023-07-18 14:34:25.000000000","message":"I expected to still see something in here about unmaintained branches needing to be constantly renewed to stay alive. Did you intentionally remove that, or mean to keep it?\n\nI think going from stable-\u003eunmaintained automatically once \"for free\" and then requiring a renewal each cycle to keep it that way makes sense to me. Optionally we could say that a branch stays in that state for X cycles afterwards, and then goes EOL if not renewed. That would give some time for a critical mass of people to have materialized that care about it.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"b2b79abab41ffeb8d24c48075ee1868005184263","unresolved":true,"context_lines":[{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"}],"source_content_type":"text/x-rst","patch_set":1,"id":"4c39bd37_b41ec264","line":74,"in_reply_to":"110091d2_61739d5e","updated":"2023-07-18 17:44:31.000000000","message":"As a user I still kinda clueless if I can, and until what time, to rely on unmaintained branches, that they will not just vanish at random time.\n\nSo what I totally like from Dans proposal, is that Unmaintained -\u003e EOL transition should happen at expected timeline. Despite it\u0027s prolonging per year or just having them for X years. But knowing, that branch can go only during some Milestones is important.\n\nAs then, as a user, I can ensure that project I\u0027m interested in is either EOL-ing or renewing the lease and could step-in or have time to agree investment to continue maintenance with management.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"bfc80a1220a0337ab007dda7ebf87a320cd2d4bb","unresolved":true,"context_lines":[{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"}],"source_content_type":"text/x-rst","patch_set":1,"id":"91140758_d8084be1","line":74,"in_reply_to":"1260e421_1db6b0d1","updated":"2023-07-24 14:26:14.000000000","message":"+1, and for Neutron currently we have only stable/ussuri as the oldest branch anyway, and I suppose there\u0027s projects with even shorter list","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"d2c5d3c2cc0dcf129851e6c40b3acf1e5f7a40a7","unresolved":true,"context_lines":[{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"}],"source_content_type":"text/x-rst","patch_set":1,"id":"8a2375dc_130ee36b","line":74,"in_reply_to":"1260e421_1db6b0d1","updated":"2023-07-24 12:46:00.000000000","message":"I think I like the 3 years timeframe as it seems to approximate but not unreasonably exceed the 5 years of support for Ubuntu LTS (5 years - 2 years between releases, depending on timing of OpenStack release). This would mean we have two unmaintained SLURP branches moving forward. That\u0027s reasonable I think.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"cef78caedc3a06f564a776dda2083594c3c20ea7","unresolved":true,"context_lines":[{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1260e421_1db6b0d1","line":74,"in_reply_to":"39f88b39_a2f229c4","updated":"2023-07-20 08:46:59.000000000","message":"Agree with Sean, keeping 4 years of releases (even if these are unmaintained) could be too much.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"14915d7a321a0d667e4a6c5728258660b52c3186","unresolved":true,"context_lines":[{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"}],"source_content_type":"text/x-rst","patch_set":1,"id":"6b615991_a9258450","line":74,"in_reply_to":"4c39bd37_b41ec264","updated":"2023-07-18 18:01:13.000000000","message":"agree, I will suggest 4 years of that release can be good amount (1.5 years in Maintained phase + 2.5 years in Unmaintained phase).\n\nThis way we will keep (counting from the time of latest 2023.1 release):\n\nMaintained:\n1. master\n2. stable/2023.1 (\u003c 6 months of release)\n3. stable/zed (6 months of release)\n4. stable/yoga (12 months of release)\n\nUnmaintained:\n1. unmaintained/xena (1.5 years of release)\n2. unmaintained/wallaby (2 years of release)\n3. unmaintained/victoria (2.5 years of release)\n4. unmaintained/ussuri (3 years of release)\n5. unmaintained/train (3.5 years of release)\n6. unmaintained/stein (4 years of release)\n7. unmaintained/rocky -\u003e EOL ( \u003e 4 years of release)\n\nor we can make it 5 if that timeline seems good.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"61835cc0714fee08ccf897edd9b1092c9c566c7c","unresolved":true,"context_lines":[{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"}],"source_content_type":"text/x-rst","patch_set":1,"id":"6bb1c4d2_63ccb018","line":74,"in_reply_to":"52ec1057_760d0a38","updated":"2023-07-18 14:48:00.000000000","message":"I\u0027m okay with X cycles. \n\nMy remaining concern is that since there was some pushback with regards to the difficulty in testing project A that depends on project B if project B is EOL and a fix is required to unblock project A\u0027s gate.\n\nSo the process of EOL-ing individual projects is suboptimal still.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"43720d9ef96a78729ae7079ea25fdd413a47e6d5","unresolved":true,"context_lines":[{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"}],"source_content_type":"text/x-rst","patch_set":1,"id":"39f88b39_a2f229c4","line":74,"in_reply_to":"6b615991_a9258450","updated":"2023-07-18 18:46:09.000000000","message":"honestly i think that is too long.\n\n3 years (18 months maintained and 18 mounts unmainted) is proably more pargmatic.\na roling 3 slurp window across 2 operating system version i think woudl be more achivable then 5 years.\n\nusing yoga as the first psydo slurp release that woudl mean when we release 2024.1 it would go EOL unless the ci was working and there were active contibutors form outside the project teams keeping it open.\n\ntrain is starting to be problematic for nova and ussuri is not much better so im in favor of eoling train and older branches this cycle.\nAt m3 i also think we shoudl consider if ussuri shoudl be EOL based on ci health.\n\nussuri was the first python3 only release if i recall correctly upstream.\nthe ussuir to train backport is alwasy a pain as you have to be careful to consider if you need to re-add python 2.7 support.\n\nif we move stable/train to unmaintained/train and disabel some jobs we coudl perhap keep it open but given the unresolved CVE, the fact that ubuntu 18.04 is eol\npython 2.7,3.6 and 3.7 are eol upstream i dont think its really reasonabel to keep maintaining it.\nhttps://github.com/openstack/governance/blob/master/reference/runtimes/train.rst\n\nthe victoria runtime was the first to move to 20.04\nhttps://github.com/openstack/governance/blob/master/reference/runtimes/victoria.rst\nthat is why i think we shoudl be considereing eoling ussuri and older at the end of the cycle to avoid issue with ci goign forward.\nthat atleast pulls in python 3.8 supprot as a requirement for all project which has securityupdate till 14 Oct 2024 https://endoflife.date/python","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bad956de34f8988ff78b1f396193e77c9f50cc2e","unresolved":true,"context_lines":[{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"}],"source_content_type":"text/x-rst","patch_set":1,"id":"f3376699_0b3aecb5","line":74,"in_reply_to":"6bb1c4d2_63ccb018","updated":"2023-07-18 16:11:03.000000000","message":"I am not fan of opt-in in this case where we already handover the EM branches maintenance to the separate team.\n\nby \u0027transitioning from maintained to unmaintained\u0027 you mean any new document/guidlines we need to prepare other than exiting one ?\n- https://docs.openstack.org/project-team-guide/stable-branches.html","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"0e42034de93852032adbc123d2ef1967e47bae76","unresolved":true,"context_lines":[{"line_number":71,"context_line":"  branches will not include periodic jobs and full tempest testing."},{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"}],"source_content_type":"text/x-rst","patch_set":1,"id":"110091d2_61739d5e","line":74,"in_reply_to":"f3376699_0b3aecb5","updated":"2023-07-18 16:21:17.000000000","message":"but I think the last option Dan mentioned make sense. I wrote the same kind of option in my next comment. either after X cycle or x number of years we can automatically move the unmaintained to EOL unless approved by the TC.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bad956de34f8988ff78b1f396193e77c9f50cc2e","unresolved":true,"context_lines":[{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"},{"line_number":78,"context_line":"[2]. https://etherpad.opendev.org/p/vancouver-2023-em"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fc1d5575_18d1bea2","line":76,"range":{"start_line":75,"start_character":0,"end_line":76,"end_character":3},"updated":"2023-07-18 16:11:03.000000000","message":"I know we have not concluded it yet but we can discuss and conclude about \u0027transitioning from  unmaintained to EOL\u0027 here.\n\nIMO, we can make \u0027transitioning from  unmaintained to EOL\u0027 automatically after 4 or 5 years of that branch moved to \u0027unmaintained\u0027 unless core team of that branch take the TC exception to keep that open.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"d2c5d3c2cc0dcf129851e6c40b3acf1e5f7a40a7","unresolved":true,"context_lines":[{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"},{"line_number":78,"context_line":"[2]. https://etherpad.opendev.org/p/vancouver-2023-em"}],"source_content_type":"text/x-rst","patch_set":1,"id":"b6edf826_27de77d7","line":76,"range":{"start_line":75,"start_character":0,"end_line":76,"end_character":3},"in_reply_to":"0cdf0c6d_c3f15992","updated":"2023-07-24 12:46:00.000000000","message":"I added a bullet point about the PTL being able to assign a Unmaintained branch liaison. This being separate from the stable branch liaison allows for this person and group to be different.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"86c430e02212ea95708817c2cace0b721415f250","unresolved":true,"context_lines":[{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"},{"line_number":78,"context_line":"[2]. https://etherpad.opendev.org/p/vancouver-2023-em"}],"source_content_type":"text/x-rst","patch_set":1,"id":"4aefa898_77658534","line":76,"range":{"start_line":75,"start_character":0,"end_line":76,"end_character":3},"in_reply_to":"15925692_b5e53157","updated":"2023-07-19 07:22:52.000000000","message":"I have one more question kind of related to this. Who is \"the leader\" of the unmaintained branch? Should there be some liaison for each such branch or PTL of the project should take care of all of those unmaintained branches? I personally don\u0027t think it\u0027s good idea to add this to the PTL\u0027s pile.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"d0f690cc18340463b78d6f2a64a63503391c5f05","unresolved":true,"context_lines":[{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"},{"line_number":78,"context_line":"[2]. https://etherpad.opendev.org/p/vancouver-2023-em"}],"source_content_type":"text/x-rst","patch_set":1,"id":"0cdf0c6d_c3f15992","line":76,"range":{"start_line":75,"start_character":0,"end_line":76,"end_character":3},"in_reply_to":"4aefa898_77658534","updated":"2023-07-19 16:26:23.000000000","message":"liasion to the core/stable team form teh unmaintiend team?\nor unmaintened grop to other groups like release/VMT?\n\ni agree this shoudl not erelaly be lumped on teh PTLs \n\nGiven there woudl be no releases form the unmiantained branches i dont think there need to be a release leaison bu thaving someone form that group attend the team meetings and give a status update for the unmaintianed branches similar to the stabel branch status would not be a terribel idea.\n\ni dont think we shoudl expect the people giving the stable branch updates to also look at the unmaintaned branches.","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"e556c99b05d1eadc35e496a01723d408159c663e","unresolved":true,"context_lines":[{"line_number":72,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":73,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":74,"context_line":"  deletion."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"},{"line_number":77,"context_line":"[1]. https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.html"},{"line_number":78,"context_line":"[2]. https://etherpad.opendev.org/p/vancouver-2023-em"}],"source_content_type":"text/x-rst","patch_set":1,"id":"15925692_b5e53157","line":76,"range":{"start_line":75,"start_character":0,"end_line":76,"end_character":3},"in_reply_to":"fc1d5575_18d1bea2","updated":"2023-07-18 17:51:29.000000000","message":"Another item we need to address is, *who* makes the EOL decision?  Can the project-core team force closure if the unmaintained-core team isn\u0027t active?  Or is this solely the decision of the unmaintained-core team?","commit_id":"ad328961f5162cebecd3d4a60da4ef6b2a9cffd0"}],"resolutions/20230724-unmaintained-branches.rst":[{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"0b1a871c09114c94a618b181e8b48ea35675d0b4","unresolved":true,"context_lines":[{"line_number":51,"context_line":"proposed and merged to unmaintained branches, while improving communication"},{"line_number":52,"context_line":"around the responsibilities and defining clearer processes."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"The first branch this policy will apply to is stable/yoga. A sister resolution"},{"line_number":55,"context_line":"will be proposed concerning what to do with the current branches under"},{"line_number":56,"context_line":"extended maintenance."},{"line_number":57,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"16c84d62_aabeeff8","line":54,"range":{"start_line":54,"start_character":46,"end_line":54,"end_character":57},"updated":"2023-07-24 14:50:57.000000000","message":"It might be worth adding \", which, at the time of this proposal, is the oldest releasable stable branch, and which is scheduled to transition to the next phase shortly after the coordinated 2023.2 release in October 2023.\"","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"28d3e1bc6e7b1120cba3f10c73ea9f74800775fd","unresolved":false,"context_lines":[{"line_number":51,"context_line":"proposed and merged to unmaintained branches, while improving communication"},{"line_number":52,"context_line":"around the responsibilities and defining clearer processes."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"The first branch this policy will apply to is stable/yoga. A sister resolution"},{"line_number":55,"context_line":"will be proposed concerning what to do with the current branches under"},{"line_number":56,"context_line":"extended maintenance."},{"line_number":57,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"b5fdd126_35abecd7","line":54,"range":{"start_line":54,"start_character":46,"end_line":54,"end_character":57},"in_reply_to":"16c84d62_aabeeff8","updated":"2023-08-09 11:00:12.000000000","message":"Ack","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"0b1a871c09114c94a618b181e8b48ea35675d0b4","unresolved":true,"context_lines":[{"line_number":68,"context_line":"  membership is separate from that group."},{"line_number":69,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":70,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":71,"context_line":"- Branches that correspond to a non-SLURP release are ineligible for having"},{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."}],"source_content_type":"text/x-rst","patch_set":2,"id":"2902c51b_e8b3d06a","line":71,"range":{"start_line":71,"start_character":32,"end_line":71,"end_character":49},"updated":"2023-07-24 14:50:57.000000000","message":"Might be useful to put a reference to https://governance.openstack.org/tc/resolutions/20220210-release-cadence-adjustment.html here","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"28d3e1bc6e7b1120cba3f10c73ea9f74800775fd","unresolved":false,"context_lines":[{"line_number":68,"context_line":"  membership is separate from that group."},{"line_number":69,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":70,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":71,"context_line":"- Branches that correspond to a non-SLURP release are ineligible for having"},{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."}],"source_content_type":"text/x-rst","patch_set":2,"id":"591cc8a4_43e0ed90","line":71,"range":{"start_line":71,"start_character":32,"end_line":71,"end_character":49},"in_reply_to":"2902c51b_e8b3d06a","updated":"2023-08-09 11:00:12.000000000","message":"Ack","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"6b216eecc55a67955c724b95ee205220ef8e2f4c","unresolved":true,"context_lines":[{"line_number":69,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":70,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":71,"context_line":"- Branches that correspond to a non-SLURP release are ineligible for having"},{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."}],"source_content_type":"text/x-rst","patch_set":2,"id":"0765c4bb_e848d187","line":72,"updated":"2023-07-24 16:47:04.000000000","message":"I feel like this statement (non-SLURPs are not eligible) is a bit of a double negative and harder to understand than just saying \"only SLURPs are eligible\". Not a big deal, but maybe easier to read.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"0b1a871c09114c94a618b181e8b48ea35675d0b4","unresolved":true,"context_lines":[{"line_number":69,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":70,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":71,"context_line":"- Branches that correspond to a non-SLURP release are ineligible for having"},{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."}],"source_content_type":"text/x-rst","patch_set":2,"id":"59c28d62_cda7fef9","line":72,"updated":"2023-07-24 14:50:57.000000000","message":"I\u0027m assuming that we\u0027re going to allow stable/yoga -\u003e unmaintained/yoga even though 2023.1 is the first SLURP release.  The justification would be that it\u0027s on the proper cadence and it also gives us an opportunity to work out any kinks in the proposed process and associated tooling.  In any case, we need to say something about that here.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bc7a1b28665f31563af0d94cff057814eef0553e","unresolved":true,"context_lines":[{"line_number":69,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":70,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":71,"context_line":"- Branches that correspond to a non-SLURP release are ineligible for having"},{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff0ee878_b93479f8","line":72,"in_reply_to":"0765c4bb_e848d187","updated":"2023-07-24 17:32:09.000000000","message":"yeah, let\u0027s just say SLURP eligibility with some reason why for example people can upgrade from SLURP to SLURP now.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"28d3e1bc6e7b1120cba3f10c73ea9f74800775fd","unresolved":false,"context_lines":[{"line_number":69,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":70,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":71,"context_line":"- Branches that correspond to a non-SLURP release are ineligible for having"},{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."}],"source_content_type":"text/x-rst","patch_set":2,"id":"807dfd50_d070c945","line":72,"in_reply_to":"59c28d62_cda7fef9","updated":"2023-08-09 11:00:12.000000000","message":"Ack","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"42bbdebf548a66d9ce9471e39763872985fdb221","unresolved":false,"context_lines":[{"line_number":69,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":70,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":71,"context_line":"- Branches that correspond to a non-SLURP release are ineligible for having"},{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."}],"source_content_type":"text/x-rst","patch_set":2,"id":"8dd8373b_64677b12","line":72,"in_reply_to":"ff0ee878_b93479f8","updated":"2023-07-24 19:36:51.000000000","message":"Done","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"6b216eecc55a67955c724b95ee205220ef8e2f4c","unresolved":true,"context_lines":[{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."}],"source_content_type":"text/x-rst","patch_set":2,"id":"a30296e8_beeab2b3","line":77,"updated":"2023-07-24 16:47:04.000000000","message":"Is the minimum really intentional here? Meaning, if a project wants to EOL their only unmaintained branch immediately, we won\u0027t allow it? I dunno that it\u0027s a big deal, I was just kinda surprised to see this. Obviously just leaving it (actually) unmaintained until it dies works, but that means it stays like that for a year instead of just communicating that it\u0027s already dead.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bc7a1b28665f31563af0d94cff057814eef0553e","unresolved":true,"context_lines":[{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."}],"source_content_type":"text/x-rst","patch_set":2,"id":"f863106a_456cc282","line":77,"range":{"start_line":77,"start_character":44,"end_line":77,"end_character":46},"updated":"2023-07-24 17:32:09.000000000","message":"for EOL policy I will still like the time-based term. Same as I mentioned in my previous comment, at least that give enough time for people to stay on unmaintained branches and upgrade to the newer one.\n\n4 years of that release can be a good amount of time (1.5 years in Maintained phase + 2.5 years in Unmaintained phase).\n\nThis way we will keep (counting from the time of latest 2023.1 release):\n\nMaintained:\n-----------\nmaster\nstable/2023.1 (\u003c 6 months of release)\nstable/zed (6 months of release)\nstable/yoga (12 months of release)\n\nUnmaintained:\n-------------\nunmaintained/xena (1.5 years of release)\nunmaintained/wallaby (2 years of release)\nunmaintained/victoria (2.5 years of release)\nunmaintained/ussuri (3 years of release)\nunmaintained/train (3.5 years of release)\nunmaintained/stein (4 years of release)\nunmaintained/rocky -\u003e EOL ( \u003e 4 years of release)\n\nor we can make it 3 years if that timeline seems good.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bc7a1b28665f31563af0d94cff057814eef0553e","unresolved":true,"context_lines":[{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."}],"source_content_type":"text/x-rst","patch_set":2,"id":"4f81a95f_ecd50427","line":77,"range":{"start_line":75,"start_character":0,"end_line":77,"end_character":46},"updated":"2023-07-24 17:32:09.000000000","message":"this looks strange to me too. We are not putting any work load on project team and keeping them unmainained for non-project team. I am not sure what we will achieve or solve by putting these max/min number of unmaintained branch policy?\n\nAll unmaintained branches are meant to be maintained by the people who need it and for the time they need and can maintain it. Stopping them to do so is contradict to to open branches for long term for maintainers need them. If we are going with this max/min policy (max 2 unmaintained branches) then we can just extend our \u0027Maintained\u0027 branches to one year more. And we do not need \u0027unmaintained\u0027 phase at all.\n\nWe should keep these unmaintained branches open for maintainers as long as we can and they can die naturally due to testing failing, no interest from anyone, deps broken, base ditro EOL etc.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"c452a27b38902ea40ec4985af55814c93adbd425","unresolved":true,"context_lines":[{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."}],"source_content_type":"text/x-rst","patch_set":2,"id":"2c998e91_1a2cd40a","line":77,"range":{"start_line":75,"start_character":0,"end_line":77,"end_character":46},"in_reply_to":"059721b0_0e8e1af1","updated":"2023-07-24 19:08:19.000000000","message":"ah, my bad I did not counted from SLUPR perspective. I agree on 2 SLURP maintained as automatic opt-in but let\u0027s not put it as max number of unmaintained as hard restriction .","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"c452a27b38902ea40ec4985af55814c93adbd425","unresolved":true,"context_lines":[{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."}],"source_content_type":"text/x-rst","patch_set":2,"id":"f9018b79_c8326165","line":77,"in_reply_to":"27369f88_e0ce8c63","updated":"2023-07-24 19:08:19.000000000","message":"maybe we can just say 2 unmaintained branches as automatic opt-in and more can be opt-in manually if there are maintainers and they request to keep more than 2 unmaintained branches open. This will give option to maintainers who need and want to maintain a few more unmaintained branches.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"7dcc66e2b9cb0eac0098b7eed31cd6d15c5f5575","unresolved":true,"context_lines":[{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."}],"source_content_type":"text/x-rst","patch_set":2,"id":"bf611380_d432f06f","line":77,"range":{"start_line":75,"start_character":0,"end_line":77,"end_character":46},"in_reply_to":"2c998e91_1a2cd40a","updated":"2023-07-24 19:15:01.000000000","message":"Just to make my comment clear. I think we should have at least 2 automatic opt-in and more can be opt-in but manually. only 1 automatic opt-in make 1.5 years of release and give really less benefit of this branches-open-to-maintain concept.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"714a0cd56125fd8886139a35767364d1fa987041","unresolved":true,"context_lines":[{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."}],"source_content_type":"text/x-rst","patch_set":2,"id":"059721b0_0e8e1af1","line":77,"range":{"start_line":75,"start_character":0,"end_line":77,"end_character":46},"in_reply_to":"3aa89909_3d35042a","updated":"2023-07-24 18:49:18.000000000","message":"Yeah I think maybe just re-word this to say the first one is automatic but without the words \"minimum 1\" and it should be clearer.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"28d3e1bc6e7b1120cba3f10c73ea9f74800775fd","unresolved":false,"context_lines":[{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."}],"source_content_type":"text/x-rst","patch_set":2,"id":"993a61e7_3b3c151b","line":77,"range":{"start_line":75,"start_character":0,"end_line":77,"end_character":46},"in_reply_to":"450c6c25_a0280cfc","updated":"2023-08-09 11:00:12.000000000","message":"Ack","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"27cf98d70e44e714a7348340a706c9a7859fe7e0","unresolved":true,"context_lines":[{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3aa89909_3d35042a","line":77,"range":{"start_line":75,"start_character":0,"end_line":77,"end_character":46},"in_reply_to":"4f81a95f_ecd50427","updated":"2023-07-24 18:42:34.000000000","message":"I put the number 2 because considering the once a year periodicity of SLURP releases, 2 SLURPs under unmaintained branches means 1.5-2 years after maintenance ends.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"27cf98d70e44e714a7348340a706c9a7859fe7e0","unresolved":true,"context_lines":[{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."}],"source_content_type":"text/x-rst","patch_set":2,"id":"27369f88_e0ce8c63","line":77,"in_reply_to":"a30296e8_beeab2b3","updated":"2023-07-24 18:42:34.000000000","message":"When we discussed during the previous meeting, we seemed to reach consensus on an automatic initial opt-in, with a X cycles grace period for finding people to keep it running. I understand now that my poor phrasing may mean we disallow teams from opting out and will revise.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"42bbdebf548a66d9ce9471e39763872985fdb221","unresolved":true,"context_lines":[{"line_number":72,"context_line":"  an Unmaintained branch."},{"line_number":73,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."}],"source_content_type":"text/x-rst","patch_set":2,"id":"450c6c25_a0280cfc","line":77,"range":{"start_line":75,"start_character":0,"end_line":77,"end_character":46},"in_reply_to":"bf611380_d432f06f","updated":"2023-07-24 19:36:51.000000000","message":"I kept 1 as automatic, but I removed the maximum. Does that seem reasonable?","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"28d3e1bc6e7b1120cba3f10c73ea9f74800775fd","unresolved":false,"context_lines":[{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."}],"source_content_type":"text/x-rst","patch_set":2,"id":"c8b2cd23_38d10b7d","line":77,"range":{"start_line":77,"start_character":44,"end_line":77,"end_character":46},"in_reply_to":"f863106a_456cc282","updated":"2023-08-09 11:00:12.000000000","message":"Ack","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"28d3e1bc6e7b1120cba3f10c73ea9f74800775fd","unresolved":false,"context_lines":[{"line_number":74,"context_line":"  and the current maintained releases."},{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3075d9a8_360bf4c4","line":77,"in_reply_to":"f9018b79_c8326165","updated":"2023-08-09 11:00:12.000000000","message":"Ack","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bc7a1b28665f31563af0d94cff057814eef0553e","unresolved":true,"context_lines":[{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."},{"line_number":81,"context_line":"- The TC will maintain and document the full steps and guidelines for"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3bcc3be4_10ea596d","line":78,"range":{"start_line":78,"start_character":35,"end_line":78,"end_character":53},"updated":"2023-07-24 17:32:09.000000000","message":"I think we need to mention here what is criteria of being CI a good standing. We can mention you need to have all the integrated job as best-effort and at least one tempest job as must (if you cannot do for any reason then inform TC and we will discuss if we can allow to remove all tempest jobs). unit/functional/pep8 job are mandatory to pass.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"27cf98d70e44e714a7348340a706c9a7859fe7e0","unresolved":true,"context_lines":[{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."},{"line_number":81,"context_line":"- The TC will maintain and document the full steps and guidelines for"}],"source_content_type":"text/x-rst","patch_set":2,"id":"4f920fa1_873d0069","line":78,"range":{"start_line":78,"start_character":35,"end_line":78,"end_character":53},"in_reply_to":"3bcc3be4_10ea596d","updated":"2023-07-24 18:42:34.000000000","message":"I will add a note about integrated job at a minimum. I\u0027m on the fence regarding mandating a tempest job.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"28d3e1bc6e7b1120cba3f10c73ea9f74800775fd","unresolved":false,"context_lines":[{"line_number":75,"context_line":"- There can be a minimum of 1 Unmaintained branch and a maximum of 2."},{"line_number":76,"context_line":"  This corresponds to approximately 3 years since release. A project must"},{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."},{"line_number":81,"context_line":"- The TC will maintain and document the full steps and guidelines for"}],"source_content_type":"text/x-rst","patch_set":2,"id":"c14e6969_99c15f0a","line":78,"range":{"start_line":78,"start_character":35,"end_line":78,"end_character":53},"in_reply_to":"4f920fa1_873d0069","updated":"2023-08-09 11:00:12.000000000","message":"Ack","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bc7a1b28665f31563af0d94cff057814eef0553e","unresolved":true,"context_lines":[{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."},{"line_number":81,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":82,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":83,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":2,"id":"f0101c1a_5df3f091","line":80,"range":{"start_line":80,"start_character":41,"end_line":80,"end_character":74},"updated":"2023-07-24 17:32:09.000000000","message":"+1, good ideas. this helps and not much load on CI infra too.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"08641ea010333183303419624de63154fe10302f","unresolved":true,"context_lines":[{"line_number":77,"context_line":"  opt-in to keep a second Unmaintained branch."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the end of each cycle."},{"line_number":79,"context_line":"  However this is a best-effort CI and to preserve resources for Unmaintained"},{"line_number":80,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."},{"line_number":81,"context_line":"- The TC will maintain and document the full steps and guidelines for"},{"line_number":82,"context_line":"  transitioning from maintained to unmaintained, and for the eventual branch"},{"line_number":83,"context_line":"  deletion."}],"source_content_type":"text/x-rst","patch_set":2,"id":"043be5c2_288db9a0","line":80,"range":{"start_line":80,"start_character":41,"end_line":80,"end_character":74},"in_reply_to":"f0101c1a_5df3f091","updated":"2023-07-28 10:05:15.000000000","message":"It\u0027s not related to that document directly but maybe infra team will have some possibility to define monthly jobs to be run not all in the same time. So the load caused by them can be spread across different days.","commit_id":"f0b189771326db8866c81a5b83728d7db1c160d5"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b045392e0ebf263def9a714dc4f8b8c00a1988ce","unresolved":true,"context_lines":[{"line_number":51,"context_line":"proposed and merged to unmaintained branches, while improving communication"},{"line_number":52,"context_line":"around the responsibilities and defining clearer processes."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"The first branch this policy will apply to is stable/yoga. A sister resolution"},{"line_number":55,"context_line":"will be proposed concerning what to do with the current branches under"},{"line_number":56,"context_line":"extended maintenance."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"Unmaintained branches"},{"line_number":59,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"b636ef47_c1d4de5d","line":56,"range":{"start_line":54,"start_character":0,"end_line":56,"end_character":21},"updated":"2023-07-24 20:14:27.000000000","message":"This one still valid ?\n\nAs stable/yoga is still a 6 month upgradable we need to keep it explicit that policy for SLURP releases (which is 2023.1 onwards) and for before-SLURP-concept releases","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"28d3e1bc6e7b1120cba3f10c73ea9f74800775fd","unresolved":false,"context_lines":[{"line_number":51,"context_line":"proposed and merged to unmaintained branches, while improving communication"},{"line_number":52,"context_line":"around the responsibilities and defining clearer processes."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"The first branch this policy will apply to is stable/yoga. A sister resolution"},{"line_number":55,"context_line":"will be proposed concerning what to do with the current branches under"},{"line_number":56,"context_line":"extended maintenance."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"Unmaintained branches"},{"line_number":59,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1d3ad27e_6ee1923f","line":56,"range":{"start_line":54,"start_character":0,"end_line":56,"end_character":21},"in_reply_to":"b636ef47_c1d4de5d","updated":"2023-08-09 11:00:12.000000000","message":"Ack","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b045392e0ebf263def9a714dc4f8b8c00a1988ce","unresolved":true,"context_lines":[{"line_number":59,"context_line":"---------------------"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":62,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":63,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":64,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":65,"context_line":"  unmaintained/train."}],"source_content_type":"text/x-rst","patch_set":3,"id":"b533632f_ff01eaed","line":62,"range":{"start_line":62,"start_character":68,"end_line":62,"end_character":69},"updated":"2023-07-24 20:14:27.000000000","message":"+1.\n\nAlso, as our SLURP releases start from 2023.1 only and all our existing EM and future one till 2023.1 are 6 month upgradable only, we need to make policy for those 6 month upgradable branches also. \n\nWe should add something like below:\n\n\"For the releases before SLURP concept, we can keep them eligible for Unmaintained branch policy.\"","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"bd5bfee6a65b22adde4ed2bb208d79db44d3c8b1","unresolved":true,"context_lines":[{"line_number":59,"context_line":"---------------------"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":62,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":63,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":64,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":65,"context_line":"  unmaintained/train."}],"source_content_type":"text/x-rst","patch_set":3,"id":"f0205c6a_bbfac1b6","line":62,"range":{"start_line":62,"start_character":68,"end_line":62,"end_character":69},"in_reply_to":"1f24921e_b9057b1f","updated":"2023-07-25 18:10:14.000000000","message":"+1 to Sean.\n\nI would add Yoga to the list of Unmainained, simply because then this policy will be applicable only in over a year. And until then we would drop EMs without replacement for upstream packagers.","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"63e05831af139cdaec38081fef13ec60451479e4","unresolved":true,"context_lines":[{"line_number":59,"context_line":"---------------------"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":62,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":63,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":64,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":65,"context_line":"  unmaintained/train."}],"source_content_type":"text/x-rst","patch_set":3,"id":"6943da92_4d69aa2b","line":62,"range":{"start_line":62,"start_character":68,"end_line":62,"end_character":69},"in_reply_to":"1f24921e_b9057b1f","updated":"2023-07-26 09:24:58.000000000","message":"ok but htat means yoga and zed will go eol once they hit 18months after there release  since they are not slurp release correct so they are not eligbale for unmaintianed status under this new policy and we shoudl not contiue to have EM branches beyond the ones that already exist.","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"40853868fa10b03943efdcbe30de89cc2dd9f625","unresolved":false,"context_lines":[{"line_number":59,"context_line":"---------------------"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":62,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":63,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":64,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":65,"context_line":"  unmaintained/train."}],"source_content_type":"text/x-rst","patch_set":3,"id":"c3d21cd1_a54f82e3","line":62,"range":{"start_line":62,"start_character":68,"end_line":62,"end_character":69},"in_reply_to":"6943da92_4d69aa2b","updated":"2023-08-09 07:01:41.000000000","message":"There is \"Transition\" section at the end of the document that describes this.\n\n```\n- Until the first SLURP release ends its maintained phase, all current branches\nare eligible for Unmaintained.\n```\n\nSo both Y and Z should get \"Unmaintained\" according to that.","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"030c612707420b630173b3b77005c022cbb41803","unresolved":true,"context_lines":[{"line_number":59,"context_line":"---------------------"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":62,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":63,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":64,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":65,"context_line":"  unmaintained/train."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1f24921e_b9057b1f","line":62,"range":{"start_line":62,"start_character":68,"end_line":62,"end_character":69},"in_reply_to":"76cb59e5_2c2e09e6","updated":"2023-07-25 16:15:08.000000000","message":"I disagree with this comment; yoga was a beta test of the SLURP process; we should not be setting up a path where users may be using a less-tested path for upgrades. IMO starting at the first real slurp release, A, is best.","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"3dba644dd933a48a3d0965c80a5e697e9b239d14","unresolved":true,"context_lines":[{"line_number":59,"context_line":"---------------------"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":62,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":63,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":64,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":65,"context_line":"  unmaintained/train."}],"source_content_type":"text/x-rst","patch_set":3,"id":"76cb59e5_2c2e09e6","line":62,"range":{"start_line":62,"start_character":68,"end_line":62,"end_character":69},"in_reply_to":"b533632f_ff01eaed","updated":"2023-07-25 08:23:44.000000000","message":"we have treated yoga as a pseudo SLURP release for the purpous fo workign out the mecanics of SLURP release.\n\nwe perhaps should consider it in this context too.\nwhen it exits stable maintance at teh end of the cycle i woudl treat it as the first SLURP release. when zed exits stable matiance we can consider eoling it immediately as a non slurp if we belive sufficent upgrade support exist form yoga to antelope. \n\ni would also consider EOLing anythong loder then victoria based on the supproted lifecycle of 18.04 and the fact that was the ubuntu used on prior releases.","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b045392e0ebf263def9a714dc4f8b8c00a1988ce","unresolved":true,"context_lines":[{"line_number":73,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":74,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."},{"line_number":75,"context_line":"- By default, only the latest eligible Unmaintained branch is kept. When a new"},{"line_number":76,"context_line":"  branch is eligible, the Unmaintained branch liaison must opt-in to keep all"},{"line_number":77,"context_line":"  previous branches active."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the time of opt-in."},{"line_number":79,"context_line":"  At a minimum this needs to contain all integrated jobs (unit tests, pep8,"},{"line_number":80,"context_line":"  and functional.)"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3de2b99c_f6fb3847","line":77,"range":{"start_line":76,"start_character":22,"end_line":77,"end_character":27},"updated":"2023-07-24 20:14:27.000000000","message":"++, I like two unmaintained as automatic opt-in but as there is option to opt-in by maintainers I am fine to have 1 as default opt-in.","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b045392e0ebf263def9a714dc4f8b8c00a1988ce","unresolved":true,"context_lines":[{"line_number":74,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."},{"line_number":75,"context_line":"- By default, only the latest eligible Unmaintained branch is kept. When a new"},{"line_number":76,"context_line":"  branch is eligible, the Unmaintained branch liaison must opt-in to keep all"},{"line_number":77,"context_line":"  previous branches active."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the time of opt-in."},{"line_number":79,"context_line":"  At a minimum this needs to contain all integrated jobs (unit tests, pep8,"},{"line_number":80,"context_line":"  and functional.)"}],"source_content_type":"text/x-rst","patch_set":3,"id":"05f2bd26_cb382d41","line":77,"range":{"start_line":77,"start_character":26,"end_line":77,"end_character":27},"updated":"2023-07-24 20:14:27.000000000","message":"As SLURP releases start from 2023.1, we need to add policy for existing releases before 2023.1 which are 6 month upgradable only. maybe we can keep them as per current time-based transition I mentioned before. Maybe time-based of 3 years which will be victoria as last Unmaintained branch. Something like:\n\n- All releases before the SLURP release concept (\u003c 2023.1), will be in Unmaintained releases for their 2.5 years of release. After 2.5 years of releases, Unmaintained branch liasion must opt-in to keep all previous branches active.","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"3dba644dd933a48a3d0965c80a5e697e9b239d14","unresolved":true,"context_lines":[{"line_number":74,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."},{"line_number":75,"context_line":"- By default, only the latest eligible Unmaintained branch is kept. When a new"},{"line_number":76,"context_line":"  branch is eligible, the Unmaintained branch liaison must opt-in to keep all"},{"line_number":77,"context_line":"  previous branches active."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the time of opt-in."},{"line_number":79,"context_line":"  At a minimum this needs to contain all integrated jobs (unit tests, pep8,"},{"line_number":80,"context_line":"  and functional.)"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ba06eaca_3d369b10","line":77,"range":{"start_line":77,"start_character":26,"end_line":77,"end_character":27},"in_reply_to":"05f2bd26_cb382d41","updated":"2023-07-25 08:23:44.000000000","message":"2.5 years would mean walaby later will be unmaintained unless im off by one which would make it vicotria.\nmeaning the oldest ubuntu we require for ci images is 20.04 which i think makes sense form a \"is this distro still supproted\" point of view and it also mean python 3.8 which is simialr supproted.\n\npython 3.6 and centos 8 was techniall a test runtim for both however centos 8 was eol 31 Dec 2021 and python 3.6 is also eol 23 Dec 2021\n\nso in terms of tox job we can test with just py38 as our minium python version.","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"08641ea010333183303419624de63154fe10302f","unresolved":true,"context_lines":[{"line_number":73,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":74,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."},{"line_number":75,"context_line":"- By default, only the latest eligible Unmaintained branch is kept. When a new"},{"line_number":76,"context_line":"  branch is eligible, the Unmaintained branch liaison must opt-in to keep all"},{"line_number":77,"context_line":"  previous branches active."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the time of opt-in."},{"line_number":79,"context_line":"  At a minimum this needs to contain all integrated jobs (unit tests, pep8,"},{"line_number":80,"context_line":"  and functional.)"}],"source_content_type":"text/x-rst","patch_set":3,"id":"103acaa3_646e0e23","line":77,"range":{"start_line":76,"start_character":22,"end_line":77,"end_character":27},"in_reply_to":"384cde40_e5397e51","updated":"2023-07-28 10:05:15.000000000","message":"+1 for one automatic cycle of unmaintained","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"055c78577778b3afabf614567d11914f8ff73673","unresolved":true,"context_lines":[{"line_number":73,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":74,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."},{"line_number":75,"context_line":"- By default, only the latest eligible Unmaintained branch is kept. When a new"},{"line_number":76,"context_line":"  branch is eligible, the Unmaintained branch liaison must opt-in to keep all"},{"line_number":77,"context_line":"  previous branches active."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the time of opt-in."},{"line_number":79,"context_line":"  At a minimum this needs to contain all integrated jobs (unit tests, pep8,"},{"line_number":80,"context_line":"  and functional.)"}],"source_content_type":"text/x-rst","patch_set":3,"id":"384cde40_e5397e51","line":77,"range":{"start_line":76,"start_character":22,"end_line":77,"end_character":27},"in_reply_to":"3de2b99c_f6fb3847","updated":"2023-07-25 17:28:05.000000000","message":"I prefer one automatic cycle of unmaintained, and require renewal after that.","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b045392e0ebf263def9a714dc4f8b8c00a1988ce","unresolved":true,"context_lines":[{"line_number":76,"context_line":"  branch is eligible, the Unmaintained branch liaison must opt-in to keep all"},{"line_number":77,"context_line":"  previous branches active."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the time of opt-in."},{"line_number":79,"context_line":"  At a minimum this needs to contain all integrated jobs (unit tests, pep8,"},{"line_number":80,"context_line":"  and functional.)"},{"line_number":81,"context_line":"  However, as this is a best-effort CI and to preserve resources, Unmaintained"},{"line_number":82,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."},{"line_number":83,"context_line":"- The TC will maintain and document the full steps and guidelines for"}],"source_content_type":"text/x-rst","patch_set":3,"id":"4b3b4ab9_85335892","line":80,"range":{"start_line":79,"start_character":41,"end_line":80,"end_character":18},"updated":"2023-07-24 20:14:27.000000000","message":"This may confuse integrated jobs with unit/pep8, how about writing this like\n\n.. contain all integrated jobs, unit tests, pep8, and functional testing.","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"67de861637379474c98280d767f0fd69c171c1b7","unresolved":false,"context_lines":[{"line_number":76,"context_line":"  branch is eligible, the Unmaintained branch liaison must opt-in to keep all"},{"line_number":77,"context_line":"  previous branches active."},{"line_number":78,"context_line":"- The CI for all branches must be in good standing at the time of opt-in."},{"line_number":79,"context_line":"  At a minimum this needs to contain all integrated jobs (unit tests, pep8,"},{"line_number":80,"context_line":"  and functional.)"},{"line_number":81,"context_line":"  However, as this is a best-effort CI and to preserve resources, Unmaintained"},{"line_number":82,"context_line":"  branches will include periodic jobs of no higher than monthly frequency."},{"line_number":83,"context_line":"- The TC will maintain and document the full steps and guidelines for"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f5886bf_2764a9aa","line":80,"range":{"start_line":79,"start_character":41,"end_line":80,"end_character":18},"in_reply_to":"4b3b4ab9_85335892","updated":"2023-07-24 20:56:19.000000000","message":"Done","commit_id":"af0b0f77fc4b434b2d2702bf170cf5c30b1d5b39"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"541cb95447a7e0d04d28fb7910c315e0cc1cf960","unresolved":true,"context_lines":[{"line_number":91,"context_line":"  are eligible for Unmaintained."},{"line_number":92,"context_line":"- The last 3 active Extended Maintenance branches are automatically"},{"line_number":93,"context_line":"  transitioned to Unmaintained branches."},{"line_number":94,"context_line":"- Projects need to opt-in to keep more than 3 branches (instead of 1 for SLURP)"},{"line_number":95,"context_line":"  and the guidelines for opt-in described above apply."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3ff7bad5_9f4f76e6","line":94,"range":{"start_line":94,"start_character":2,"end_line":94,"end_character":11},"updated":"2023-07-24 21:08:25.000000000","message":"let\u0027s use  \u0027Unmaintained branch liaison\u0027 here too to avoid confusion if project teams means project core team.","commit_id":"58d525e1ba1f80537ea73a2623449ad2a4554d2d"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"0c7bb91b7f8c35c3b96288d4fb083813631f16a8","unresolved":false,"context_lines":[{"line_number":91,"context_line":"  are eligible for Unmaintained."},{"line_number":92,"context_line":"- The last 3 active Extended Maintenance branches are automatically"},{"line_number":93,"context_line":"  transitioned to Unmaintained branches."},{"line_number":94,"context_line":"- Projects need to opt-in to keep more than 3 branches (instead of 1 for SLURP)"},{"line_number":95,"context_line":"  and the guidelines for opt-in described above apply."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"[0]. https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html"}],"source_content_type":"text/x-rst","patch_set":5,"id":"e380eaee_0c59adaf","line":94,"range":{"start_line":94,"start_character":2,"end_line":94,"end_character":11},"in_reply_to":"3ff7bad5_9f4f76e6","updated":"2023-07-24 21:12:20.000000000","message":"Done","commit_id":"58d525e1ba1f80537ea73a2623449ad2a4554d2d"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5988a0f45fb21f45fe8f798dff0c1b5b62d76f43","unresolved":true,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":58,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":59,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"}],"source_content_type":"text/x-rst","patch_set":6,"id":"2fb633cf_b3791ee8","line":61,"range":{"start_line":59,"start_character":0,"end_line":61,"end_character":21},"updated":"2023-07-25 14:49:28.000000000","message":"I want to be clear on this.\n1. The branch will be tagged before deletion, are we following current practice and tagging it -eol?\n2. Is the unmaintained/ branch creation automatic, or opt-in?  (I suppose I\u0027m OK with automatic, since we\u0027ll only be keeping 1 of these by default, so if it goes unused, it will only be there for 1 year.)","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"08641ea010333183303419624de63154fe10302f","unresolved":true,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":58,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":59,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"}],"source_content_type":"text/x-rst","patch_set":6,"id":"d73cdfa2_69036122","line":61,"range":{"start_line":59,"start_character":0,"end_line":61,"end_character":21},"in_reply_to":"2076d167_3035326e","updated":"2023-07-28 10:05:15.000000000","message":"We could also just release new version of each project just before moving it to unmaintained and say in docs, that last released version of this project is when maintenance was over. That way we will have always released last maintained version in e.g. pypi.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"68f5961bfe5df5cf63541295ad84b9cef999e360","unresolved":true,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":58,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":59,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"}],"source_content_type":"text/x-rst","patch_set":6,"id":"560bf384_6773194f","line":61,"range":{"start_line":59,"start_character":0,"end_line":61,"end_character":21},"in_reply_to":"2fb633cf_b3791ee8","updated":"2023-07-25 15:33:07.000000000","message":"for the 1st question: i think we should not use *-eol, rather *-eom \u003d End of Maintenance or something like that.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"8cc8c48f1b0e0cff02f6c282aa14bb571d46c121","unresolved":true,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":58,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":59,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"}],"source_content_type":"text/x-rst","patch_set":6,"id":"55058bfa_813c1902","line":61,"range":{"start_line":59,"start_character":0,"end_line":61,"end_character":21},"in_reply_to":"3386bb99_3734447c","updated":"2023-07-25 18:07:36.000000000","message":"So every branch will have two tags eventually? eol and eom? AFAIK, we don\u0027t do that today, we just have EOL. I think having the word \"unmaintained\" in the branch name is a plenty strong signal that it is indeed unmaintained.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"43ef8cd09bd71e5cbb5b4c7f27282a74829a6833","unresolved":true,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":58,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":59,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"}],"source_content_type":"text/x-rst","patch_set":6,"id":"ca85f9d5_759606da","line":61,"range":{"start_line":59,"start_character":0,"end_line":61,"end_character":21},"in_reply_to":"55058bfa_813c1902","updated":"2023-07-25 18:16:10.000000000","message":"Yes we do.\n\nAIUI:\n\nstable/X for 18 months\nX-em is tagged\nstable/X in EM for (however long)\nX-eol is tagged, branch deleted","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5ef2970c11429ffb78b357e788d6fbc73dfa5acb","unresolved":true,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":58,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":59,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"}],"source_content_type":"text/x-rst","patch_set":6,"id":"82ad73e6_0d23ddfc","line":61,"range":{"start_line":59,"start_character":0,"end_line":61,"end_character":21},"in_reply_to":"560bf384_6773194f","updated":"2023-07-25 17:24:16.000000000","message":"@Elod: that\u0027s an indirect argument for making \u0027unmaintained\u0027 automatic.  What I mean is:\n\n- stable/n is tagged n-eom and deleted\n- unmaintained/n is created from n-eom\n- one year later, when unmaintained/n+1 is created; unmaintained/n is tagged n-eol and deleted\n\nOtherwise, if unmaintained/n is never created, n-eol won\u0027t be created either.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"055c78577778b3afabf614567d11914f8ff73673","unresolved":true,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":58,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":59,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"}],"source_content_type":"text/x-rst","patch_set":6,"id":"70943b86_232ceb56","line":61,"range":{"start_line":59,"start_character":0,"end_line":61,"end_character":21},"in_reply_to":"560bf384_6773194f","updated":"2023-07-25 17:28:05.000000000","message":"The way I read this and what I thought we discussed is that we don\u0027t tag until we\u0027re deleting the final branch. So, for a SLURP, we delete stable/foo and create unmaintained/foo in its place. Then when we delete unmaintained/foo, we tag as foo-eol. For non-SLURP we go straight from stable/bar to a bar-eol tag.\n\nBrian is that what you\u0027re thinking?\n\nElod, I don\u0027t think we need a tag for the unmaintained phase if we have a branch, and I definitely don\u0027t want to rename EOL to EOM for the phase after the final branch has been deleted as I think EOL is a stronger name.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"bd25cba7bf84b088eb70b59ceb9840256a2e4f04","unresolved":true,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":58,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":59,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3386bb99_3734447c","line":61,"range":{"start_line":59,"start_character":0,"end_line":61,"end_character":21},"in_reply_to":"70943b86_232ceb56","updated":"2023-07-25 18:06:00.000000000","message":"If we stop providing a tag that says \"official maintenance is over\", we\u0027ll be sending the inadvertent message that unmaintained/ branches are kinda-maintained.\n\nI would still want a tag indicating \"this is when we disavowed maintenance of this\", or else we\u0027re just going to be putting the onus back on project teams to feel responsible for code they shouldn\u0027t be responsible for anymore.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"63e05831af139cdaec38081fef13ec60451479e4","unresolved":true,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":58,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":59,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"}],"source_content_type":"text/x-rst","patch_set":6,"id":"2076d167_3035326e","line":61,"range":{"start_line":59,"start_character":0,"end_line":61,"end_character":21},"in_reply_to":"80268e88_27d20a04","updated":"2023-07-26 09:24:58.000000000","message":"maybe to be explcit stable-eol or EOM (end of maintaince) rahter tagging as EM would be better with this new propoasl","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"e85bf4c83a951b983c61d466519254f94d0c21dd","unresolved":true,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":58,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":59,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"}],"source_content_type":"text/x-rst","patch_set":6,"id":"80268e88_27d20a04","line":61,"range":{"start_line":59,"start_character":0,"end_line":61,"end_character":21},"in_reply_to":"ca85f9d5_759606da","updated":"2023-07-25 18:18:34.000000000","message":"Ack, I see them now, I guess I\u0027ve always lumped those together being so similarly named and haven\u0027t noticed. Fair enough.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"40853868fa10b03943efdcbe30de89cc2dd9f625","unresolved":true,"context_lines":[{"line_number":56,"context_line":""},{"line_number":57,"context_line":"- The phase of Extended Maintenance for a branch is renamed to Unmaintained."},{"line_number":58,"context_line":"- Only SLURP releases are eligible for having an Unmaintained branch."},{"line_number":59,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9a2655f3_2231ddfa","line":61,"range":{"start_line":59,"start_character":0,"end_line":61,"end_character":21},"in_reply_to":"d73cdfa2_69036122","updated":"2023-08-09 07:01:41.000000000","message":"Well, for tagging EM we had to make last \"normal\" version according to the process. So we have 27.x.x and train-em tracking the same SHA. So I assume we\u0027ll do the same for stable-eom tag?","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"bd5bfee6a65b22adde4ed2bb208d79db44d3c8b1","unresolved":true,"context_lines":[{"line_number":59,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9b9b59df_fe0656a0","line":63,"range":{"start_line":62,"start_character":2,"end_line":63,"end_character":66},"updated":"2023-07-25 18:10:14.000000000","message":"Also in case branch creation is automated, should we also automatically create a group? As I  would estimate only small amount of projects would benefit from that.\nSo not creating it as default behaviour (or create from same as stable-maint) might be fair comparing to make all projects with just couple maintainers to fill in this group.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"40853868fa10b03943efdcbe30de89cc2dd9f625","unresolved":false,"context_lines":[{"line_number":59,"context_line":"- After a branch is no longer officially maintained, the branch is deleted and"},{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"}],"source_content_type":"text/x-rst","patch_set":6,"id":"f168f7fe_b4818f43","line":63,"range":{"start_line":62,"start_character":2,"end_line":63,"end_character":66},"in_reply_to":"9b9b59df_fe0656a0","updated":"2023-08-09 07:01:41.000000000","message":"Done","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"3cf057f3e8643a61d5e63de7322066393544a9fd","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"135d9899_378e0d92","line":67,"updated":"2023-07-25 18:40:38.000000000","message":"I think this bulletpoint negates most of the rest of the proposal -- one of the key items identified at the forum was that project teams feel responsible for these EM/UM branches even if they don\u0027t want to be.\n\nForcing the PTL to choose if someone should get core access on the unmaintained/ branches continues to rest the responsibility for these branches on the shoulders of the project team.\n\nWe should come up with a way to curate the core group without needing the project team involved. My suggestion:\n- A single core group is created, unmaintained-cores, which could have merge access on *all* unmaintained branches\n- The TC or a designate curates the unmaintained-cores group, with a very low bar for approval mainly based around trust-to-not-perform-malicious-things.\n\n\nUntil this concern is resolved, I\u0027m afraid we\u0027re just recreating another version of this same issue.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"08641ea010333183303419624de63154fe10302f","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"96ab015c_7cb81c22","line":67,"in_reply_to":"06ddd087_3aa3b007","updated":"2023-07-28 10:05:15.000000000","message":"@Sean: I don\u0027t think adding whole \u003cproject\u003e-stable-core group as a member of the \u003cproject\u003e-unmaintained-core group is good idea. It will make that stable project team will feel even more responsible for that unmaintained branches.\nIMO PTL role here should be \"just\" to find unmaintained liaison and let that person to do other things related to the unmaintained branches. If there is nobody who wants to be such liaison in the project, then there are 2 options: PTL can do it on it\u0027s own if wants to or maybe it means that there is no community interest in having branches of that project to be open for longer period then 18 months and such project don\u0027t need to leave unmaintained branches open.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"7ee3b8bb1f5281976cd783842d174872a64aa4ac","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"45985b42_c6b1a119","line":67,"in_reply_to":"135d9899_378e0d92","updated":"2023-07-25 19:05:09.000000000","message":"well I see this as a admin taks by PTL to just create/add interested people there. This does not make PTL responsible for maintaining the unmaintained branches. PTL have such many tasks to do for master and stable branches for example \u0027tracking of feature implementation\u0027 which does not mean PTL is responsible to complete those features on time, it is just tracking.\n\nIMO, this is another small task for PTL which hardly will take 5 min per 6 months to just check/track maintainers on unmaintained brnahces. It can be done in every PTG with small amount of time.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"4c8747b7a8107fb0a5990d9039c13449224feeb8","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"2f4f26a9_06ac91ba","line":67,"in_reply_to":"13d0bc62_0f198700","updated":"2023-07-25 22:21:54.000000000","message":"Want to make clear there is no language here that prohibits a ptl/unmaintained liaison from dropping a branch earlier if there is no interest in it, or for whatever reason they take that decision.\n\nI also believe a global unmaintained-core group is a great idea in further lowering the burden on a ptl if there is time on their part to vet people and there are known good backporters/reviewers that the community vets and trusts.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"33a70f032d6d190f9a8db846ee8cad672cea8c21","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"5a21c116_1df1871e","line":67,"in_reply_to":"2f4f26a9_06ac91ba","updated":"2023-07-26 00:57:14.000000000","message":"\u003e So I spoke with Kristi some about this concern, discovered this should be possible:\n\nI did not find the discussion of that but it is good if you discussed it with him and got clarification. but that is what the expectation is here and I am trying to say since starting :). \n\nThere is no restriction/mention of \"unmaintained branches has to stay live for xyz time\". If PTL does not find any liaison, no maintainers, CI does not work for any reason, then the automatic opt-in branches can be moved to EOL immediatly.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"080a28321f8353bcd0a1c41ff59fdfa9516d2244","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"505f80ae_b4928d41","line":67,"in_reply_to":"45985b42_c6b1a119","updated":"2023-07-25 20:48:55.000000000","message":"I can\u0027t speak for other PTLs; I can only speak for me with my Ironic PTL hat on: This is exactly the kind of stuff that pulled in project team members to EM. If I, with my PTL hat on, have to add people to a core group, I *cannot* in good conscience do this without some kind of evaluation of merit or at least vetting against dangerous/malicious actors.\n\nWhat if, as PTL, I don\u0027t think we should add operators to a core group? If I\u0027d rather those branches go truly unmaintained instead of getting people added to the core group who wouldn\u0027t be eligible to be in the \"supported\" branches core team. \n\nThis is the crux of the problem. If we want a phase of lifecycle that the project team isn\u0027t responsible for; they need to actually not be responsible for it. That doesn\u0027t mean \"oh, you\u0027re only a little responsible\", or \"oh, this won\u0027t take much time\" -- it means I want to be truly divorced from these branches, because otherwise their quality *will* be a direct reflection on me (as PTL) and the project team. \n\nIf the point is to create a second base of power to create a lower bar for older branches; lets do that -- but leaving the PTL in the loop does not achieve that goal and would still leave the \"Cinder problem\" -- where a project team/PTL could decide a branch should die and have all the power needed to kill it... this is exactly what happened with Cinder: cores became uncomfortable with the idea of people running their unpatched code and (attempted to) use the power delegated to them by the TC to kill those branches. There\u0027s nothing in this proposal that prevents that from happening again as long as the power base -- the Project Team Lead for that project -- remains the same.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"e2567bf5aa23846ae486047ccf577a4175872f12","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"60f49e10_b60f5462","line":67,"in_reply_to":"505f80ae_b4928d41","updated":"2023-07-25 21:04:39.000000000","message":"with all those points, how TC is more appropriate and closer than PTL to know who is best person to add in unmaintained branches of project? PTL is the best person to know who better know about their project code base compare to the TC.\n\nIMO, PTL should take this just as a admin task to manage the initial group/branches instead of doing the trust checks. If any dangerous activity happens, we can handle that in the same way if that happens in any of the stable or master branches.\n\nAny Operator/vendor/users using/seeing those unmaintained branches know that upstream team is not responsible for any dangerous/malicious activity in those because those are *Not maintained by upstream project team*. If anything goes wrong we can always call out them to EOL.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"63e05831af139cdaec38081fef13ec60451479e4","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"06ddd087_3aa3b007","line":67,"in_reply_to":"5a21c116_1df1871e","updated":"2023-07-26 09:24:58.000000000","message":"so its convention that hte PTL adds someone to the core team but anyone in the core group can actully do that.\n\ni was expectign that to be the job of the unmainted-core laison not the PTL.\nby defualt if there is not liaon it can default to the ptl i agree that the PTL should not be expected to manage this in general.\n\nhow i saw the membership of the \u003cproject\u003e-unmaintained-core group being managed is as follows:\n\nintially bootstrap it by adding \u003cproject\u003e-stable-core as a member\nand ossibel the gloal unmaintained-core if that is created.\nwhen adding someone to the \u003cproject\u003e-unmaintained-core how is not form the exisitng stable-core grop ask them if they would be willing to be the unmaintained branch liason which would include managing memebrship of the \u003cproject\u003e-unmaintained-core group going forward.\n\nthat could eventrully invole removing the \u003cproject\u003e-stable-core from \u003cproject\u003e-unmaintained-core. if a stabel core want to be an unmaintianed core after that point they cna be added directly but we will have fully delgated maintaice of the unmaintained branches form the project team at that point.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"19018fd5e700358edc475505c49dda839c9a88b5","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"a08cffb0_bde63d82","line":67,"in_reply_to":"60f49e10_b60f5462","updated":"2023-07-25 21:07:50.000000000","message":"\u003e how TC is more appropriate and closer than PTL to know who is best person to add in unmaintained branches of project\n\nI\u0027m working under the assumption that these unmaintained branches would likely be handled by a completely separate community than the existing one. That means that perhaps a meta-openstack view, instead of a project-centric one, allows a better perspective; especially since the bar would be a lot lower than it is for a core on a supported branch.\n\n\nIn any event; this argument still dodges the primary concern: having the PTL involved means the project team is responsible, and that\u0027s the key piece I was hoping this proposal would resolve.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"20032925f98a3b6e636848a46b00f196f844d74e","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"21770966_22c13a9d","line":67,"in_reply_to":"60f49e10_b60f5462","updated":"2023-07-25 21:06:07.000000000","message":"s/doing the trust checks./doing and responsible for the trust checks.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"d4741ead4680635eeb4c639527967c0d74080102","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"eac7f648_0d1d62cf","line":67,"in_reply_to":"88457c91_9971879a","updated":"2023-08-01 17:00:49.000000000","message":"Yeah, adding  \u003cproject\u003e-stable-core\u0027 group will create the same issue we have today. Having no maintainers is good signal to think about their EOL.\n\n@Sean yes that is what expectation is its PTL or liaisons, here PTL job is:\n* Find the liaison\n* If they do not find any liaison then either they can be liaison\n* If no laision and PTL also does not want to be then they can proposae that as there is no maintainers of interested party in that branch we propose it for EOl\n\nIf that make is clear we can explicitly mention these text.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"326e722e9c03dd05f95be1112facd89e120f538f","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"88457c91_9971879a","line":67,"in_reply_to":"96ab015c_7cb81c22","updated":"2023-07-28 15:13:52.000000000","message":"Agree, I think that they should be separate groups entirely. Small projects may need to just add themselves to that group, but I\u0027d rather default to it being basically empty. That\u0027s a signal that \"this is not maintained by the regular people.\"","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"bce17fbc56565bb8097f6cbd8c9d49878e2dcbaf","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"13d0bc62_0f198700","line":67,"in_reply_to":"a08cffb0_bde63d82","updated":"2023-07-25 22:12:06.000000000","message":"So I spoke with Kristi some about this concern, discovered this should be possible:\n\n- Upon the 18 month anniversary of a branch, the unmaintained/ version of that branch is cut\n- The PTL can then, upon that branch being created, put out a call for interested parties to be the unmaintained branch liason (I still don\u0027t like PTL being the pivot here)\n- If nobody answers that call in say, 2 weeks, the unmaintained/ branch can be closed early and EOL\u0027d.\n\nHonestly, this is OK but not great. I think it\u0027d be better if this was a more centrally managed process -- I find it difficult to believe that a majority of the TC will be OK with a project team going this route, after asking the Cinder team to stop doing basically exactly this.\n\nIf we really want to get to a point where unmaintained branches can work outside of project team assistance, we need to fully divorce them from project teams. Have a global unmaint-core team, akin to our global stable-maint team, alongside an opt-in-by-project project-specific unmaint-core team (for projects which do have people who want to be involved in this).","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"28d3e1bc6e7b1120cba3f10c73ea9f74800775fd","unresolved":true,"context_lines":[{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"},{"line_number":67,"context_line":"  group membership decisions for \"\u003cproject\u003e-unmaintained-core\"."},{"line_number":68,"context_line":"- No SLURP branches may be skipped between the oldest unmaintained branch"},{"line_number":69,"context_line":"  and the current maintained releases. This makes sure operators have an"},{"line_number":70,"context_line":"  upgrade path from one SLURP to the next all the way to maintained releases."}],"source_content_type":"text/x-rst","patch_set":6,"id":"7fe4993d_a2246db7","line":67,"in_reply_to":"eac7f648_0d1d62cf","updated":"2023-08-09 11:00:12.000000000","message":"ok so the reason i mention \u003cproject\u003e-stable-core was if we dont have anyone step up for the unmainteined release then i guess we will eol them?\n\ni have some interest in trying to keep wallaby 6-12 months\nwallaby because thats what our newest downstream product is based on.\n so i may volenteer to be a nova-unmaintained-core for that period but my time upstream is pretty limited right now so im not actully sure i can reasonably do that.\n \nso assuming i cant and other dont step up im not sure if we will have have people start supporting it out side the current core memeber. ill bring htis up internally to see if i cna get interest.\n\none thing that is in the back of my mind is being an unmainted core is less work the stable or project core.\n\nin theory the backportablity question has already been answered by the stabel core team when they agree to backprot it and the orgianl corectness has been determined by hte core team.\n\nso the unmaintained-core team just need to determin that the continuded backport has not diverged and is still correct. as such it might be a good on ramp to eventually becomeing a stable core by first being a unmainted core.\n\ni have two team meberes in mind internally that i want ot pitch this too who are not stable or project cores.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"b8fcecc9ab9b1bd2210479431c55f0d0cc6e378f","unresolved":true,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"- Until the first SLURP release ends its maintained phase, all current branches"},{"line_number":91,"context_line":"  are eligible for Unmaintained."},{"line_number":92,"context_line":"- The last 3 active Extended Maintenance branches are automatically"},{"line_number":93,"context_line":"  transitioned to Unmaintained branches."},{"line_number":94,"context_line":"- The unmaintained branch liaison needs to opt-in to keep more than 3 branches"},{"line_number":95,"context_line":"  (instead of 1 for SLURP) and the guidelines for opt-in described above apply."}],"source_content_type":"text/x-rst","patch_set":6,"id":"d5bf9f78_72d53313","line":92,"range":{"start_line":92,"start_character":6,"end_line":92,"end_character":11},"updated":"2023-07-24 21:19:37.000000000","message":"Two questions:\n1. Do you mean the *most recent* 3 EM branches (i.e., v,w,x)?\n2. How does this impact the Cinder project\u0027s proposal to EOL and delete all current EM branches?","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"0a9f0e327dab9a037d3a3a19f74fd4e41023f69d","unresolved":true,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"- Until the first SLURP release ends its maintained phase, all current branches"},{"line_number":91,"context_line":"  are eligible for Unmaintained."},{"line_number":92,"context_line":"- The last 3 active Extended Maintenance branches are automatically"},{"line_number":93,"context_line":"  transitioned to Unmaintained branches."},{"line_number":94,"context_line":"- The unmaintained branch liaison needs to opt-in to keep more than 3 branches"},{"line_number":95,"context_line":"  (instead of 1 for SLURP) and the guidelines for opt-in described above apply."}],"source_content_type":"text/x-rst","patch_set":6,"id":"2b4b2602_d26a35b8","line":92,"range":{"start_line":92,"start_character":6,"end_line":92,"end_character":11},"in_reply_to":"51a7f628_1c2bd4a8","updated":"2023-07-25 15:56:44.000000000","message":"\u003e we would not be releaseing them but rahter tagging them and deleting the branch.\n\nYeah, I mean tag (mark to fetch the last hash on those)","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5988a0f45fb21f45fe8f798dff0c1b5b62d76f43","unresolved":true,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"- Until the first SLURP release ends its maintained phase, all current branches"},{"line_number":91,"context_line":"  are eligible for Unmaintained."},{"line_number":92,"context_line":"- The last 3 active Extended Maintenance branches are automatically"},{"line_number":93,"context_line":"  transitioned to Unmaintained branches."},{"line_number":94,"context_line":"- The unmaintained branch liaison needs to opt-in to keep more than 3 branches"},{"line_number":95,"context_line":"  (instead of 1 for SLURP) and the guidelines for opt-in described above apply."}],"source_content_type":"text/x-rst","patch_set":6,"id":"51a7f628_1c2bd4a8","line":92,"range":{"start_line":92,"start_character":6,"end_line":92,"end_character":11},"in_reply_to":"6647cf9a_9c3abbd3","updated":"2023-07-25 14:49:28.000000000","message":"\u003e There is nothing forbidding here a team to opt-out from Unmaintained entirely and EOL-ing their branches, which it seems is what the Cinder team wants.\n\nYes, that\u0027s what I wanted to verify.  Since there is currently no interest in maintaining train through xena (as indicated by the non-response on the ML), the Cinder team would like to proceed with the EOL-and-deletion as proposed by https://review.opendev.org/q/topic:cinder-eol-june2023 , and if someone shows up later interested in taking responsibility, we can create the appropriate unmaintained/* branches at that point.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"7e1f57a19be82f6a6e36866d78950db2b29f3953","unresolved":true,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"- Until the first SLURP release ends its maintained phase, all current branches"},{"line_number":91,"context_line":"  are eligible for Unmaintained."},{"line_number":92,"context_line":"- The last 3 active Extended Maintenance branches are automatically"},{"line_number":93,"context_line":"  transitioned to Unmaintained branches."},{"line_number":94,"context_line":"- The unmaintained branch liaison needs to opt-in to keep more than 3 branches"},{"line_number":95,"context_line":"  (instead of 1 for SLURP) and the guidelines for opt-in described above apply."}],"source_content_type":"text/x-rst","patch_set":6,"id":"c2a91da6_f29e34e2","line":92,"range":{"start_line":92,"start_character":6,"end_line":92,"end_character":11},"in_reply_to":"b0565f28_96cfd48b","updated":"2023-07-24 21:26:57.000000000","message":"There is nothing forbidding here a team to opt-out from Unmaintained entirely and EOL-ing their branches, which it seems is what the Cinder team wants.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"3dba644dd933a48a3d0965c80a5e697e9b239d14","unresolved":true,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"- Until the first SLURP release ends its maintained phase, all current branches"},{"line_number":91,"context_line":"  are eligible for Unmaintained."},{"line_number":92,"context_line":"- The last 3 active Extended Maintenance branches are automatically"},{"line_number":93,"context_line":"  transitioned to Unmaintained branches."},{"line_number":94,"context_line":"- The unmaintained branch liaison needs to opt-in to keep more than 3 branches"},{"line_number":95,"context_line":"  (instead of 1 for SLURP) and the guidelines for opt-in described above apply."}],"source_content_type":"text/x-rst","patch_set":6,"id":"6647cf9a_9c3abbd3","line":92,"range":{"start_line":92,"start_character":6,"end_line":92,"end_character":11},"in_reply_to":"c2a91da6_f29e34e2","updated":"2023-07-25 08:23:44.000000000","message":"we would not be releaseing them but rahter tagging them and deleting the branch.","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"5e5ef86aec763830eeecc15595c2aeb3a9a597f9","unresolved":true,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"- Until the first SLURP release ends its maintained phase, all current branches"},{"line_number":91,"context_line":"  are eligible for Unmaintained."},{"line_number":92,"context_line":"- The last 3 active Extended Maintenance branches are automatically"},{"line_number":93,"context_line":"  transitioned to Unmaintained branches."},{"line_number":94,"context_line":"- The unmaintained branch liaison needs to opt-in to keep more than 3 branches"},{"line_number":95,"context_line":"  (instead of 1 for SLURP) and the guidelines for opt-in described above apply."}],"source_content_type":"text/x-rst","patch_set":6,"id":"b0565f28_96cfd48b","line":92,"range":{"start_line":92,"start_character":6,"end_line":92,"end_character":11},"in_reply_to":"d5bf9f78_72d53313","updated":"2023-07-24 21:24:09.000000000","message":"I think, yes he mean last 3 by most recent one.\n\nFor cinder proposal, we can go with the same policy s proposed here.\n\n1. delete all current EM (by releasing them with latest hash)\n2. create unmaintained/victoria, unmaintained/wallaby, unmaintained/xena as per policy listed here.\n\nsame we need to do for all the projects, does that solve the Cinder team concern ?","commit_id":"31a0a388a842bfb862e7a6d11a741cf86b57f624"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"d9520c8cf8323ef3d3f73ee1d0f6f1d49bd40e07","unresolved":true,"context_lines":[{"line_number":60,"context_line":"  a new branch is created under unmaintained/\u003cbranch_name\u003e, for example,"},{"line_number":61,"context_line":"  unmaintained/train."},{"line_number":62,"context_line":"- A group in Gerrit called \"\u003cproject\u003e-unmaintained-core\", for example,"},{"line_number":63,"context_line":"  \"keystone-unmaintained-core\", will have +2/+W on these branches. This group"},{"line_number":64,"context_line":"  may be bootstrapped with or include the \"\u003cproject\u003e-stable-maint\" group, but"},{"line_number":65,"context_line":"  membership is separate from that group."},{"line_number":66,"context_line":"- The PTL, or a new Unmaintained branch liaison assigned by the PTL, makes"}],"source_content_type":"text/x-rst","patch_set":7,"id":"f9f83713_f3e5f775","line":63,"updated":"2023-08-09 11:08:29.000000000","message":"by the way we dont need to state thsi in this doc but for unmaintained branches\ni do not think we need 2 +2s before a +w\n\ni think if we have a single +2w from someone who is not the author that is enough for the normal merge workflow and if there is only one unmaintained core then they shoudl be able to merge there own patch after a period of time if required.\n\ni.e. if your the only core there wait a week and ping the project irc and ask for reviews  and if no one objects then merge it.\n\ni was effectively the only maintainer of os-vif for a few years and that was the policy i had for that. we solved the lack of cores propbelm for os-vif kind of by\naddding the nova porject team to it so when i woudl ping in the nova channel i could usually find someone to reivew it even if most of the nova core team were not familar with the details of os-vif.\n\ni dont want to get into a situration with the unmainted branch that for procedural reasons contributors to it cant merge code because there is only one person looking at it.","commit_id":"6181213985a477f5849e59d37685d9a8527bbb49"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"40853868fa10b03943efdcbe30de89cc2dd9f625","unresolved":true,"context_lines":[{"line_number":73,"context_line":"  previous branches active."},{"line_number":74,"context_line":"- The PTL or Unmaintained branch liaison are allowed to delete an Unmaintained"},{"line_number":75,"context_line":"  branch early, before its scheduled branch deletion."},{"line_number":76,"context_line":"- The CI for all branches must be in good standing at the time of opt-in."},{"line_number":77,"context_line":"  At a minimum this needs to contain all integrated jobs, unit tests, pep8,"},{"line_number":78,"context_line":"  and functional testing."},{"line_number":79,"context_line":"  However, as this is a best-effort CI and to preserve resources, Unmaintained"}],"source_content_type":"text/x-rst","patch_set":7,"id":"74bb8477_9ebb81bb","line":76,"range":{"start_line":76,"start_character":2,"end_line":76,"end_character":72},"updated":"2023-08-09 07:01:41.000000000","message":"In case unmaintained branch removal/creation is automatic and made by releases team - how we\u0027re gonna verify/ensure that?\nThis kinda makes sense only if unmaintained branch is manually opted-in, but then previous statement `the branch is deleted and a new branch is created under unmaintained/\u003cbranch_name\u003e` is not referring to automatic process?","commit_id":"6181213985a477f5849e59d37685d9a8527bbb49"}]}