[openstack-dev] [requirements][I18n][OpenStackClient][Quality Assurance][Security][Telemetry][ec2-api][heat][horizon][ironic][kuryr][magnum][manila][monasca][murano][neutron][octavia][senlin][solum][swift][tacker][tricircle][vitrage][watcher][winstackers][zun] Help needed
tony at bakeyournoodle.com
Thu Aug 10 05:46:32 UTC 2017
In an effort to qualify which projects are likley to be affected if
when we open the requirements repo I generated a list of all repos that:
1. Subscribe to requirements management
2. Do not already have a stable/pike branch
3. Do not follow the cycle-with-milestones, cycle-trailing or
independent release models
4. Are not a 'branchless' project (tempest or tempest-plugin)
These repos I believe *should* have a stable/pike branch or will see
problems when we open openstack/requirements. Those issues were
described in 
It turns out close to 1/3rd of projects that subscribe to requirements
management are not ready for us to re-open for master. So we need you
help to get that number down to a much more acceptable number.
The good news is it's pretty easy to fix this with the cool tools and
workflow in the releases repo. I suspect that the 'service' will
take care of themselves, and the horizon-plugins are waiting to horizon
to cut RC1.
Repos with type: horizon-plugin
Repos with type: other
patrole Quality Assurance
Repos with type: service
Those are the easy items.
The following repos don't seem to use the openstack/releases repo so I
have less information there.
It'd be great to get some of these repos represented in
openstack/releases. Having a confirmed release-model would go a long
way to clearing up the list. An alternate approach would be to remove
redundant items from projects.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: not available
More information about the OpenStack-dev