Renat Akhmerov wrote: > [...] > So long story short, this change will affect your project only if you > use “mistral action-execution-list” CLI command because now this command > will be returning by default only 100 entries (to return all > “--limit=-1” needs to be passed).
A number of projects depend on python-mistralclient: openstack/python-tripleoclient [cycle-trailing] openstack/python-troveclient [cycle-with-intermediary] openstack/heat [cycle-with-milestones] openstack/mistral [cycle-with-milestones] openstack/murano [cycle-with-milestones] openstack/solum [cycle-with-intermediary] openstack/tacker [cycle-with-intermediary] openstack/instack-undercloud [cycle-with-intermediary] openstack/mistral-dashboard [None] openstack/openstackclient [None] openstack/python-openstackclient [cycle-with-intermediary] openstack/tripleo-common [cycle-trailing] However, I suspect none of those go through the CLI, so they likely won't be affected by the proposed change and could still depend on >=3.1.1 (therefore avoiding re-releases). Could you have a quick look at those and confirm that ? > We at Nokia need this fix released in Pike because we need to trigger > updates of RDO packages used in our system. Since this change affects behavior, it's better to do it before Pike release than after Pike release as a stable point update. So if my hunch on CLI usage above is right, then I would rather grant the library release freeze exception now. -- Thierry Carrez (ttx) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev