As we have started to move to a tempest plugin for our functional test suite, we have 2 choices about where it lives.
1 - In repo (as we have [0] currently) 2 - In a repo of its own (something like openstack/designate-tempest) There are several advantages to a separate repo: * It will force us to make API changes compatable * * This could cause us to be slower at merging changes [1] * It allows us to be branchless (like tempest is) * It can be its own installable package, and a (much) shorter list of requirements. If everyone is OK with a separate repo, I will go ahead and start the creation process. Thanks - Graham 0 - https://review.openstack.org/283511 1 - http://docs.openstack.org/developer/tempest/HACKING.html#branchless-tempest-considerations __________________________________________________________________________ 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
