Open Stack

On 23/10/13 17:33, Russell Bryant wrote:
> 
> 4) Blueprint Prioritization
> 
> I would like to do a better job of using priorities in Icehouse.  The
> priority field services a couple of purposes:
> 
>   - helps reviewers prioritize their time
> 
>   - helps set expectations for the submitter for how reviewing this
>     work stacks up against other things
> 
> In the last meeting we discussed an idea that I think is worth trying at
> least for icehouse-1 to see if we like it or not.  The idea is that
> *every* blueprint starts out at a Low priority, which means "best
> effort, but no promises".  For a blueprint to get prioritized higher, it
> should have 2 nova-core members signed up to review the resulting code.
> 

All of the mentioned seem like awesome ideas that I +1 wholeheartedly. A
comment on this point though.

I don't have the numbers but I have a feeling that what happened in
Havana was that a lot of blueprints slipped until the time for feature
freeze. Reviewers thought it was a worthwile feature at that point (this
was, I feel, when *actual* blueprint reviews are done - whatever the
process says. It's natural too - once the code is there so much more is
clear) and wanted to get it in - but it was late in the cycle so we
ended up accepting things that could have been done better.

It would be good to levarage the blueprint process to make people post
code as soon as possible IMHO. How about making posted code a pre-req
for core reviewers to sign up for them? Thoughts?

Thanks,

N.