Hi, As you might already know we are using the independent release which means that we can release whenever we want.
Like we discussed during the Tokyo summit our goal is to release a couple versions before the Mitaka release which should correspond to the 1.0 version. Every version will implement a new feature, or improve some part of the code, deprecating the old one. If we want to implement all the features we envisioned we'll need to release 0.5 version ASAP to focus on next features. Most of the code regarding 0.5 are pending review. The last goals are to integrate bugfixes and Gnocchi support before releasing first rc. I got positive feedbacks from people testing the gnocchi integration. Code only needs minor fixes and code review, people should start reviewing code as it's mostly finished and only a few minor parts are subject to changes. Some gerrits rights problems are being fixed so that we can release a 0.5 branch and start focusing on next version while RC is being tested. You can still send patch to review, but their integration will be postponed until we have a 0.5 branch. Any blueprint that has not yet been approved will not be part of the 0.5 release. Just a quick reminder that 0.6 will feature new collector and resources models. Which will help people needing multiple collector instances for different backends (for example multiple ceilometer backends). A compatibility layer will be added to support legacy code and data format. We're only a few steps away from releasing gnocchi support in CloudKitty. Let's focus and make it a success :) Cheers __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
