-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
>> Date: 03/09/2016 01:24 PM
>> Subject: [openstack-dev] [nova] patches that improve code quality
>>
>> [...]
>>
>> And now, finally, I can get to the point of this e-mail. I'm relatively
>> new to this project, but I found no way to direct the (precious)
>> at
Radomir Dopieralski <openst...@sheep.art.pl> wrote on 03/09/2016 01:22:56
PM:
> From: Radomir Dopieralski <openst...@sheep.art.pl>
> To: openstack-dev@lists.openstack.org
> Date: 03/09/2016 01:24 PM
> Subject: [openstack-dev] [nova] patches that improve code quality
Ideally it's good practice to do refactoring the codes to add more
readability. In reality, it's kind of impossible.
Because there might be another process required after refactoring and
it would take a time.
But that's good point, honestly.
On Thu, Mar 10, 2016 at 1:33 AM, Matt Riedemann
On 3/9/2016 6:22 AM, Radomir Dopieralski wrote:
Some of the code we have in Nova is admittedly hard to read and brittle.
This is true even though we cave excellent code review,
and the reviewers that deeply care for the quality of code that is being
merged. Some of this code has been there
Some of the code we have in Nova is admittedly hard to read and brittle.
This is true even though we cave excellent code review,
and the reviewers that deeply care for the quality of code that is being
merged. Some of this code has been there always, some got that way as a
result of bug fixes
