[openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

Russell Bryant rbryant at redhat.com
Tue Feb 24 12:48:29 UTC 2015


On 02/24/2015 12:54 PM, Daniel P. Berrange wrote:
> On Tue, Feb 24, 2015 at 11:48:29AM +0000, Chris Dent wrote:
>> On Tue, 24 Feb 2015, Daniel P. Berrange wrote:
>>
>>> need to do more work. If this is so, then I don't think this is a blocker,
>>> it is just a sign that the project needs to focus on providing more resources
>>> to the teams impacted in that way.
>>
>> What are the mechanisms whereby the project provides more resources
>> to teams?
> 
> The technical committee and / or foundation board can highlight the need
> for investment of resources in critical areas of the project, to either
> the community members or vendors involved. As an example, this was done
> successfully recently to increase involvement in maintaining the EC2
> API support.  There are plenty of vendors involved in OpenStack which
> have the ability to target resources, if they can learn where those
> resources are best spent.

Indeed ... and if horizontal teams are the ones hit the most by the
extra work, each project should help with that burden.  For example,
projects may need to take their responsibility for documentation more
seriously and require documentation with features (content at least, not
necessarily integration into the proper documentation deliverables)
instead of assuming it magically gets written later.

-- 
Russell Bryant



More information about the OpenStack-dev mailing list