Re: [PROPOSAL] branch on first RC and open up master for features

As far as I remember only 4.4 and the commercial 3.x series were releases that way. On 09/05/17 08:25, "Erik Weber" wrote: On Mon, May 8, 2017 at 10:40 AM, Daan Hoogland wrote: > LS, > > In a lot of occasions, we have seen

Re: [PROPOSAL] branch on first RC and open up master for features

On Mon, May 8, 2017 at 10:40 AM, Daan Hoogland wrote: > LS, > > In a lot of occasions, we have seen new features that are waiting for > releases with blocker bugs and while these bugs certainly must be solved, > users that are not hindered by those bugs directly are

Re: Re: [PROPOSAL] branch on first RC and open up master for features

Thank you for getting this through your lab too Haijiao. :) *Will Stevens* CTO On Mon, May 8, 2017 at 10:50 PM, Haijiao <18602198...@163.com> wrote: > Hi, Rajani, Will and Community > > > Yes, we just finished the test in our lab. We confirmed the latest PR > 2062#

Re: [PROPOSAL] branch on first RC and open up master for features

Yes. That's the only blocker. Once it's merged, I will create rc2 ~Rajani Sent from phone. On 8 May 2017 7:24 p.m., "Simon Weller" wrote: > The only PR that is currently showing in blocker status is : > https://github.com/apache/cloudstack/pull/2062 > > Are there others that

Re: [PROPOSAL] branch on first RC and open up master for features

It's waiting on test update from haijiao ~Rajani Sent from phone. On 8 May 2017 8:05 p.m., "Will Stevens" wrote: > https://github.com/apache/cloudstack/pull/2062 should be ready to merge, I > think I had that one ready a couple weeks ago. > > *Will Stevens* > CTO > >

Re: [PROPOSAL] branch on first RC and open up master for features

All the PRs are tagged with milestone 4.10.0.0 and label Blocker ~Rajani Sent from phone. On 8 May 2017 5:14 p.m., "Rohit Yadav" wrote: > Rajani, > > > Can we have a list of outstanding blockers/issues? > > > I also saw some enhancement PRs merged, which I think we

Re: [PROPOSAL] branch on first RC and open up master for features

https://github.com/apache/cloudstack/pull/2062 should be ready to merge, I think I had that one ready a couple weeks ago. *Will Stevens* CTO On Mon, May 8, 2017 at 9:53 AM, Simon Weller wrote: > The only PR that is currently showing in blocker status

Re: [PROPOSAL] branch on first RC and open up master for features

The only PR that is currently showing in blocker status is : https://github.com/apache/cloudstack/pull/2062 Are there others that should be tagged? - Si From: Rohit Yadav Sent: Monday, May 8, 2017 6:43 AM To:

Re: [PROPOSAL] branch on first RC and open up master for features

Rajani, Can we have a list of outstanding blockers/issues? I also saw some enhancement PRs merged, which I think we should be avoiding and instead have our resources spent on fixing the release blockers, thanks. Regards. From: Rajani Karuturi

Re: [PROPOSAL] branch on first RC and open up master for features

I am +1 Even though git is distributed, the github workflow (PRs) has some scale limitations. Having a lots of small PRs can lead into a maintenance hell for keeping them mergeable. One way around it is to either have a "next"-branch or branch of master. Either way, branching is required. Since

Re: [PROPOSAL] branch on first RC and open up master for features

But these two points of attention are not mutually exclusive, are they? On 08/05/17 12:50, "Rajani Karuturi" wrote: I disagree. The release process is taking long because we dont have enough people working on the release. Sometimes, even the blockers don't get

Re: [PROPOSAL] branch on first RC and open up master for features

I disagree. The release process is taking long because we dont have enough people working on the release. Sometimes, even the blockers don't get enough attention. There is no point in adding features on already broken/blocked master which is not releasable. "un-freezing" master for new features