Open Stack

Hi Miguel, all,

The initiative is very welcome and will help make it more efficient to 
develop in stadium projects.

legacy-tempest-dsvm-networking-bgpvpn-bagpipe would be a candidate, for 
networking-bgpvpn and networking-bagpipe (it covers API and scenario 
tests for the BGPVPN API (networking-bgpvpn) and given that 
networking-bagpipe is used as reference driver, it exercises a large 
portion of networking-bagpipe as well).

Having this one will help a lot.

Thanks,

-Thomas


On 9/30/18 2:42 AM, Miguel Lavalle wrote:
> Dear networking Stackers,
>
> During the recent PTG in Denver, we discussed measures to prevent 
> patches merged in the Neutron repo breaking Stadium and related 
> networking projects in general. We decided to implement the following:
>
> 1) For Stadium projects, we want to add non-voting jobs to the Neutron 
> check queue
> 2) For non stadium projects, we are inviting them to add 3rd party CI jobs
>
> The next step is for each project to propose the jobs that they want 
> to run against Neutron patches.
>
> Best regards
>
> Miguel
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.