Open Stack

Folks

I wanted to raise awareness about one of the things I captured while doing
reviews recently - we are sacrificing quality to bugfixing and feature
development velocity, essentially moving from one heap to another - from
bugs/features to 'tech-debt' bugs.

I understand that we all have deadlines and need to meet them. But, folks,
let's create the following policy:

1) do not introduce hacks/workarounds/kludges if it is possible.
2) while fixing things if you have a hack/workaround/kludge that you need
to work with - think of removing it instead of enhancing and extending it.
If it is possible - fix it. Do not let our technical debt grow.
3) if there is no way to avoid kludge addition/enhancing, if there is no
way to remove it - please, add a 'TODO/FIXME' line above it, so that we can
collect them in the future and fix them gradually.

I suggest to add this requirement into code-review policy.

What do you think about this?

-- 
Yours Faithfully,
Vladimir Kuklin,
Fuel Library Tech Lead,
Mirantis, Inc.
+7 (495) 640-49-04
+7 (926) 702-39-68
Skype kuklinvv
35bk3, Vorontsovskaya Str.
Moscow, Russia,
www.mirantis.com <http://www.mirantis.ru/>
www.mirantis.ru
vkuklin at mirantis.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151110/55fc4ca7/attachment.html>