Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 03/10/2016 03:35 AM, Markus Zoeller wrote:

> Agreed, bug reports are *not* a way to document technical debt. 
> They should be used for documenting faulty behavior which can hit 
> downstream consumers.
> 
> I also have the feeling that refactorings get less attention than 
> bug fixes and features. Matt already pointed to the numbers of
> open reviews which compete for attention. One way to make those 
> refactoring patches more visible and queryable could be to use a 
> topic "refactoring" for them. Reviewers can then search for them if
> they decide to switch their focus to resolving technical debt.

I think a specless blueprint would cover most of these situations.
This would show that it is not a bug, but an implementation of a
feature, where the feature is "code that doesn't suck as much".

I would recommend identifying these areas and submitting code *early*
in the release cycle, where the impact of refactoring won't hold up a
release. At the end of the cycle there is just too much pressure to
get features in before the freeze that no one wants to make that
harder by merging code that might conflict with those changes.

- -- 

- -- Ed Leafe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJW4ZwoAAoJEKMgtcocwZqL8MwQAJKugI/FOFWCYptWnQbGI3t/
5bXnckt3w2FFU6jtdzRlQwDaKDUTGaEDyer0iuQi6OX1b/kpaDujymDFpP8kWNnn
ujIS5wOkX8tF3fYM58AxRgv3DENolShovFUpFvaa2jPnAl/ibORTTWY2oS9EH0z1
XJyOZt3O17cob3NqFj2Ao1NHD42v/LoJ1NjS3l6//EphJMUix5lRJUI9n00I+mCn
AFokz+JPRi2ePq6mGXf9MS4qCGGV+UZ7h1JxPmlIuJVZJ3/vypiWBwr+Rk6mWbHh
HDwFIGx6mynQvzNC1wOcMpk+n62arDEtW1y2kTcGhxYybr7kLQ+UkX8EaPfumfIB
QZ1IHktoJozNrywGbW7uqc74cFAMl+LPoe7BRAH7j/Lh7A6i5tJB5Vq6abQHSSXj
gvZPlIg08RBUQi1uKDz4Y4Ze1lhJtHOIpO93mD/V6mQjERjDMz3Wp6k34WHrI6zI
kH9OriJGCB3jauLrJiV/bQKBmWqFM2vEOEAcdbk1SdHVIrUMuE/wJNMahkzrNhsj
Z3fS+QwidgV81I3Wgsswcvn6yBN3i61kq6ThJ3ePrI+gImwCUcZmxi6cur1TAmN7
qM6OPnzwj0x2Zb85y+NW6VO9/PgDccbiFZg0WGvBcqi9Vk44QIZZL2eA6HVKc5Ik
qD4Am79IAkjONWC5Bqrh
=5r5T
-----END PGP SIGNATURE-----