[openstack-dev] [nova] patches that improve code quality
ed at leafe.com
Thu Mar 10 16:09:13 UTC 2016
-----BEGIN PGP SIGNED MESSAGE-----
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/
-----END PGP SIGNATURE-----
More information about the OpenStack-dev