Hello!
The requirements team is expecting the re-open the master branch
shortly after we create a stable/pike branch. This means that
cycle-training projects may (will?) start seeing bot generated
requirements syncs intended for queens. I tried to come up with an
automated way to block this and failed. This measn it's going to fall
on your teams to block all requirements updates you branch your repo's for pike.If you think a change is destined for pike feel free to reach out for clarification. Alos if you can think of a better way to handle this in 6 months we're all ears :) For the sake of completeness here's a list of repos[1] I expect you'll need to keep an eye on. openstack-ansible OpenStackAnsible openstack-ansible-apt_package_pinning OpenStackAnsible openstack-ansible-ceph_client OpenStackAnsible openstack-ansible-galera_client OpenStackAnsible openstack-ansible-galera_server OpenStackAnsible openstack-ansible-haproxy_server OpenStackAnsible openstack-ansible-lxc_container_create OpenStackAnsible openstack-ansible-lxc_hosts OpenStackAnsible openstack-ansible-memcached_server OpenStackAnsible openstack-ansible-openstack_hosts OpenStackAnsible openstack-ansible-openstack_openrc OpenStackAnsible openstack-ansible-ops OpenStackAnsible openstack-ansible-os_almanach OpenStackAnsible openstack-ansible-os_aodh OpenStackAnsible openstack-ansible-os_barbican OpenStackAnsible openstack-ansible-os_ceilometer OpenStackAnsible openstack-ansible-os_cinder OpenStackAnsible openstack-ansible-os_cloudkitty OpenStackAnsible openstack-ansible-os_designate OpenStackAnsible openstack-ansible-os_freezer OpenStackAnsible openstack-ansible-os_glance OpenStackAnsible openstack-ansible-os_gnocchi OpenStackAnsible openstack-ansible-os_heat OpenStackAnsible openstack-ansible-os_horizon OpenStackAnsible openstack-ansible-os_ironic OpenStackAnsible openstack-ansible-os_keystone OpenStackAnsible openstack-ansible-os_magnum OpenStackAnsible openstack-ansible-os_molteniron OpenStackAnsible openstack-ansible-os_monasca OpenStackAnsible openstack-ansible-os_monasca-agent OpenStackAnsible openstack-ansible-os_monasca-ui OpenStackAnsible openstack-ansible-os_neutron OpenStackAnsible openstack-ansible-os_nova OpenStackAnsible openstack-ansible-os_octavia OpenStackAnsible openstack-ansible-os_rally OpenStackAnsible openstack-ansible-os_sahara OpenStackAnsible openstack-ansible-os_searchlight OpenStackAnsible openstack-ansible-os_swift OpenStackAnsible openstack-ansible-os_tempest OpenStackAnsible openstack-ansible-os_trove OpenStackAnsible openstack-ansible-os_watcher OpenStackAnsible openstack-ansible-os_zaqar OpenStackAnsible openstack-ansible-pip_install OpenStackAnsible openstack-ansible-plugins OpenStackAnsible openstack-ansible-rabbitmq_server OpenStackAnsible openstack-ansible-repo_build OpenStackAnsible openstack-ansible-repo_server OpenStackAnsible openstack-ansible-rsyslog_client OpenStackAnsible openstack-ansible-rsyslog_server OpenStackAnsible openstack-ansible-specs OpenStackAnsible openstack-ansible-tests OpenStackAnsible kolla kolla kolla-ansible kolla kolla-kubernetes kolla diskimage-builder tripleo instack-undercloud tripleo os-apply-config tripleo os-collect-config tripleo os-refresh-config tripleo tripleo-common tripleo tripleo-heat-templates tripleo tripleo-validations tripleo Yours Tony. [1] It could be all .. I didn't check that ;P
signature.asc
Description: PGP signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
