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

2015-02-24 Thread Russell Bryant
On 02/24/2015 12:54 PM, Daniel P. Berrange wrote: > On Tue, Feb 24, 2015 at 11:48:29AM +, 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 o

[openstack-dev] [cinder] Resuming of workflows/tasks

2015-02-24 Thread Dulko, Michal
Hi all, I was working on spec[1] and prototype[2] to make Cinder to be able to resume workflows in case of server or service failure. Problem of requests lost and resources left in unresolved states in case of failure was signaled at the Paris Summit[3]. What I was able to prototype was to res

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

2015-02-24 Thread Russell Bryant
On 02/24/2015 01:28 PM, Kashyap Chamarthy wrote: > On Tue, Feb 24, 2015 at 11:54:31AM +, Daniel P. Berrange wrote: >> On Tue, Feb 24, 2015 at 11:48:29AM +, 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 t

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

2015-02-24 Thread Kashyap Chamarthy
On Tue, Feb 24, 2015 at 11:54:31AM +, Daniel P. Berrange wrote: > On Tue, Feb 24, 2015 at 11:48:29AM +, 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 p

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

2015-02-24 Thread Daniel P. Berrange
On Tue, Feb 24, 2015 at 11:48:29AM +, 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

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

2015-02-24 Thread Chris Dent
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 r

Re: [openstack-dev] [stable][all] Revisiting the 6 month release cycle

2015-02-24 Thread Daniel P. Berrange
On Mon, Feb 23, 2015 at 04:14:36PM -0800, Joe Gordon wrote: > Was: > http://lists.openstack.org/pipermail/openstack-dev/2015-February/057578.html > > There has been frustration with our current 6 month development cadence. > This is an attempt to explain those frustrations and propose a very rough

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

2015-02-24 Thread Chris Dent
On Tue, 24 Feb 2015, Daniel P. Berrange wrote: I was writing this mail for the past few days, but the nova thread today prompted me to finish it off & send it :-) Thanks for doing this. I think you're probably right that the current release cycle has many negative impacts on the development pr

Re: [openstack-dev] [nova] Outcome of the nova FFE meeting for Kilo

2015-02-24 Thread Daniel P. Berrange
On Mon, Feb 23, 2015 at 03:24:01PM -0500, Jay Pipes wrote: > Here's another thought: is the big-bang integrated 6-month fixed release > cycle useful any more? Can we talk about using more of a moving train model > that doesn't have these long freeze cycles? At least for some of the > projects, I th

Re: [openstack-dev] [Murano] [QA] Automated tests for all Murano applications

2015-02-24 Thread Timur Nurlygayanov
Hi Boris, this idea is about the JSON files for each Murano application, which can be used in Murano functional tests or in Rally tests with Rally jobs for each commit to Murano engine and Murano applications repositories. I like the idea to configure Rally jobs for Murano repositories and then a

Re: [openstack-dev] [Glance] Core nominations.

2015-02-24 Thread Flavio Percoco
On 24/02/15 08:57 +0100, Flavio Percoco wrote: On 24/02/15 04:38 +, Nikhil Komawar wrote: Hi all, I would like to propose the following members to become part of the Glance core team: Ian Cordasco Louis Taylor Mike Fedosin Hemanth Makkapati Please, yes! Actually - I hope this doesn't c

Re: [openstack-dev] [nova] Outcome of the nova FFE meeting for Kilo

2015-02-24 Thread Duncan Thomas
Agreed. It causes two problems: 1) 9 month delays in getting code into a release 2) Some projects consider something to be breakable, from a back compatibility point of view, until it has made a formal release, which means anybody cutting releases from anything other than final/stable is facing th

Re: [openstack-dev] [Glance] Core nominations.

2015-02-24 Thread Flavio Percoco
On 24/02/15 04:38 +, Nikhil Komawar wrote: Hi all, I would like to propose the following members to become part of the Glance core team: Ian Cordasco Louis Taylor Mike Fedosin Hemanth Makkapati Please, yes! They have been contributing significant numbers of high quality reviews in the

<    1   2