Hi all, I have a question regarding patrole and release management. Many projects like heat or murano have a tempest plugin within their repos, so by extension their tempest plugins have releases, as the projects change over time. However, since patrole is just a tempest plugin, yet heavily reliant on tempest, how should patrole do release management? Am I correct in thinking that it should, in the first place? With nova-network and other APIs slated for deprecation in Pike and beyond, Patrole will logically have to continuously be maintained to keep up, meaning that older tests, just like with Tempest, will have to be phased out. If Patrole, then, does not have releases, then older release-dependent tests and functionality will over time be lost.
Thank You, Felipe Monteiro
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
