)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"7c6d4ab6fb4455e4a7438c89658028ce033ac3ef","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"0461f625_59642cf5","updated":"2021-10-26 00:07:07.000000000","message":"I believe we need the following steps:\n- 1. (already done) update global-requirements.txt to allow horizon to update requirements.txt to include Django 3.2. (Otherwise \n- 2. specify the required Django version which includes both 2.2 and 3.2 (at this point u-c uses 2.2)\n- 3. update upper-constraints.txt in the requirements repo to use Django 3.2\n- 4. bump the min version of Django in horizon\n- (optionally) update non-primary-django tests to include non-primary versions of Django. (it seems you drops 2.2 support together when we support 3.2, so perhaps this step is not the case though.)\n\nThe above is what I did in past when we bump the Django minimum version.\n\nHowever, https://review.opendev.org/c/openstack/horizon/+/811412 directly updated the min version of Django to 3.2. Skipping almost all tests is not recommended.","commit_id":"4ef292b0cde3f3c96a6b018ed5a5f71bf3d9fe39"},{"author":{"_account_id":29313,"name":"Vishal Manchanda","email":"manchandavishal143@gmail.com","username":"vishalmanchanda"},"change_message_id":"ff3dd1a6c1096cb0d185a6fd12194a1ad5a7c3f6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"25a9ab86_7315388d","updated":"2021-10-25 10:56:40.000000000","message":"already got two +2, self approving it to unblock the CI.","commit_id":"4ef292b0cde3f3c96a6b018ed5a5f71bf3d9fe39"}]}