I am running for PTL for Oslo for the Kilo release cycle.

I have served 2 terms now, and my tl;dr platform for Kilo is, “More of the 

I have already posted the retrospective the team put together for Juno [1], so 
I won’t go over those items in depth here. From my perspective, the team is 
working well together and made excellent progress with our goals for Juno. 
We’ve ironed out a lot of the kinks in the graduation process, and with those 
adjustments I think Kilo will go just as smoothly as Juno has, if not more.

My first priority for us is to finish the work on the libraries we graduated in 
Juno, including adoption, removing incubated code, adding documentation, and 
any of the other tasks we identify that we need to do before we can say we are 
“done”. I would like to focus on this for K1.

We started oslo.log and oslo.concurrency late in the cycle, so we have more 
work to do there than for some of the other libraries. I really count those as 
Kilo graduations, even though we did get them started in Juno. I think we can 
finish these for K1 as well.

Dims has already started working on the analysis for which modules are ready to 
come out next, and we should finish that relatively soon to give us time to 
plan things out for the summit. My impression is we have 3-4 more libraries 
ready to move out of the incubator for K2-K3. At that point, I think we will 
have handled most of the code that is ready for graduation. We will need to 
look at anything that remains, to decide how to handle it for the L release 

Graduation work was the focus of our attention for Juno, and I would give it a 
high priority during Kilo as well. However, we also need to bring bug triage 
and fixes back to the forefront, to make sure we take advantage of the new 
libraries to release fixes quickly to all of OpenStack, without waiting for 
projects to sync changes.

I hope these goals seem reasonable to everyone, and I look forward to working 
with all of you again this cycle.


OpenStack-dev mailing list

Reply via email to