On Thu, Aug 10, 2017 at 10:17:23AM -0400, Matthew Treinish wrote:
> On Thu, Aug 10, 2017 at 03:46:32PM +1000, Tony Breeds wrote:
> > 
> > Hi All,
> >     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 [1]
> > 
> > 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[2].  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
> > ironic-ui                                          ironic              
> > manila-ui                                          manila              
> > monasca-ui                                         monasca             
> > neutron-fwaas-dashboard                            neutron             
> > solum-dashboard                                    solum               
> > tacker-horizon                                     tacker              
> > watcher-dashboard                                  watcher             
> > zun-ui                                             zun                 
> > 
> > Repos with type: other
> > python-openstackclient                             OpenStackClient     
> > patrole                                            Quality Assurance
> 
> Fwiw, patrole is also a tempest plugin. [1] So it should also fall into the
> branchless category and you don't need to worry about it branching before
> unfreezing requirements.

\o/  I shall update my script and the tracking document.

Thanks.

Yours Tony.

Attachment: signature.asc
Description: PGP signature

__________________________________________________________________________
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

Reply via email to