)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"55ac20e57acac4ced3d206ebdf7bc40f757d12ee","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"37b1a111_bcd6a024","updated":"2026-02-13 03:10:18.000000000","message":"thanks, lgtm","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"74a5e5af224dc22e9962bee2b990639290ffa80f","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"481e353a_412a0a29","updated":"2026-02-23 20:29:43.000000000","message":"Unrelated to the previous discussion, after reviewing https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/977374 I\u0027m wondering whether we also need to specify which arches we expect these tests to run on. Like in my understanding, all the \"required\" tests are implying to be run on amd64 only, do we need to make that explicit? Do we want to add a note about arm64 as additional optional arch? Do we want to mention other arches (like those with good distro support) and ask for donation of resources in order to be able to test those?","commit_id":"4dc1c6d1b289ff55145267da568f4a8ae738285b"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"33e125c7cb32f4eabd341803b245c465f8a887c3","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"acdde57b_023d6cb5","in_reply_to":"481e353a_412a0a29","updated":"2026-02-23 20:39:14.000000000","message":"hum that a interesting question. in the past that has been implie but there was alwasy a desire to test on arm and other archateture where possible.\n\nnova used ot have some power pc coverage form teh power kvm job\nbut that has never explicitly been stated as part fo the runtime.\n\ni arm and even riscv would be value to test at some point but i dont know if this is something this doc can adress this cycle.\n\none thing i will say si nova officlly droped supprot for 32 architecutres many year ago due to compilation issue wwhen pychyptograpy gained a rust depency and stop compling on x86\n\nthat was pre pandmeic so when we refer to x86 we really mean x86-64-v2 and newer.\n\ni have booted a vm on debian 13 using a m1 macbook air but with only 8g of ram i didnt really have a way to test that relibale. arm is becomding more common in datacenters escpilly with nvidia releaseing grace hopper so i expect non x86 demand to increase going forward.\n\n\ni belive linaro used to provide some ci capacity but i assume more of our ci providers dont have capsity for arm testing?\n\nnova does suppprot archetecure emulation in more recent release but i woudl assume vexhost and other likely dont have that aviable in the ci clouds.","commit_id":"4dc1c6d1b289ff55145267da568f4a8ae738285b"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"53f64972af2bd9e509ea7c99e5984e3cd98f576c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"961d4e42_416f26ef","in_reply_to":"acdde57b_023d6cb5","updated":"2026-03-03 18:50:36.000000000","message":"I think we could start a separate discussion around this because we\u0027ve debated distros and python versions here; and discussing cpu arch types may need wider discussions with project teams.","commit_id":"4dc1c6d1b289ff55145267da568f4a8ae738285b"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"cc54a2ad4aa3f21951054b1d23e26a5dd4eb7da0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"9dabad9c_337d130d","updated":"2026-03-03 19:09:47.000000000","message":"I am not convince about the reason of dropping python3.10 when our policy says to avoid dropping it before EOL.","commit_id":"ba4d7ffe7d5957d36213d62e549d7ca1f302e7a7"},{"author":{"_account_id":5890,"name":"Doug Goldstein","email":"cardoe@cardoe.com","username":"cardoe"},"change_message_id":"dc015210e465b29b7503c1e99ce35679e3575f89","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":4,"id":"b6668b2c_8af4a75c","updated":"2026-03-03 19:44:19.000000000","message":"I personally would like to see us include Python 3.14 but I can be swayed to not require it.","commit_id":"ba4d7ffe7d5957d36213d62e549d7ca1f302e7a7"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"6128b301cf4674d15156b7216704acec396ecde8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"7c99958c_cf4abb0a","updated":"2026-03-09 19:51:11.000000000","message":"We have sufficient RC votes, and this has marinated enough. Let\u0027s get this in and improve this further if required. Thanks all!","commit_id":"ba4d7ffe7d5957d36213d62e549d7ca1f302e7a7"}],"reference/runtimes/2026.2.rst":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"2dbf2181e1662e6ea28cad6db222135cf4c695d1","unresolved":true,"context_lines":[{"line_number":40,"context_line":"  Python 3.10 does not require full tempest testing, but py310 unit tests are"},{"line_number":41,"context_line":"  expected as a minimum requirement for all Python projects. The minimal"},{"line_number":42,"context_line":"  requirement for testing jobs against Python versions above is to ensure"},{"line_number":43,"context_line":"  language compatibility, having more extensive testing is allowed."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"2b780011_884d7fa7","line":43,"updated":"2026-02-16 16:13:43.000000000","message":"I wonder whether we should make this either optional or drop completely. does it really make sense to require a python version that will go EOL right after the release?","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"6b1f1061d7856855e964b628b78f4513bab5069b","unresolved":false,"context_lines":[{"line_number":40,"context_line":"  Python 3.10 does not require full tempest testing, but py310 unit tests are"},{"line_number":41,"context_line":"  expected as a minimum requirement for all Python projects. The minimal"},{"line_number":42,"context_line":"  requirement for testing jobs against Python versions above is to ensure"},{"line_number":43,"context_line":"  language compatibility, having more extensive testing is allowed."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"b2a30169_391b24b9","line":43,"in_reply_to":"0bb3dd23_7210bc3b","updated":"2026-03-03 18:54:00.000000000","message":"Done","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"5b5aeaef6ffa8dee5d5b2b7c791231cbab65361f","unresolved":true,"context_lines":[{"line_number":40,"context_line":"  Python 3.10 does not require full tempest testing, but py310 unit tests are"},{"line_number":41,"context_line":"  expected as a minimum requirement for all Python projects. The minimal"},{"line_number":42,"context_line":"  requirement for testing jobs against Python versions above is to ensure"},{"line_number":43,"context_line":"  language compatibility, having more extensive testing is allowed."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"8edb2c40_bd449199","line":43,"in_reply_to":"24192bd1_e6ef758c","updated":"2026-03-03 19:11:30.000000000","message":"keeping it open to discuss it further","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"da5db43813bc203eb387e0ad33a43cfeace44299","unresolved":true,"context_lines":[{"line_number":40,"context_line":"  Python 3.10 does not require full tempest testing, but py310 unit tests are"},{"line_number":41,"context_line":"  expected as a minimum requirement for all Python projects. The minimal"},{"line_number":42,"context_line":"  requirement for testing jobs against Python versions above is to ensure"},{"line_number":43,"context_line":"  language compatibility, having more extensive testing is allowed."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"f3fb020d_1f91cd19","line":43,"in_reply_to":"2b780011_884d7fa7","updated":"2026-02-18 01:00:17.000000000","message":"we exiplcitly dropped python 3.9 in 2025.2 i actuvilythink we shoudl remove 3.10 in 2026.2\n\npython now has a yearly release candance and 5 years of supprot for each release\n\ni think each .2 release we shoudl remove the oldes python and add the newst so i dont think we should be testing 3.10 at all on master for 2026.2\n\nhttps://github.com/openstack/governance/blob/master/reference/runtimes/2025.2.rst","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"a3fa84f5227461a526d114f0c3e55e0beb0d42aa","unresolved":true,"context_lines":[{"line_number":40,"context_line":"  Python 3.10 does not require full tempest testing, but py310 unit tests are"},{"line_number":41,"context_line":"  expected as a minimum requirement for all Python projects. The minimal"},{"line_number":42,"context_line":"  requirement for testing jobs against Python versions above is to ensure"},{"line_number":43,"context_line":"  language compatibility, having more extensive testing is allowed."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"55b2093a_8f9c8e8c","line":43,"in_reply_to":"31ca4532_9ff0ae17","updated":"2026-03-04 18:43:38.000000000","message":"Maybe that makes sense: we have a SLURP in front of this that has to be supported on 3.10 anyway. However, I was thinking that this being a shorter-lived release having to backport things to it that will run on unsupported python/distros so soon after the release (i.e. for most of the support cycle it will be kept running on an unsupported version) makes it less worthwhile.","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"d6f1d0e3485741eaf30cc3906c559678cc173161","unresolved":true,"context_lines":[{"line_number":40,"context_line":"  Python 3.10 does not require full tempest testing, but py310 unit tests are"},{"line_number":41,"context_line":"  expected as a minimum requirement for all Python projects. The minimal"},{"line_number":42,"context_line":"  requirement for testing jobs against Python versions above is to ensure"},{"line_number":43,"context_line":"  language compatibility, having more extensive testing is allowed."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"66d40e2d_98b660d4","line":43,"in_reply_to":"4441616a_c27c6232","updated":"2026-03-04 16:08:34.000000000","message":"Ah I see this was originally about 3.10, nevermind me :)","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"c30c76cd5f4abdd0b38c578bb5797002ae249cb1","unresolved":true,"context_lines":[{"line_number":40,"context_line":"  Python 3.10 does not require full tempest testing, but py310 unit tests are"},{"line_number":41,"context_line":"  expected as a minimum requirement for all Python projects. The minimal"},{"line_number":42,"context_line":"  requirement for testing jobs against Python versions above is to ensure"},{"line_number":43,"context_line":"  language compatibility, having more extensive testing is allowed."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"e74d7226_5d8797db","line":43,"in_reply_to":"55b2093a_8f9c8e8c","updated":"2026-03-04 19:27:11.000000000","message":"@gmaan.os14@gmail.com: \n\nPython 3.9 officially reached end-of-life (EOL) on October 31, 2025 [1][2]\n2025.2/Flamingo was released on October 1, 2025 [3]\n\nMy hope with people running OpenStack 2026.1 is that, at some point in its extended lifetime, they\u0027ll update the underlying OS to get off of a EOL python, or do so before upgrading to 2026.2 or 2027.1.\n\n[1] https://www.python.org/downloads/ \n[2] https://endoflife.date/python\n[3] https://releases.openstack.org/flamingo/schedule.html","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"3f1f0b74a5c8bfd1b828749223c02d9a52edaa29","unresolved":true,"context_lines":[{"line_number":40,"context_line":"  Python 3.10 does not require full tempest testing, but py310 unit tests are"},{"line_number":41,"context_line":"  expected as a minimum requirement for all Python projects. The minimal"},{"line_number":42,"context_line":"  requirement for testing jobs against Python versions above is to ensure"},{"line_number":43,"context_line":"  language compatibility, having more extensive testing is allowed."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"4441616a_c27c6232","line":43,"in_reply_to":"590ba9bc_ec22f6bd","updated":"2026-03-04 16:07:29.000000000","message":"I\u0027m generally of the position that we avoid pushing people to newer stuff unless we need to. Since I don\u0027t expect much delta between 3.11 and 3.12 (in terms of actual hard-to-support differences) I\u0027d rather be conservative and keep it unless there\u0027s an (actual) reason not to.","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"edb10932b5e11855462f9655afc74eba5b84dcd0","unresolved":true,"context_lines":[{"line_number":40,"context_line":"  Python 3.10 does not require full tempest testing, but py310 unit tests are"},{"line_number":41,"context_line":"  expected as a minimum requirement for all Python projects. The minimal"},{"line_number":42,"context_line":"  requirement for testing jobs against Python versions above is to ensure"},{"line_number":43,"context_line":"  language compatibility, having more extensive testing is allowed."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"31ca4532_9ff0ae17","line":43,"in_reply_to":"66d40e2d_98b660d4","updated":"2026-03-04 18:40:05.000000000","message":"@gouthampravi@gmail.com python3.9 was removed because it was EOLing before the 2025.2 release. I am not sure EOLing after a month of release is a solid reason because we anwyays have to support py31.0 for 2026.1 which will still be in supported releases after 3.10 is EOL. I was hoping the same model for 2026.2 also. If py3.10 is working for 2026.2 then why to force users to newer python. They anyways can move to newer python if EOL is impacting them.\n\nNOTE: by dropping py3.10 as min we are making openstack 2026.2 uninstallable on python3.10, that is how this runtime is implemented.","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"d7b8f7096b957d616c4d5681bff216983936f12f","unresolved":true,"context_lines":[{"line_number":40,"context_line":"  Python 3.10 does not require full tempest testing, but py310 unit tests are"},{"line_number":41,"context_line":"  expected as a minimum requirement for all Python projects. The minimal"},{"line_number":42,"context_line":"  requirement for testing jobs against Python versions above is to ensure"},{"line_number":43,"context_line":"  language compatibility, having more extensive testing is allowed."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"590ba9bc_ec22f6bd","line":43,"in_reply_to":"8edb2c40_bd449199","updated":"2026-03-03 19:21:49.000000000","message":"Yes, my initial patch retaining this was for this statement in our Python PTI... however, the branch maintenance after shipping is enormous and EOL being one month  after the release is solid reason. \n\nWe had a similar conundrum when determining the python versions to test 2025.2 with: https://review.opendev.org/c/openstack/governance/+/941141\n\nWe preferred to explicitly drop 3.9.\n\n\nI can propose a change to the PTI to consider EOL timelines pragmatically. One month is too short to warrant testing; a few months, sure..","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"cc54a2ad4aa3f21951054b1d23e26a5dd4eb7da0","unresolved":false,"context_lines":[{"line_number":40,"context_line":"  Python 3.10 does not require full tempest testing, but py310 unit tests are"},{"line_number":41,"context_line":"  expected as a minimum requirement for all Python projects. The minimal"},{"line_number":42,"context_line":"  requirement for testing jobs against Python versions above is to ensure"},{"line_number":43,"context_line":"  language compatibility, having more extensive testing is allowed."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"24192bd1_e6ef758c","line":43,"in_reply_to":"b2a30169_391b24b9","updated":"2026-03-03 19:09:47.000000000","message":"But that is not EOL during 2026.2 cycle so we should avoid removing the support in advance. I think that is what we agreed on when operators/package maintainer asked about py3.6 removal and we made policy of not dropping the support of min python unless it is EOL or any solid reason that it cannot be supported.\n\nhttps://governance.openstack.org/tc/reference/pti/python.html\n\n\"Projects should avoid removing Python versions that have not reached End Of Life without a solid reason. It is recommended to keep compatibility with older Python versions as long as possible. While CI coverage of Python versions that are not mentioned in PTI can be reduced, such reduction is not mandatory.\"","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b2580bf8fc0ee5e412b19e52e31efb2d53fba22e","unresolved":false,"context_lines":[{"line_number":40,"context_line":"  Python 3.10 does not require full tempest testing, but py310 unit tests are"},{"line_number":41,"context_line":"  expected as a minimum requirement for all Python projects. The minimal"},{"line_number":42,"context_line":"  requirement for testing jobs against Python versions above is to ensure"},{"line_number":43,"context_line":"  language compatibility, having more extensive testing is allowed."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7049338e_3e26fb16","line":43,"in_reply_to":"e74d7226_5d8797db","updated":"2026-03-05 19:11:42.000000000","message":"SLUPR/non-SLURP transition is good point here 2026.1 (on py3.10) -\u003e 2027.1 (without 3.10) upgrade needs go from python 3.10 to higher version so doing same for 2026.1 -\u003e 2026.2 should not be an issue which is similar to py3.9 (thanks for correcting the timelines for py3.9).\n\nI think i am good here and agree on overall value to keep 3.10 in 2026.2 non-SLURP.","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"8f0a57ffd52e5df48f0ccf019c9742a95b51cbcd","unresolved":true,"context_lines":[{"line_number":40,"context_line":"  Python 3.10 does not require full tempest testing, but py310 unit tests are"},{"line_number":41,"context_line":"  expected as a minimum requirement for all Python projects. The minimal"},{"line_number":42,"context_line":"  requirement for testing jobs against Python versions above is to ensure"},{"line_number":43,"context_line":"  language compatibility, having more extensive testing is allowed."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"0bb3dd23_7210bc3b","line":43,"in_reply_to":"f3fb020d_1f91cd19","updated":"2026-02-19 22:21:30.000000000","message":"yes, that\u0027s true and we had this discussion during the 2025.2 timeframe, and you\u0027re both right. It makes no sense to require this.\n\npython 3.10 will go EOL a month after we ship 2026.2:\n\"The 2026.2 Hibiscus coordinated release will happen on Wednesday, September 30, 2026\"\n\nWe can move to 3.11 (eol Oct 31, 2027) as the minimum version.","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"2dbf2181e1662e6ea28cad6db222135cf4c695d1","unresolved":true,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"  In previous cycle testing, we have not seen many incompatible changes between"},{"line_number":48,"context_line":"  Python 3.10 and Python 3.11. It is okay to skip running Python 3.11"},{"line_number":49,"context_line":"  testing jobs assuming that anything that works on Python 3.10 and 3.13 will"},{"line_number":50,"context_line":"  also work on 3.11. Periodic testing should be enough for this."},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"4bbd07ff_fc62267a","line":48,"range":{"start_line":47,"start_character":3,"end_line":48,"end_character":30},"updated":"2026-02-16 16:13:43.000000000","message":"I\u0027m not sure that this is still true, since we essentially do no testing anyone looks at with py3.11. I did see some significant differences in the reqs testing though between py3.10 and 11\n\nso my suggestion would be to make py3.10 optional (maybe via periodic only or decision per project) and py3.11 mandatory instead","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"da5db43813bc203eb387e0ad33a43cfeace44299","unresolved":true,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"  In previous cycle testing, we have not seen many incompatible changes between"},{"line_number":48,"context_line":"  Python 3.10 and Python 3.11. It is okay to skip running Python 3.11"},{"line_number":49,"context_line":"  testing jobs assuming that anything that works on Python 3.10 and 3.13 will"},{"line_number":50,"context_line":"  also work on 3.11. Periodic testing should be enough for this."},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"df9e4fb3_bdb3e453","line":48,"range":{"start_line":47,"start_character":3,"end_line":48,"end_character":30},"in_reply_to":"4bbd07ff_fc62267a","updated":"2026-02-18 01:00:17.000000000","message":"i also disagre with the current text this should be mandaoty to test and 3.10 shoudl be remnove or at most optional.","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"8f0a57ffd52e5df48f0ccf019c9742a95b51cbcd","unresolved":false,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Python 3.11 (available as default in Debian 12)"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"  In previous cycle testing, we have not seen many incompatible changes between"},{"line_number":48,"context_line":"  Python 3.10 and Python 3.11. It is okay to skip running Python 3.11"},{"line_number":49,"context_line":"  testing jobs assuming that anything that works on Python 3.10 and 3.13 will"},{"line_number":50,"context_line":"  also work on 3.11. Periodic testing should be enough for this."},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"0eebfa22_c2950578","line":48,"range":{"start_line":47,"start_character":3,"end_line":48,"end_character":30},"in_reply_to":"df9e4fb3_bdb3e453","updated":"2026-02-19 22:21:30.000000000","message":"ack","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"2dbf2181e1662e6ea28cad6db222135cf4c695d1","unresolved":true,"context_lines":[{"line_number":54,"context_line":"  In previous cycle testing, we have not seen many incompatible changes between"},{"line_number":55,"context_line":"  Python 3.10 and Python 3.12. It is okay to skip running Python 3.12"},{"line_number":56,"context_line":"  testing jobs assuming that anything that works on Python 3.10 and 3.13 will"},{"line_number":57,"context_line":"  also work on 3.12. Periodic testing should be enough for this."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"* Python 3.13 (available as default in Debian 13)"},{"line_number":60,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"96dde7c6_0ef04efc","line":57,"updated":"2026-02-16 16:13:43.000000000","message":"py3.12 could then stay on periodic-only","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"8f0a57ffd52e5df48f0ccf019c9742a95b51cbcd","unresolved":true,"context_lines":[{"line_number":54,"context_line":"  In previous cycle testing, we have not seen many incompatible changes between"},{"line_number":55,"context_line":"  Python 3.10 and Python 3.12. It is okay to skip running Python 3.12"},{"line_number":56,"context_line":"  testing jobs assuming that anything that works on Python 3.10 and 3.13 will"},{"line_number":57,"context_line":"  also work on 3.12. Periodic testing should be enough for this."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"* Python 3.13 (available as default in Debian 13)"},{"line_number":60,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5c18b926_8aa2bc2a","line":57,"in_reply_to":"8fd17dd3_d515f35b","updated":"2026-02-19 22:21:30.000000000","message":"that\u0027s interesting enough to call out.","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"da5db43813bc203eb387e0ad33a43cfeace44299","unresolved":true,"context_lines":[{"line_number":54,"context_line":"  In previous cycle testing, we have not seen many incompatible changes between"},{"line_number":55,"context_line":"  Python 3.10 and Python 3.12. It is okay to skip running Python 3.12"},{"line_number":56,"context_line":"  testing jobs assuming that anything that works on Python 3.10 and 3.13 will"},{"line_number":57,"context_line":"  also work on 3.12. Periodic testing should be enough for this."},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"* Python 3.13 (available as default in Debian 13)"},{"line_number":60,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"8fd17dd3_d515f35b","line":57,"in_reply_to":"96dde7c6_0ef04efc","updated":"2026-02-18 01:00:17.000000000","message":"+1\n\nmost tempest jobs are goign to run either on noble or trixie so most of the tempest level coverate will happen on 3.12 or 3.13\n\nso runing or tox test on 3.11 and 3.14 will give use coverate of the upper and lower bound and tempest will test the release in between.","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"da5db43813bc203eb387e0ad33a43cfeace44299","unresolved":true,"context_lines":[{"line_number":65,"context_line":"  This is not mandatory testing in the 2026.2 cycle, and there is no guarantee"},{"line_number":66,"context_line":"  that the OpenStack 2026.2 release will support Python 3.14. Python 3.14"},{"line_number":67,"context_line":"  was released in October 2025 and is the default Python version in"},{"line_number":68,"context_line":"  Ubuntu 26.04."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"  .. warning::"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"51f51648_65b82607","line":68,"updated":"2026-02-18 01:00:17.000000000","message":"i think 3.14 should be added as manadory it was optional in 2026.1 so we should be graduating it to mandeotry now.\n\nhttps://github.com/openstack/governance/blob/master/reference/runtimes/2026.1.rst?plain\u003d1#L66","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"c262095b4d2f920743d0f99fea1f06a36799b178","unresolved":true,"context_lines":[{"line_number":65,"context_line":"  This is not mandatory testing in the 2026.2 cycle, and there is no guarantee"},{"line_number":66,"context_line":"  that the OpenStack 2026.2 release will support Python 3.14. Python 3.14"},{"line_number":67,"context_line":"  was released in October 2025 and is the default Python version in"},{"line_number":68,"context_line":"  Ubuntu 26.04."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"  .. warning::"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"f1f77bfa_92a8c195","line":68,"in_reply_to":"05729466_dd03b584","updated":"2026-02-19 15:58:48.000000000","message":"I share the same concern as frickler, We recommended it in 2026.1 but there was no actual testing happened.\nWithout actually testing it, I do not consider this doc a valid path to move it to mandatory in 2026.2. Even its a doc bug and should be updated in 2026.1 runtime to reflect the reality:).","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"9b0d7f0e125f517b078c063c2da7a25a9629e0ab","unresolved":true,"context_lines":[{"line_number":65,"context_line":"  This is not mandatory testing in the 2026.2 cycle, and there is no guarantee"},{"line_number":66,"context_line":"  that the OpenStack 2026.2 release will support Python 3.14. Python 3.14"},{"line_number":67,"context_line":"  was released in October 2025 and is the default Python version in"},{"line_number":68,"context_line":"  Ubuntu 26.04."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"  .. warning::"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"05729466_dd03b584","line":68,"in_reply_to":"51f51648_65b82607","updated":"2026-02-19 15:54:34.000000000","message":"although 3.14 was added to the PTI, we still are not running any actual testing, see https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/968510\nso without any real experience on how things fare, I don\u0027t think we can reasonably make it mandatory at this time","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"e48fa4d4b7b329d18b65a6a1e852976576ff75b7","unresolved":true,"context_lines":[{"line_number":65,"context_line":"  This is not mandatory testing in the 2026.2 cycle, and there is no guarantee"},{"line_number":66,"context_line":"  that the OpenStack 2026.2 release will support Python 3.14. Python 3.14"},{"line_number":67,"context_line":"  was released in October 2025 and is the default Python version in"},{"line_number":68,"context_line":"  Ubuntu 26.04."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"  .. warning::"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa521b43_2fed34db","line":68,"in_reply_to":"f1f77bfa_92a8c195","updated":"2026-02-19 16:23:50.000000000","message":"i think we shoudl state it as manadroy this cycle adn remvoe it if we find it cant be tested.\n\n\nif we don\u0027t then there is little intensive for project to invest in making it work.\n\nwith that said i care more about not requriing 3.10 to be mandaory then i do about pullignin 3.14 but i  think we shoudl do both.\n\nid dont think we should claim to supprot a python version that wil be EOL before we release. so i dont think including 3.10 in the 2026.2 runtimes is reasonable","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"8f0a57ffd52e5df48f0ccf019c9742a95b51cbcd","unresolved":true,"context_lines":[{"line_number":65,"context_line":"  This is not mandatory testing in the 2026.2 cycle, and there is no guarantee"},{"line_number":66,"context_line":"  that the OpenStack 2026.2 release will support Python 3.14. Python 3.14"},{"line_number":67,"context_line":"  was released in October 2025 and is the default Python version in"},{"line_number":68,"context_line":"  Ubuntu 26.04."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"  .. warning::"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"028b385e_618b59cc","line":68,"in_reply_to":"fa521b43_2fed34db","updated":"2026-02-19 22:21:30.000000000","message":"it was recommended in 2026.1, we didn\u0027t get around to it... that part\u0027s mentioned in the commit message. \n\nI think the push back has been that we\u0027d like to run this on a distro that supports the python 3.14 interpreter without us having to spend some time to compile it into an image, or into a test node. I\u0027ve called this out as well in the commit message hoping to spark this same discussion.. \n\nI think we can be conservative about it and highly/strongly recommend it rather than require it just because of the fact that we\u0027d need to begin the work now.. realistically, i\u0027d expect to begin using the Ubuntu 26.04 LTS image as soon as it is available for py3.14 testing and fixing up any bugs. There\u0027ll be a larger effort to use it for functional/e2e/devstack based testing that we shouldn\u0027t commit the cycle for.","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"55ac20e57acac4ced3d206ebdf7bc40f757d12ee","unresolved":false,"context_lines":[{"line_number":98,"context_line":""},{"line_number":99,"context_line":"* CentOS Stream 10"},{"line_number":100,"context_line":"* Rocky Linux 10"},{"line_number":101,"context_line":"* AlmaLinux 10"},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"  AlmaLinux 10\u0027s continued support for x86_64_v2 makes it a compelling option"},{"line_number":104,"context_line":"  for project teams due to greater CI node availability. However, we do not"}],"source_content_type":"text/x-rst","patch_set":1,"id":"eacb1e44_3e339dee","line":101,"range":{"start_line":101,"start_character":0,"end_line":101,"end_character":14},"updated":"2026-02-13 03:10:18.000000000","message":"++, devstack AlmaLinux job is not in bad state\n\nhttps://zuul.opendev.org/t/openstack/builds?job_name\u003ddevstack-platform-almalinux-purple-lion-ovn-source\u0026skip\u003d0","commit_id":"cc27832763885e02f236be1ba7e52300d72e07c4"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"f6116a081e546c36886107b8b1abbcf15910cf33","unresolved":true,"context_lines":[{"line_number":11,"context_line":"distribution \u003cpti-linux-distros\u003e` versions are:"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"* Ubuntu 24.04"},{"line_number":14,"context_line":"* Debian 12"},{"line_number":15,"context_line":"* Debian 13"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Additional testing for a smooth upgrade"}],"source_content_type":"text/x-rst","patch_set":3,"id":"6bd3a8ca_347d6471","line":14,"range":{"start_line":14,"start_character":0,"end_line":14,"end_character":11},"updated":"2026-02-20 16:38:38.000000000","message":"2026.1 was technically the release that supprot 12 for smoth upgrades\nso it should not be inlcuded itn thr runtimes anymore.\n\nwe normally only supprot the most recnt lts release of a disto with 1 cycle for upgrades and that is genreally the .1 slurp release.\n\n\nrunning  tox  3.11 jobs on it makes sens but i would not expect temepst/devstack testing on debian 12 this cycle in genreal. project can choose to test mroe then the baseline but i would strongly prefer tesitng on 13 orver 12 if debian is used.\n\nhttps://github.com/openstack/governance/blob/master/reference/runtimes/2026.1.rst?plain\u003d1#L16","commit_id":"4dc1c6d1b289ff55145267da568f4a8ae738285b"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"6b1f1061d7856855e964b628b78f4513bab5069b","unresolved":false,"context_lines":[{"line_number":11,"context_line":"distribution \u003cpti-linux-distros\u003e` versions are:"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"* Ubuntu 24.04"},{"line_number":14,"context_line":"* Debian 12"},{"line_number":15,"context_line":"* Debian 13"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Additional testing for a smooth upgrade"}],"source_content_type":"text/x-rst","patch_set":3,"id":"b8ed4bac_29621b17","line":14,"range":{"start_line":14,"start_character":0,"end_line":14,"end_character":11},"in_reply_to":"0eaa1733_c8cfb598","updated":"2026-03-03 18:54:00.000000000","message":"Done","commit_id":"4dc1c6d1b289ff55145267da568f4a8ae738285b"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"7db87a5ac8a518f544c15730e0aaa6a302c8ecd3","unresolved":true,"context_lines":[{"line_number":11,"context_line":"distribution \u003cpti-linux-distros\u003e` versions are:"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"* Ubuntu 24.04"},{"line_number":14,"context_line":"* Debian 12"},{"line_number":15,"context_line":"* Debian 13"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Additional testing for a smooth upgrade"}],"source_content_type":"text/x-rst","patch_set":3,"id":"f3bd4036_dd135bcf","line":14,"range":{"start_line":14,"start_character":0,"end_line":14,"end_character":11},"in_reply_to":"6bd3a8ca_347d6471","updated":"2026-02-20 19:57:09.000000000","message":"Yes, i was adding it back here just to indicate we\u0027d use it for unit testing with py311. That\u0027s confusing isn\u0027t it?\n\ndon\u0027t know if i can clarify that point (line 38 calls this out), or just drop this entirely, and assume it\u0027s obvious.","commit_id":"4dc1c6d1b289ff55145267da568f4a8ae738285b"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"6912e4b32295769777adbd6f0cb16f2a1d49819c","unresolved":true,"context_lines":[{"line_number":11,"context_line":"distribution \u003cpti-linux-distros\u003e` versions are:"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"* Ubuntu 24.04"},{"line_number":14,"context_line":"* Debian 12"},{"line_number":15,"context_line":"* Debian 13"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Additional testing for a smooth upgrade"}],"source_content_type":"text/x-rst","patch_set":3,"id":"0eaa1733_c8cfb598","line":14,"range":{"start_line":14,"start_character":0,"end_line":14,"end_character":11},"in_reply_to":"f3bd4036_dd135bcf","updated":"2026-02-21 09:29:33.000000000","message":"I agree we should drop Debian 12 from here (or indicate we only do unit testing on it) to avoid any confusions that it is a good platform for deploying 2026.2 in production","commit_id":"4dc1c6d1b289ff55145267da568f4a8ae738285b"},{"author":{"_account_id":22629,"name":"Michal Nasiadka","email":"mnasiadka@gmail.com","username":"mnasiadka"},"change_message_id":"6912e4b32295769777adbd6f0cb16f2a1d49819c","unresolved":true,"context_lines":[{"line_number":95,"context_line":"* Rocky Linux 10"},{"line_number":96,"context_line":"* AlmaLinux 10"},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"  AlmaLinux 10\u0027s continued support for x86_64_v2 makes it a compelling option"},{"line_number":99,"context_line":"  for project teams due to greater CI node availability. However, we do not"},{"line_number":100,"context_line":"  expect any major differences to crop up between these Enterprise Linux"},{"line_number":101,"context_line":"  distributions. Project teams can make a choice based on their needs."}],"source_content_type":"text/x-rst","patch_set":3,"id":"a4ed1c24_b38797f2","line":98,"updated":"2026-02-21 09:29:33.000000000","message":"Should we mention that Alma 10 x86_64_v2 is missing critical dependencies like OVS/OVN?","commit_id":"4dc1c6d1b289ff55145267da568f4a8ae738285b"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"53f64972af2bd9e509ea7c99e5984e3cd98f576c","unresolved":false,"context_lines":[{"line_number":95,"context_line":"* Rocky Linux 10"},{"line_number":96,"context_line":"* AlmaLinux 10"},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"  AlmaLinux 10\u0027s continued support for x86_64_v2 makes it a compelling option"},{"line_number":99,"context_line":"  for project teams due to greater CI node availability. However, we do not"},{"line_number":100,"context_line":"  expect any major differences to crop up between these Enterprise Linux"},{"line_number":101,"context_line":"  distributions. Project teams can make a choice based on their needs."}],"source_content_type":"text/x-rst","patch_set":3,"id":"f3233f28_c169638f","line":98,"in_reply_to":"756cc39d_43fe82dd","updated":"2026-03-03 18:50:36.000000000","message":"+1; don\u0027t feel comfortable enshrining that information in the PTI.. i\u0027m hoping we can find someone to build and maintain the missing packages through our outreach.","commit_id":"4dc1c6d1b289ff55145267da568f4a8ae738285b"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"b05be827e894725b4ccb663b32629477d24161b4","unresolved":true,"context_lines":[{"line_number":95,"context_line":"* Rocky Linux 10"},{"line_number":96,"context_line":"* AlmaLinux 10"},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"  AlmaLinux 10\u0027s continued support for x86_64_v2 makes it a compelling option"},{"line_number":99,"context_line":"  for project teams due to greater CI node availability. However, we do not"},{"line_number":100,"context_line":"  expect any major differences to crop up between these Enterprise Linux"},{"line_number":101,"context_line":"  distributions. Project teams can make a choice based on their needs."}],"source_content_type":"text/x-rst","patch_set":3,"id":"756cc39d_43fe82dd","line":98,"in_reply_to":"a4ed1c24_b38797f2","updated":"2026-02-23 20:41:07.000000000","message":"perhaps but even on ubuntu thre were a few releases where neton complied ovs form souce to work aorund bugs in the ubuntu version so its not that uncommon.\nit would be nice if that was eventully adress in alma but we have ways to test with ovs and ovn on alma already.","commit_id":"4dc1c6d1b289ff55145267da568f4a8ae738285b"}]}