← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1285478] Re: Enforce alphabetical ordering in requirements file

 

** Also affects: marconi
   Importance: Undecided
       Status: New

** Changed in: marconi
       Status: New => In Progress

** Changed in: marconi
     Assignee: (unassigned) => Fengqian (fengqian-gao)

-- 
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 Cinder:
  In Progress
Status in OpenStack Image Registry and Delivery Service (Glance):
  In Progress
Status in Orchestration API (Heat):
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in Ironic (Bare Metal Provisioning):
  In Progress
Status in OpenStack Identity (Keystone):
  In Progress
Status in OpenStack Message Queuing Service (Marconi):
  In Progress
Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack Compute (Nova):
  In Progress
Status in Python client library for Cinder:
  New
Status in Python client library for Glance:
  New
Status in Python client library for heat:
  New
Status in Python client library for Ironic:
  In Progress
Status in Python client library for Neutron:
  New
Status in Python client library for Nova:
  In Progress
Status in Trove client binding:
  New
Status in OpenStack contribution dashboard:
  New
Status in Tempest:
  In Progress
Status in Trove - Database as a Service:
  In Progress
Status in Tuskar:
  In Progress

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/cinder/+bug/1285478/+subscriptions


References