yahoo-eng-team team mailing list archive

[Dolph Mathews <1285478@xxxxxxxxxxxxxxxxxx>]

See bug 1365061 instead.

** Changed in: blazar
       Status: Triaged => Invalid

** Changed in: glance
       Status: In Progress => Invalid

** Changed in: keystone
       Status: In Progress => Invalid

** Changed in: trove
       Status: In Progress => Invalid

** Changed in: python-cinderclient
       Status: In Progress => Invalid

** Changed in: python-glanceclient
       Status: In Progress => Invalid

** Changed in: python-troveclient
       Status: In Progress => Invalid

** Changed in: storyboard
       Status: In Progress => Invalid

** Changed in: tempest
       Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1285478

Title:
  Enforce alphabetical ordering in requirements file

Status in Blazar:
  Invalid
Status in Cinder:
  Invalid
Status in OpenStack Image Registry and Delivery Service (Glance):
  Invalid
Status in Orchestration API (Heat):
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in OpenStack Bare Metal Provisioning Service (Ironic):
  Won't Fix
Status in OpenStack Identity (Keystone):
  Invalid
Status in OpenStack Neutron (virtual network service):
  Invalid
Status in Python client library for Cinder:
  Invalid
Status in Python client library for Glance:
  Invalid
Status in Python client library for Ironic:
  Fix Committed
Status in Python client library for Neutron:
  Invalid
Status in Trove client binding:
  Invalid
Status in OpenStack contribution dashboard:
  Fix Released
Status in Storyboard database creator:
  Invalid
Status in Tempest:
  Invalid
Status in Openstack Database (Trove):
  Invalid
Status in Tuskar:
  Fix Released
Status in OpenStack Messaging and Notifications Service (Zaqar):
  Won't Fix

Bug description:
  
  Sorting requirement files in alphabetical order makes code more readable, and can check whether specific library
  in the requirement files easily. Hacking donesn't check *.txt files.
  We had  enforced  this check in oslo-incubator https://review.openstack.org/#/c/66090/.

  This bug is used to track syncing the check gating.

  How to sync this to other projects:

  1.  Copy  tools/requirements_style_check.sh  to project/tools.

  2. run tools/requirements_style_check.sh  requirements.txt test-
  requirements.txt

  3. fix the violations

To manage notifications about this bug go to:
https://bugs.launchpad.net/blazar/+bug/1285478/+subscriptions