Re: [DISCUSS] where to begin the process for Apache CloudStack 4.0.0

2012-06-03 Thread John Kinsella
On Jun 2, 2012, at 3:38 PM, David Nalley wrote: > I think the consensus thus far has been to work in master - and > eventually branch when we get close to release (I am thinking perhaps > the RC timeframe). Feature development can continue moving forward via > topic branches that stay closed based

Re: [DISCUSS] where to begin the process for Apache CloudStack 4.0.0

2012-06-02 Thread David Nalley
On Sat, Jun 2, 2012 at 8:09 AM, Wido den Hollander wrote: > > > On 06/02/2012 02:22 AM, Kevin Kluge wrote: > > > Well, that's kind off a Citrix question. Is Citrix interested in > having a public branch to work in? From a community perspective it > woudl appear that only the ma

Re: [DISCUSS] where to begin the process for Apache CloudStack 4.0.0

2012-06-02 Thread Wido den Hollander
On 06/02/2012 02:22 AM, Kevin Kluge wrote: Well, that's kind off a Citrix question. Is Citrix interested in having a public branch to work in? From a community perspective it woudl appear that only the master branch is of interest plus any feature branches that are public. I don't get the Ci

RE: [DISCUSS] where to begin the process for Apache CloudStack 4.0.0

2012-06-01 Thread Kevin Kluge
> >> > >> Well, that's kind off a Citrix question. Is Citrix interested in > >> having a public branch to work in? From a community perspective it > >> woudl appear that only the master branch is of interest plus any > >> feature branches that are public. > > > > I don't get the Citrix question? >

Re: [DISCUSS] where to begin the process for Apache CloudStack 4.0.0

2012-06-01 Thread Robert Schweikert
On 06/01/2012 10:55 AM, Wido den Hollander wrote: Hi, On 06/01/2012 04:37 PM, Robert Schweikert wrote: On 05/31/2012 01:35 PM, David Nalley wrote: On Thu, May 31, 2012 at 8:15 AM, Robert Schweikert wrote: On 05/31/2012 12:35 AM, Kevin Kluge wrote: The master branch hasn't diverged much from

Re: [DISCUSS] where to begin the process for Apache CloudStack 4.0.0

2012-06-01 Thread Wido den Hollander
Hi, On 06/01/2012 04:37 PM, Robert Schweikert wrote: On 05/31/2012 01:35 PM, David Nalley wrote: On Thu, May 31, 2012 at 8:15 AM, Robert Schweikert wrote: On 05/31/2012 12:35 AM, Kevin Kluge wrote: The master branch hasn't diverged much from the 3.0.x branch at this point. I can't name any d

Re: [DISCUSS] where to begin the process for Apache CloudStack 4.0.0

2012-06-01 Thread Robert Schweikert
On 05/31/2012 01:35 PM, David Nalley wrote: On Thu, May 31, 2012 at 8:15 AM, Robert Schweikert wrote: On 05/31/2012 12:35 AM, Kevin Kluge wrote: The master branch hasn't diverged much from the 3.0.x branch at this point. I can't name any divergence off the top of my head. I would expect 3.0

Re: [DISCUSS] where to begin the process for Apache CloudStack 4.0.0

2012-05-31 Thread Mohammad Nour El-Din
Hi I agree that branching from a branch is not the way to go. But at the same time I agree with David that we need to follow the rule: - Release soon and release regularly also I agree with David that next release must focus more on cleaning the code or at least starting to clean the code The

Re: [DISCUSS] where to begin the process for Apache CloudStack 4.0.0

2012-05-31 Thread David Nalley
On Thu, May 31, 2012 at 8:15 AM, Robert Schweikert wrote: > On 05/31/2012 12:35 AM, Kevin Kluge wrote: >> >> The master branch hasn't diverged much from the 3.0.x branch at this >> point.  I can't name any divergence off the top of my head.  I would expect >> 3.0.x to be more stable, but if there

Re: [DISCUSS] where to begin the process for Apache CloudStack 4.0.0

2012-05-31 Thread Robert Schweikert
On 05/31/2012 12:35 AM, Kevin Kluge wrote: The master branch hasn't diverged much from the 3.0.x branch at this point. I can't name any divergence off the top of my head. I would expect 3.0.x to be more stable, but if there is another reason to go forth with master then I wouldn't stop that

RE: [DISCUSS] where to begin the process for Apache CloudStack 4.0.0

2012-05-30 Thread Kevin Kluge
The master branch hasn't diverged much from the 3.0.x branch at this point. I can't name any divergence off the top of my head. I would expect 3.0.x to be more stable, but if there is another reason to go forth with master then I wouldn't stop that for stability reasons. > New features going