| *** yadnesh_ is now known as yadnesh | 04:30 | |
| *** tosky_ is now known as tosky | 12:23 | |
| tosky | hi, I have a question about the "bump an external library in stable branches", where, according the guidelines "we usually only update constraints for projects managed within the OpenStack community. Exceptions are made for other projects when there are gate issues. Those updates must be proposed by hand." | 12:23 |
|---|---|---|
| tosky | manila-tempest-plugin is going to bump ddt to 1.6.0 (last upstream), and like all tempest plugin, it can be used also for any version >=wallaby | 12:24 |
| tosky | now, you may say tempest needs to be installed in a venv, but some downstream consumers (hello RDO!) may try to use packages | 12:24 |
| tosky | and they usually prefer to keep the requirements in sync with requirements.txt | 12:25 |
| tosky | the other users of ddt are neutron-tempest-plugin, designate-tempest-plugin and cinderlib | 12:25 |
| tosky | as ddt only had non-API breaking changes between 1.4.1 (current u-c in wallaby) and 1.6.0, (mostly new methods and new optional parameters for a few methods), it should be low risk | 12:26 |
| tosky | but just wanted to check how such changes are handling nowadays, apart from what the documentation says | 12:26 |
| opendevreview | Stephen Finucane proposed openstack/requirements master: DNM: Validate fixes for oslo.db 12.1.0 support https://review.opendev.org/c/openstack/requirements/+/855973 | 17:01 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!