)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"050c387c22834f439c7580d7d943be39bfb25951","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"d028b176_7f5d211e","updated":"2023-06-27 17:40:30.000000000","message":"Thanks Jay. I am not sure if we need to call out the deprecation action here which can be done via our process of marking inactive projects. Let\u0027s keep it a migration plan only.","commit_id":"47d83ddee41ed619c906b5fdbf659c43621bd7e5"},{"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":"ae6732f659a7a9e785f7529fa7dda3fe17e508c6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ed63d842_52215b18","updated":"2023-07-11 13:00:59.000000000","message":"Grammar issues have been addressed. I do not wish to make this resolution less strong; we cannot put our distro partners and ourselves in a bind by being the last software project to migrate to sqlalchemy 2.0.\n\nI don\u0027t think of a project being forced to migrate or go inactive as a punitive action; it\u0027s more of a reflection of that projects inability to maintain their software.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b3a7cea71584f772418758774726d04d15c96fc4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"1c513730_6619249f","updated":"2023-06-27 18:54:43.000000000","message":"I still think not to put any action on this and keep it for migration plan only","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"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":"a73fe5896392ed58d11434008bd5e02cbbe7151f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"0678e3cb_4b1edfa6","updated":"2023-06-28 18:29:15.000000000","message":"I will revise this for grammar/spelling/wording concerns once the substantive bits are settled and revised to match discussion. I see+appreciate your comments :D","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":15993,"name":"Amy Marrich","display_name":"Amy Marrich (spotz)","email":"amy@demarco.com","username":"amarrich"},"change_message_id":"dfe7239ca22fa05c66d6dc3498722fe33ed577e8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ab137dd4_c4c845a8","updated":"2023-06-27 20:32:26.000000000","message":"grammary things","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"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":"5cbdfad48a1f5769d218bbdd402879e3eb7bd5f1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"f67166d9_76e89309","updated":"2023-07-14 14:00:08.000000000","message":"Based on conversation in #openstack-tc today; it\u0027s now not as clear to me that 2024.1 is actually the technical deadline for this change. I took this date from the notes from the forum session.\n\nI\u0027m going to research and add some supporting information about when distros may be shipping this as proof that 2024.1 is the right deadline (or find that a later deadline may be preferable).","commit_id":"6146529bd71ad18169af78a9c218998c5b129ca0"},{"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":"0d58b193ca3451408f4b9543529a09f05b314478","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"4faff058_62bfe10c","updated":"2023-09-08 18:17:52.000000000","message":"I did some digging here:\n\nNo distribution we target ships sqlalchemy 2.0. This includes things like OpenSuse Tumbleweed and Fedora Rawhide. The only packaged distro version of SQLAlchemy 2.0 is in Gentoo right now (where it is stable; but 1.4.x is also available).\n\nThis indicates to me that it\u0027s extremely unlikely we\u0027ll have to do this migration anytime soon.\n\nAs a result; I\u0027m abandoning this change until Ubuntu, Debian, or RH ships a SQLAlchemy 2.0 package.","commit_id":"6146529bd71ad18169af78a9c218998c5b129ca0"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"a59c66a2093e5eb84f05e8f105dc3a2de863a58a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"14e91808_40b43e41","updated":"2023-07-11 14:50:51.000000000","message":"I\u0027m still -1 on the stick approach here. There are multiple ways to insulate a service from the distro packages (containers, venvs, etc) which are in use by plenty of real deployments. Our own devstack will have to move to fully isolating everything in one or more venvs in order to even work on ubuntu 23.04, debian 12, and others. Experience with threats for maintenance items in the past leads me to believe this is the wrong approach here as well.","commit_id":"6146529bd71ad18169af78a9c218998c5b129ca0"},{"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":"61ee3014affc79e2fe4a78fd062bd8edb3e021c8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"a31c0e2c_a8e1fea2","updated":"2023-07-14 10:43:56.000000000","message":"It\u0027s unclear to me if I should RC+1 my own patch; I couldn\u0027t find anything in governance relevant -- if it\u0027s against our rules, please show me (so I\u0027ll know how I didn\u0027t find the doc in the first place), and I\u0027ll happily drop the vote.","commit_id":"6146529bd71ad18169af78a9c218998c5b129ca0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"c28df8ac0b82c1f4f895f58fce746b896cd3fec1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"8ffd9997_83419ba3","updated":"2023-07-11 16:32:58.000000000","message":"One more thing, I am not happy how previous voting are gone due to the nit updates etc. Please try to keep them as follow up so that we have existing voting either it is -1 or +1 to get clarity on how discussion/agreement is going. Honestly saying I could have easily forgot to revote here even my concern to the proposal is not resolved. This is my humble request.\n\nOther idea we can do (did in past) in TC is propose multiple proposal if there is a slightly change in the proposal so that we know which one is going more closure to agreement.","commit_id":"6146529bd71ad18169af78a9c218998c5b129ca0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"a5ed620d92f4e8be3886076a7489fee0de19ffc7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"d6202be0_be57ee54","in_reply_to":"a31c0e2c_a8e1fea2","updated":"2023-07-14 14:52:40.000000000","message":"You can do and you should do so that we can count the motion quorum. Rule is written in house rule for the code change etc where author vote will be excluded otherwise author must vote on their proposal to have quorum counted correctly.","commit_id":"6146529bd71ad18169af78a9c218998c5b129ca0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"fa1bb47b8bca0c7cafde4a668d4a8bd80cbf75b7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"e2933f3b_e7e396b8","in_reply_to":"f67166d9_76e89309","updated":"2023-07-14 16:34:08.000000000","message":"I am not against of early deadline even distro are supporting that. Having a early migration plan in advance is good. \n\nBelow is something we can do (discussed in IRC also today):\n\n1. set deadline (any early deadline is ok to avopid risk at the end)\n2. create a clear migration plan with exmaple of work\n3. Plan can include adding the testing to show failure/work needed\n4. Help projects with a fewer contributors/have-less-idea about work. As stephenfin is already doing since long and more people can help.\n\nAnd as we do have time for hard stop why not this can be a community-wide goal where we can communicate the plan and finish work in a better way","commit_id":"6146529bd71ad18169af78a9c218998c5b129ca0"}],"resolutions/20230627-sqlalchemy2-migration.rst":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"050c387c22834f439c7580d7d943be39bfb25951","unresolved":true,"context_lines":[{"line_number":31,"context_line":"      SQLAlchemy in requirements to 2.0. Shortly after, audit the CI status of"},{"line_number":32,"context_line":"      projects and notify PTLs of any projects that are not passing CI that"},{"line_number":33,"context_line":"      they are at risk of being excluded from the 2024.1 release and"},{"line_number":34,"context_line":"      deprecated."},{"line_number":35,"context_line":"    - Three weeks before milestone two of release 2024.1, any project still"},{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will have their deprecation"},{"line_number":37,"context_line":"      proposed to the governance repo."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their deprecation approved."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ce768b63_ba70f7b7","line":39,"range":{"start_line":34,"start_character":0,"end_line":39,"end_character":57},"updated":"2023-06-27 17:40:30.000000000","message":"I think deprecation of project because of this seems little bit strong action to mention here. We have been stuck for many things/migration over the years due to techcnical or non-technical reason. \n\nI will suggest to remove the deprecation action from here. And we can say if you do not migrate then project gate will be blocked as we bump the requirement.\n\nLet\u0027s keep both things separate 1. migration plan 2. keep monitoring and filtering the inactive project. As per our project inactive process, any project not active and not fixing their gate (failing due to this migration or any other reason) will be moved to Inactive list and next steps mentioned in this doc https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html","commit_id":"47d83ddee41ed619c906b5fdbf659c43621bd7e5"},{"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":"ae6732f659a7a9e785f7529fa7dda3fe17e508c6","unresolved":false,"context_lines":[{"line_number":31,"context_line":"      SQLAlchemy in requirements to 2.0. Shortly after, audit the CI status of"},{"line_number":32,"context_line":"      projects and notify PTLs of any projects that are not passing CI that"},{"line_number":33,"context_line":"      they are at risk of being excluded from the 2024.1 release and"},{"line_number":34,"context_line":"      deprecated."},{"line_number":35,"context_line":"    - Three weeks before milestone two of release 2024.1, any project still"},{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will have their deprecation"},{"line_number":37,"context_line":"      proposed to the governance repo."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their deprecation approved."}],"source_content_type":"text/x-rst","patch_set":1,"id":"10ded165_55b85ae5","line":39,"range":{"start_line":34,"start_character":0,"end_line":39,"end_character":57},"in_reply_to":"b5be7b65_d919194d","updated":"2023-07-11 13:00:59.000000000","message":"Done","commit_id":"47d83ddee41ed619c906b5fdbf659c43621bd7e5"},{"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":"487eaf458b02efd75eefa62fe2bb3f32da0c87dc","unresolved":true,"context_lines":[{"line_number":31,"context_line":"      SQLAlchemy in requirements to 2.0. Shortly after, audit the CI status of"},{"line_number":32,"context_line":"      projects and notify PTLs of any projects that are not passing CI that"},{"line_number":33,"context_line":"      they are at risk of being excluded from the 2024.1 release and"},{"line_number":34,"context_line":"      deprecated."},{"line_number":35,"context_line":"    - Three weeks before milestone two of release 2024.1, any project still"},{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will have their deprecation"},{"line_number":37,"context_line":"      proposed to the governance repo."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their deprecation approved."}],"source_content_type":"text/x-rst","patch_set":1,"id":"b5be7b65_d919194d","line":39,"range":{"start_line":34,"start_character":0,"end_line":39,"end_character":57},"in_reply_to":"ce768b63_ba70f7b7","updated":"2023-06-27 17:46:07.000000000","message":"Aha, yeah, this is what I was trying to communicate and did a bad job of it. I\u0027ll revise this to reflect the inactivity process.","commit_id":"47d83ddee41ed619c906b5fdbf659c43621bd7e5"},{"author":{"_account_id":15993,"name":"Amy Marrich","display_name":"Amy Marrich (spotz)","email":"amy@demarco.com","username":"amarrich"},"change_message_id":"dfe7239ca22fa05c66d6dc3498722fe33ed577e8","unresolved":true,"context_lines":[{"line_number":2,"context_line":"2022-06-27 Migrate to SQLAlchemy 2"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"SQLAlchemy is a library at the core of most oslo.db and used by projects that"},{"line_number":6,"context_line":"require a database. Recently, SQLAlchemy 2.0 was released with significant"},{"line_number":7,"context_line":"breaking changes and will require coordination for OpenStack projects to"},{"line_number":8,"context_line":"migrate."}],"source_content_type":"text/x-rst","patch_set":2,"id":"aab14f68_9b3175ea","line":5,"updated":"2023-06-27 20:32:26.000000000","message":"not sure most is needed here","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"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":"ae6732f659a7a9e785f7529fa7dda3fe17e508c6","unresolved":false,"context_lines":[{"line_number":2,"context_line":"2022-06-27 Migrate to SQLAlchemy 2"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"SQLAlchemy is a library at the core of most oslo.db and used by projects that"},{"line_number":6,"context_line":"require a database. Recently, SQLAlchemy 2.0 was released with significant"},{"line_number":7,"context_line":"breaking changes and will require coordination for OpenStack projects to"},{"line_number":8,"context_line":"migrate."}],"source_content_type":"text/x-rst","patch_set":2,"id":"6eaa166c_07d18000","line":5,"in_reply_to":"aab14f68_9b3175ea","updated":"2023-07-11 13:00:59.000000000","message":"Ack","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"76b59039b88e5777a60b9b86926b3ff3aca08fa7","unresolved":true,"context_lines":[{"line_number":7,"context_line":"breaking changes and will require coordination for OpenStack projects to"},{"line_number":8,"context_line":"migrate."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"OpenStack has a synced requirements reprository, where projects work to"},{"line_number":11,"context_line":"remain co-installable. In order to fulfill this requirement, all projects"},{"line_number":12,"context_line":"must work together to atomically cut over the requirement to SQLAlchemy 2.0."},{"line_number":13,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"144a4377_5af68348","line":10,"range":{"start_line":10,"start_character":36,"end_line":10,"end_character":47},"updated":"2023-06-27 18:21:35.000000000","message":"\"repository\"","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"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":"ae6732f659a7a9e785f7529fa7dda3fe17e508c6","unresolved":false,"context_lines":[{"line_number":7,"context_line":"breaking changes and will require coordination for OpenStack projects to"},{"line_number":8,"context_line":"migrate."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"OpenStack has a synced requirements reprository, where projects work to"},{"line_number":11,"context_line":"remain co-installable. In order to fulfill this requirement, all projects"},{"line_number":12,"context_line":"must work together to atomically cut over the requirement to SQLAlchemy 2.0."},{"line_number":13,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"0615432c_7caf8e8d","line":10,"range":{"start_line":10,"start_character":36,"end_line":10,"end_character":47},"in_reply_to":"144a4377_5af68348","updated":"2023-07-11 13:00:59.000000000","message":"Ack","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":15993,"name":"Amy Marrich","display_name":"Amy Marrich (spotz)","email":"amy@demarco.com","username":"amarrich"},"change_message_id":"dfe7239ca22fa05c66d6dc3498722fe33ed577e8","unresolved":true,"context_lines":[{"line_number":14,"context_line":"One of the difficulties of this migration is that projects may have been using"},{"line_number":15,"context_line":"SQLAlchemy-migrate to perform their database migrations. SQLAlchemy-migrate is"},{"line_number":16,"context_line":"no longer supported in SQLAlchemy 2.0. This means that projects may also need"},{"line_number":17,"context_line":"to migrate their database migrations to alembic as part of this work."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"These facts lead to an unfortunate result: any project that is unable to"},{"line_number":20,"context_line":"ensure compatability for SQLAlchemy 2.0 for the 2024.1 release will be unable"}],"source_content_type":"text/x-rst","patch_set":2,"id":"2b805089_1c60685c","line":17,"updated":"2023-06-27 20:32:26.000000000","message":"too many migrates. Maybe move or transition?","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"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":"e847fcfa87ce2f9600caeb91558b30bccf34f9a0","unresolved":false,"context_lines":[{"line_number":14,"context_line":"One of the difficulties of this migration is that projects may have been using"},{"line_number":15,"context_line":"SQLAlchemy-migrate to perform their database migrations. SQLAlchemy-migrate is"},{"line_number":16,"context_line":"no longer supported in SQLAlchemy 2.0. This means that projects may also need"},{"line_number":17,"context_line":"to migrate their database migrations to alembic as part of this work."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"These facts lead to an unfortunate result: any project that is unable to"},{"line_number":20,"context_line":"ensure compatability for SQLAlchemy 2.0 for the 2024.1 release will be unable"}],"source_content_type":"text/x-rst","patch_set":2,"id":"a875f591_7c132948","line":17,"in_reply_to":"2b805089_1c60685c","updated":"2023-07-11 13:07:32.000000000","message":"Done","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"76b59039b88e5777a60b9b86926b3ff3aca08fa7","unresolved":true,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"These facts lead to an unfortunate result: any project that is unable to"},{"line_number":20,"context_line":"ensure compatability for SQLAlchemy 2.0 for the 2024.1 release will be unable"},{"line_number":21,"context_line":"to be released and will be marked inactive [0]_ . Since the releases team needs"},{"line_number":22,"context_line":"to know by milestone two what projects will be in the release, this means that"},{"line_number":23,"context_line":"projects will be required to be compatible with SQLAlchemy 2.0 by milestone"},{"line_number":24,"context_line":"two of the 2024.1 release."}],"source_content_type":"text/x-rst","patch_set":2,"id":"d09a3d6c_1cb50562","line":21,"range":{"start_line":21,"start_character":60,"end_line":21,"end_character":68},"updated":"2023-06-27 18:21:35.000000000","message":"\"release team\"? Too many plurals sound kinda weird here.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"76b59039b88e5777a60b9b86926b3ff3aca08fa7","unresolved":true,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"These facts lead to an unfortunate result: any project that is unable to"},{"line_number":20,"context_line":"ensure compatability for SQLAlchemy 2.0 for the 2024.1 release will be unable"},{"line_number":21,"context_line":"to be released and will be marked inactive [0]_ . Since the releases team needs"},{"line_number":22,"context_line":"to know by milestone two what projects will be in the release, this means that"},{"line_number":23,"context_line":"projects will be required to be compatible with SQLAlchemy 2.0 by milestone"},{"line_number":24,"context_line":"two of the 2024.1 release."}],"source_content_type":"text/x-rst","patch_set":2,"id":"2497ff0f_96cb2ef8","line":21,"range":{"start_line":21,"start_character":27,"end_line":21,"end_character":42},"updated":"2023-06-27 18:21:35.000000000","message":"I think we need to work towards getting everyone on 2.0 and not set a deadline after which they\u0027re penalized. After all, it\u0027s something external changing on them and not the other way around.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"8f1307f178535f6677e9024ceb89c3764d52d341","unresolved":true,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"These facts lead to an unfortunate result: any project that is unable to"},{"line_number":20,"context_line":"ensure compatability for SQLAlchemy 2.0 for the 2024.1 release will be unable"},{"line_number":21,"context_line":"to be released and will be marked inactive [0]_ . Since the releases team needs"},{"line_number":22,"context_line":"to know by milestone two what projects will be in the release, this means that"},{"line_number":23,"context_line":"projects will be required to be compatible with SQLAlchemy 2.0 by milestone"},{"line_number":24,"context_line":"two of the 2024.1 release."}],"source_content_type":"text/x-rst","patch_set":2,"id":"b58be3a3_09432dfc","line":21,"range":{"start_line":21,"start_character":27,"end_line":21,"end_character":42},"in_reply_to":"2497ff0f_96cb2ef8","updated":"2023-06-28 07:24:33.000000000","message":"I\u0027m not sure if we can wait \"forever\" for that as distros like Ubuntu/Debian/Centos will move to SQLAlchemy 2.0 sooner or later and just need to be ready for that.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"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":"e89a087e037421718c0881b88bbf74acecf85c72","unresolved":true,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"These facts lead to an unfortunate result: any project that is unable to"},{"line_number":20,"context_line":"ensure compatability for SQLAlchemy 2.0 for the 2024.1 release will be unable"},{"line_number":21,"context_line":"to be released and will be marked inactive [0]_ . Since the releases team needs"},{"line_number":22,"context_line":"to know by milestone two what projects will be in the release, this means that"},{"line_number":23,"context_line":"projects will be required to be compatible with SQLAlchemy 2.0 by milestone"},{"line_number":24,"context_line":"two of the 2024.1 release."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ef5b4b84_f5002e07","line":21,"range":{"start_line":21,"start_character":27,"end_line":21,"end_character":42},"in_reply_to":"b58be3a3_09432dfc","updated":"2023-06-28 18:28:36.000000000","message":"\u003d\u003dSlawek\n\nIt\u0027s my understanding from the discussion at the forum that we can\u0027t wait too much longer if we want OpenStack to remain distro-installable.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"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":"ae6732f659a7a9e785f7529fa7dda3fe17e508c6","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"These facts lead to an unfortunate result: any project that is unable to"},{"line_number":20,"context_line":"ensure compatability for SQLAlchemy 2.0 for the 2024.1 release will be unable"},{"line_number":21,"context_line":"to be released and will be marked inactive [0]_ . Since the releases team needs"},{"line_number":22,"context_line":"to know by milestone two what projects will be in the release, this means that"},{"line_number":23,"context_line":"projects will be required to be compatible with SQLAlchemy 2.0 by milestone"},{"line_number":24,"context_line":"two of the 2024.1 release."}],"source_content_type":"text/x-rst","patch_set":2,"id":"dfd5985e_ef236bd0","line":21,"range":{"start_line":21,"start_character":60,"end_line":21,"end_character":68},"in_reply_to":"d09a3d6c_1cb50562","updated":"2023-07-11 13:00:59.000000000","message":"Ack","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"76b59039b88e5777a60b9b86926b3ff3aca08fa7","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5655e3f4_f8e357ca","line":39,"updated":"2023-06-27 18:21:35.000000000","message":"I dunno how doable this deadline is, but I\u0027d want to hear an analysis of that before we lay down this gauntlet, personally. In the past when we had big conversions like this, we started with a goal and then treated the hard cutoff as a last resort, which should probably line up with projects that need retirement for this and other reasons.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"6b4a907cb79352aea06e1873774b7dd066225f5d","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"888dffb2_cb49879e","line":39,"in_reply_to":"090f82bc_32c33dc7","updated":"2023-07-12 16:38:05.000000000","message":"I think this patch and the debate here represents the discussions well.\n\nI understand at some point we need all things we release to support SQLA2.0. Given distro choices, sounds like the time is this cycle.\n\nI am making this assumption, not fully researching the details, and that we don’t want half of OpenStack projects not being co-installable with Nova and Ironic. (Yes that is a narrow view, but it’s my specific need, granted I am also within a venv in a per service container, but I want to use supported SQL libs!).\n\nMy take, if we can’t release a project, it’s inactive.\n\nI am assuming creating a release, having fixed tests, means you are not inactive any more? as in it easy to reverse things.\n\nMaybe we should also mark such projects as being on an independent release cycle, assuming they state what supported version of the coordinated release they are tested with? Maybe we apply that at the same time as inactive? Or maybe we add something new like unable-to-release or project-needs-help?\n\nFWIW being honest about project health could help revitalise important projects that get forgotten. Not telling operators creating a cloud there is no hope for a new release of a project they just deployed, seems much worse than asking for help by marking a project as inactive/“needs help” or otherwise. I see this as vital help rather than a threat but maybe that is me being British. Not sure what words we can use so this seems non-threatening globally.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"6684580a61e336af4a420ef4b2684a36914600b2","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"090f82bc_32c33dc7","line":39,"in_reply_to":"11aad1e0_9a9cf90f","updated":"2023-07-11 17:32:02.000000000","message":"We\u0027ve previously had hard deadlines that didn\u0027t get met. We renewed them and they still weren\u0027t met. Some are *still* unmet, and OSC is a good example. That\u0027s why I don\u0027t think threats will work.\n\nThe important part is the messaging, IMHO, to make sure people know the stuff is required. The critical parts of a base devstack install are probably going to be okay (i.e. keystone, neutron, glance, cinder, nova) and the people that don\u0027t meet the timeline of us moving to a SQLA-2.0-only test platform will likely only be impacting themselves. That\u0027s why I don\u0027t think we *need* threats.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"a0ac62156c42c775871d1d3236f830d136c51c6a","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"96afa8b7_2e4ca7c7","line":39,"in_reply_to":"4917a1b4_55aa7fcd","updated":"2023-07-11 15:24:31.000000000","message":"This discussion during the TC + Community leaders is captured in this etherpad https://etherpad.opendev.org/p/tc-leaders-interaction-2023-vancouver\n\nThis strongly aligns with what was discussed and agreed at the forum session including writing a resolution for project retirement, and timelines as defined here that are imposed by the SLURP cadence.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b3a7cea71584f772418758774726d04d15c96fc4","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7f5b4c4f_2fc95be7","line":39,"in_reply_to":"5655e3f4_f8e357ca","updated":"2023-06-27 18:54:43.000000000","message":"Yeah, we have many such integrated work which did not finish on time due to various reason and we did not take the strict action like this.\n\nAs I mentioned in my earlier comment also (if it was not clear in my ealry comment), let\u0027s keep this resolution ( or maybe we can define it as goal) for *migration plan* only and leave the project deprecation/inactive action to our existing process only. If any project gate is broken and things not merging there due to this migration or other reason they will anyways will fall in inactive project list.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"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":"e89a087e037421718c0881b88bbf74acecf85c72","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"effcd83b_97073972","line":39,"in_reply_to":"6068ea8e_7a7a076b","updated":"2023-06-28 18:28:36.000000000","message":"Slawek understanding my intent here, I think -- which is if we can\u0027t release the project due to incompatabilities, these are the risks it undergoes per the other policy around inactivity. It all hinges on the timeline, and I\u0027m fairly sure due to the external nature of the sqlalchemy change, we cannot dictate when we complete this migration ourselves without placing openstack at risk of being uninstallable in some distributions.\n\nI think it\u0027s significantly more open to be direct about the consequences of not being able to be released up front, rather than expecting a PTL -- who, if impacted by this would obviously be short on time -- to go read cross references to all our policies.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"7b1a71afe0c6aa83959a8066ec0f10f00e3619b8","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"cf167424_d79126eb","line":39,"in_reply_to":"7f5b4c4f_2fc95be7","updated":"2023-06-27 19:06:07.000000000","message":"++","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"c6c93d6013e8056f16c250cd565c4f9b2cf419cd","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"b5b00bc1_d710fdce","line":39,"in_reply_to":"888dffb2_cb49879e","updated":"2023-07-12 16:54:06.000000000","message":"I agree on those but if any project does not do release, test failing, not merging the things will be moved to inactive project list as per the below process (we have done that in past and can do that irrespective of the SQLA2.0 work).\n- https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html\n\nAnd if we do not get all project doing this, it does not mean other project will not do that. They will finish (already finished the SQLA2.0 work by stephenfin) the work irrespective of what other less active project.\n\nMy main concern of saying \"project will become inactive\" if xyz work is not done will create the inconsistency in our process. Where we are choosing a specific work as criteria to make project inactive which can give wrong impressions that other community-level work are less important (for example, RBAC, OSC, unified limit, any future work) because TC will not make your project inactive if you do not finish those work.\n\nI am saying if any work not done by projects make them unreleasable, untested then we have existing process to handle it.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"c28df8ac0b82c1f4f895f58fce746b896cd3fec1","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"b22b90b6_fc52c6cc","line":39,"in_reply_to":"96afa8b7_2e4ca7c7","updated":"2023-07-11 16:32:58.000000000","message":"Let me clarify forurm discussion. I do not think we have agreed to retire project if this work is not done. This is a thing brought up and there were a few ok and a few no on this.\n\nMy main concern on retiring project on this work is can we do the same for other important work we want to do as OpenStack and cannot do in all projects? \n\n* Can we retire swift as they did not drop py27? \n* Can we retire glance if they do not move to OSC (now there is progress on this but take this as example) ?\n\nlet\u0027s keep one thing to focus here, \"define the deadline for migration and try best\". project failing gate, not merging things will definitly become inactive as per our project inactive process.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"d6ab230084f4fafa05c337049a708d584864e944","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"c0552780_c3116ff4","line":39,"in_reply_to":"b22b90b6_fc52c6cc","updated":"2023-07-11 16:46:56.000000000","message":"Those are completely valid points that we should consider on a case-by-case basis. - Swift not dropping py27: doesn\u0027t mean it doesn\u0027t support something that the rest of OpenStack and distros require.\n- Glance not moving to OSC: worth talking about in a separate discussion.\n\nI believe that there is not much value in a resolution that says \"we should try to do our best to migrate to sqlalchemy 2, there is no timeline or penalties, do your best\".","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"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":"61ee3014affc79e2fe4a78fd062bd8edb3e021c8","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"70f68928_6958c4a9","line":39,"in_reply_to":"b5b00bc1_d710fdce","updated":"2023-07-14 10:43:56.000000000","message":"\u003e FWIW being honest about project health could help revitalize important projects that get forgotten.\n\nThis is a better way of saying something I\u0027ve felt for a long time. Sometimes you have to shine a light on places of weakness, such as projects without enough contribution to keep up with regular maintenance, in order to motivate people relying on those projects to step up and help maintain them -- or, as I\u0027ve personally experienced, giving the developers who *want* to maintain them the ammunition to justify that to their employers.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6d56dc59c2322f6b2a4743b5235c04d41668d1a9","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"11aad1e0_9a9cf90f","line":39,"in_reply_to":"c0552780_c3116ff4","updated":"2023-07-11 17:00:10.000000000","message":"there is timeline which is I agree and that should be enough.\n\n\"penalties\" is not something we can force from TC. any active project delay/not doing this and we force retire them will create difficult situation.\n\nand for retirement and inactive project we already have the process and criteria defined already in TC. We should follow those process to retire projects and if any project not migrating to SQLAlchemy 2.0 and if it fall under the below critria like gate broken, things not merging then it will get retire as per already defined process.\n\nRetirement process: https://governance.openstack.org/tc/reference/dropping-projects.html\n\nIn active project process: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"8f1307f178535f6677e9024ceb89c3764d52d341","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"6068ea8e_7a7a076b","line":39,"in_reply_to":"cf167424_d79126eb","updated":"2023-06-28 07:24:33.000000000","message":"isn\u0027t exactly that written in this document already? If project will have broken gate at 2024.1 Milestone 2 then we will mark it as inactive and there will be no release of this project in 2024.1. Or am I missing something?","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"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":"34259ea54cd5bd45a2e349f311c7200d071794c2","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7fe86b5d_01712f3b","line":39,"in_reply_to":"efc8d7f9_71755ad1","updated":"2023-07-11 13:37:04.000000000","message":"\u003e This way, we are tightly coupling a required work with a project inactive which is not good\n\nYou said it yourself: required work.\n\nThis is not the TC requiring this work; it\u0027s the python ecosystem. This resolution serves as basically the minimum we can do to be good stewards of ensuring OpenStack will continue to work on newer distributions. It\u0027s sad that this change may end up exposing how understaffed some projects are -- but it\u0027s not a change that we have control to delay.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"3423715ed63c7ed73f08474df79d8321c1e22a99","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"4917a1b4_55aa7fcd","line":39,"in_reply_to":"efc8d7f9_71755ad1","updated":"2023-07-11 14:06:35.000000000","message":"Wasn\u0027t there a forum discussion on this topic? Wouldn\u0027t we want to codify that discussion in a non-ephemeral form? Did the group in that session reach the same conclusion as this resolution proposes? Does that not deserve to be recorded in some permanent form and weigh heavy on the TC as the community telling them the required direction?\n\nThere is a balance of simplicity which is required coupled with need to drive the community. So perhaps a way forward is to to shift the discussion, focus, and prioritization to reach a codified community consensus and a recommendation from the TC to the community which it governs.\n\nThe conflict in this thread ultimately seems to be carrot versus stick and the resulting outcome. That is not an *easy* discussion. There are valid points by everyone, but some form of consensus is required, even if it is partial. I would suggest a division of a question[0]. What, why, versus non-compliance outcome seems to be the appropriate point to divide at, at least to my perception.\n\n[0]: https://en.wikipedia.org/wiki/Division_of_a_question","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"ae406bca47a53e302a2cb4c1048a08f84f1f6fc7","unresolved":true,"context_lines":[{"line_number":36,"context_line":"      unable to pass tests running SQLAlchemy 2.0 will be proposed for"},{"line_number":37,"context_line":"      inactive [0]_ status."},{"line_number":38,"context_line":"    - Two weeks before milestone two of release 2024.1, any project still"},{"line_number":39,"context_line":"      incompataible will have their inactive [0]_ status approved."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":".. [0] https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html"}],"source_content_type":"text/x-rst","patch_set":2,"id":"efc8d7f9_71755ad1","line":39,"in_reply_to":"effcd83b_97073972","updated":"2023-06-28 18:52:57.000000000","message":"I do not deny on making the project inactive. I am saying let\u0027s not add that as one of the action if this migration is not done. This way, we are tightly coupling a required work with a project inactive which is not good. If we want to do that, why we did not do that for uwsgi things, or can we do it for osc, rbac or other required work we want to do across all projects?\n\nIn this doc, let\u0027s target the migration plan/strategy only and let the existing process handle the inactive status per the criteria defined in our process doc. If we want to add some work to be a criteria to make project inactive then we should add that in our process doc not here.","commit_id":"d0f4df323bdc899391ac859cccc2f38ff470ac01"}]}