)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":29313,"name":"Vishal Manchanda","email":"manchandavishal143@gmail.com","username":"vishalmanchanda"},"change_message_id":"e93729a93a7aa6440f7c0e8769563e289bcd4af3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"0c1260b6_48cda016","updated":"2021-10-22 09:26:19.000000000","message":"recheck.","commit_id":"81489de5baea4b0b5c7e7236a903118a85507361"},{"author":{"_account_id":29313,"name":"Vishal Manchanda","email":"manchandavishal143@gmail.com","username":"vishalmanchanda"},"change_message_id":"e03c68150cbb8ad04d75e48f81f17e61e166b3f0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"eb47797f_a34b9aa9","updated":"2021-10-25 13:18:02.000000000","message":"recheck","commit_id":"a18769597513cf1c17824b9c37a9aacd09846318"},{"author":{"_account_id":29313,"name":"Vishal Manchanda","email":"manchandavishal143@gmail.com","username":"vishalmanchanda"},"change_message_id":"06f783a3200cdc00c8b27b393629aeaafba831bd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"d5359a94_3cc12762","updated":"2021-10-25 15:53:19.000000000","message":"\u003e Patch Set 3:\n\u003e \n\u003e This will require a change in horizon to work with both django 2.2 and 3.2.\n\nI am wondering what else needs to be changed in the horizon, We have already bumped the Django\nversion in horizon https://review.opendev.org/c/openstack/horizon/+/811412","commit_id":"99a9ec6c2c94be49f87a306908e1721755c096c2"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"3790ff772abbd59ee818ea11c9944cb49df06567","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"d031c2ec_91c86e29","updated":"2021-10-26 13:26:42.000000000","message":"\u003e Patch Set 6:\n\u003e \n\u003e we uncapped django, this should happen in this order imo.\n\u003e \n\u003e 1. horizon updated to work with old and new versions of django (2.2/3.2 iirc)\n\u003e 1a. horizon as a lib is still used with plugins, running django 2\n\u003e 2. horizon released, supporting django 2 and 3\n\u003e 3. upper-constraints updated to use new horizon release\n\u003e 4. projects can set a minimum version of django 3 if they want (when using the horizon lib)\n\u003e 5. horizon plugins can use this release of horizon (as a lib) to migrate their support of django to version 3\n\u003e 6. horizon can drop support for django 2 and release a version (I\u0027d say a major version bump) noting this in their requirements.txt\n\u003e 7. upper-constraints can be updated again for the new horizon release\n\u003e 8. projects that use horizon as a lib will be forced to use the new django at this point.\n\nThanks for summarizing the story. This is same as my understanding.\nI was lazy enough when I post the last comment and did not write the full story.\nI plan to write a page in the horizon contributor doc so that such confusion does not happen in future.","commit_id":"41cd75c75bad10671b750cc5f206c65b7ab2559c"},{"author":{"_account_id":29313,"name":"Vishal Manchanda","email":"manchandavishal143@gmail.com","username":"vishalmanchanda"},"change_message_id":"21c8e7acc685fa251fd034e82d101d018e3eed6c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"07c98ca1_78483687","updated":"2021-10-25 18:02:36.000000000","message":"recheck.","commit_id":"41cd75c75bad10671b750cc5f206c65b7ab2559c"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"ba9cb83222143027ba12d69d2e02205a057392d8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"d90643eb_883b8f30","updated":"2021-10-26 01:07:50.000000000","message":"requirements-tox-py38-check-uc failure is valid. horizon is used as a library in horizon plugins, so horizon which accepts Django 3.2 needs to be released before updating upper-constraints.txt to Django 3.2. I believe this is the right step to bump the Django minimum version.","commit_id":"41cd75c75bad10671b750cc5f206c65b7ab2559c"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"145ae6bc3dabaf62243952cd4937babe714620ce","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":6,"id":"9cad4e62_b8745307","in_reply_to":"d90643eb_883b8f30","updated":"2021-10-26 01:24:19.000000000","message":"\u003e requirements-tox-py38-check-uc failure is valid. horizon is used as a library in horizon plugins, so horizon which accepts Django 3.2 needs to be released before updating upper-constraints.txt to Django 3.2. I believe this is the right step to bump the Django minimum version.\n\nor django version in u-c can be updated together with horizon update in u-c.","commit_id":"41cd75c75bad10671b750cc5f206c65b7ab2559c"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"298643ab7c42e8fd98b8c843c58902716c9f224a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"deee84f2_a09dec55","updated":"2021-11-14 09:08:33.000000000","message":"recheck unrelated neutron job timeout","commit_id":"e1975758936a2936a3a78a0e278ec903257b3a65"}]}