openstack/sahara

Nikolay Starodubtsev 16b05b8b54 Take back upstream checks for import order

Import order checks was removed from upstream after discussion [1].
We want to save it in Sahara and we can do it because we support only
py2.7
NOTE: After moving to 3.x this checks should be removed/modified
[1]: http://lists.openstack.org/pipermail/openstack-dev/2014-December/052519.html

Change-Id: Ie26613c527c46bfd71ef58cb77219644d784f4c3
Closes-Bug: 1429089

2015-03-13 15:28:01 +03:00

742 B

Raw Blame History

Sahara Style Commandments

Step 1: Read the OpenStack Style Commandments http://docs.openstack.org/developer/hacking/
Step 2: Read on

Sahara Specific Commandments

Commit Messages

Using a common format for commit messages will help keep our git history readable. Follow these guidelines:

[S365] First, provide a brief summary of 50 characters or less. Summaries of greater then 72 characters will be rejected by the gate.
[S364] The first line of the commit message should provide an accurate description of the change, not just a reference to a bug or blueprint.

Imports

[S366, S367] Organize your imports according to the Import order