)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"0f435241502bb639a51b7aea50908f0dbc8f5121","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"460b169d_e7458713","updated":"2021-10-26 14:36:03.000000000","message":"Hello,\n\nUsually we avoid backporting new features to stable branch, but these changes are well isolated and non-invasive.\n\nThe added requirements (bcrypt) is already supported its higher version [1].\nThese changes are already present in yoga and xena [2][3] (merged during xena so cherry-picked from xena).\n\n[1] https://opendev.org/openstack/requirements/src/branch/stable/wallaby/upper-constraints.txt#L209\n[2] https://review.opendev.org/c/openstack/oslo.middleware/+/802234\n[3] https://opendev.org/openstack/oslo.middleware/src/branch/master/oslo_middleware/basic_auth.py","commit_id":"c65e56a7af6de96f543be3d2abdee59f17e2ab98"},{"author":{"_account_id":8833,"name":"Rabi Mishra","email":"ramishra@redhat.com","username":"rabi"},"change_message_id":"4d3c3962aa33b8bccc049f093636a91699b31eb5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1afecae4_583ce3ff","updated":"2021-11-02 08:23:53.000000000","message":"Hey Herve!\n\nCan we merge this? I would appreciate any further help to expedite it:)","commit_id":"c65e56a7af6de96f543be3d2abdee59f17e2ab98"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"cdf13573021644c10406ad6f1703c6799ea91f8b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ad50f6df_c1e9b4eb","updated":"2021-11-04 11:50:46.000000000","message":"I don\u0027t know if this is backportable. It adds a new dependency to a stable release. That seems to go against stable policy.\n\nWould it make sense to do this in a downstream-only context?","commit_id":"c65e56a7af6de96f543be3d2abdee59f17e2ab98"},{"author":{"_account_id":8833,"name":"Rabi Mishra","email":"ramishra@redhat.com","username":"rabi"},"change_message_id":"d38bea914f91291682f11640d53a64f1e94a94f5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e69dcee3_31630a00","updated":"2021-10-26 03:07:06.000000000","message":"This is a non-invasive change and required for a feature originally proposed to Tripleo Wallaby. Hence we can probably make an exception here?","commit_id":"c65e56a7af6de96f543be3d2abdee59f17e2ab98"},{"author":{"_account_id":8833,"name":"Rabi Mishra","email":"ramishra@redhat.com","username":"rabi"},"change_message_id":"3e687bdd54860d68cedae81fc1651c29c1e35060","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"14477a04_6a6d722c","in_reply_to":"ad50f6df_c1e9b4eb","updated":"2021-11-08 06:43:24.000000000","message":"Sure, adding a new feature (which may need a new dependency) is not allowed as per stable policy. I thought we can do it as an exception as the feature and the dependency are non-invasive.\n\nHowever, if we don\u0027t want to merge this I\u0027m fine. The fact that TripleO is using an independent release model (no xena release) now would delay this further.\n\nDoing downstream only is not something easy to manage from TripleO pov and I would avoid it.","commit_id":"c65e56a7af6de96f543be3d2abdee59f17e2ab98"}]}