Open Stack

Sure, 100% agree with that statement.

I was just wondering if there could be some lead saying we are going to
work on technical debt now that all the compute code is relatively stable
and orchestration, no-db-compute (and others) are in that boat where it'd
be great to have a lot of people working on it and making sure its right
instead of a select few trying to fix it while others continue with there
daily business. 

Maybe that is not a reachable goal, but a thought at least for discussion
(and it seems like there will always be a continually build-up of
technical debt every few releases that should be fixed, ie every X out of
Y release is a technical debt cleanup release, ie no new features).

On 11/13/12 2:04 PM, "Russell Bryant" <rbryant at redhat.com> wrote:

>On 11/13/2012 04:59 PM, Joshua Harlow wrote:
>> Why not just go to the end goal immediately.
>> 
>> Or do u think that¹s not possible?
>
>It's possible.  It's just not very practical.
>
>We're working in some code that sees a *lot* of changes.  Just as a data
>point ... nova/compute/* has seen 840 commits in the last year.
>
>It would be incredibly painful to try to do a huge change in that code
>all at once.  This approach is mostly about trying to lay out very small
>easily merge-able steps that get us headed in the direction we want to
>go while not stepping on other work happening in the nova/compute/ code.
>
>-- 
>Russell Bryant