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

2017-05-09 Thread Daan Hoogland 
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 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 stopped by them. Therefore, I 
propose we will fork on the first RC branches for future releases, so that 
development is not stopped for it. If the release process takes too long and to 
nice features get merged in between we can always decide to re-branch before 
releasing.


I might be misunderstanding, but isn't your proposal more or less how
we used to do releases back in the day?

-- 
Erik



daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

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

2017-05-09 Thread Erik Weber 
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 stopped by them. 
> Therefore, I propose we will fork on the first RC branches for future 
> releases, so that development is not stopped for it. If the release process 
> takes too long and to nice features get merged in between we can always 
> decide to re-branch before releasing.


I might be misunderstanding, but isn't your proposal more or less how
we used to do releases back in the day?

-- 
Erik

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

2017-05-08 Thread Will Stevens 
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# has fixed the known issues about VPN disconnection due to any network
> change including VPN account add/delete.
>
>
> I will update the result in PR 2062# and I think it can be merged now.
>
>
> Thanks for your effort,  good job !
>
>
>
>
> 在2017年05月09 10时04分, "Rajani Karuturi"写道:
>
> 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
> >
> > 
> >
> > On Mon, May 8, 2017 at 9:53 AM, 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 should be tagged?
> > >
> > >
> > > - Si
> > >
> > >
> > > 
> > > From: Rohit Yadav 
> > > Sent: Monday, May 8, 2017 6:43 AM
> > > To: dev@cloudstack.apache.org
> > > Subject: 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 
> > > Sent: 08 May 2017 16:20:01
> > > To: dev@cloudstack.apache.org
> > > Subject: 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 shouldn't be
> > > the goal in my opinion. We should move towards faster
> > > releases/release cycles.
> > >
> > > Thanks,
> > >
> > > ~ Rajani
> > >
> > > http://cloudplatform.accelerite.com/
> > >
> > > On May 8, 2017 at 2:11 PM, Daan Hoogland
> > > (daan.hoogl...@shapeblue.com) 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 stopped by them. Therefore, I propose we will
> > > fork on the first RC branches for future releases, so that
> > > development is not stopped for it. If the release process takes
> > > too long and to nice features get merged in between we can always
> > > decide to re-branch before releasing.
> > >
> > > Thoughts..?
> > > Daan
> > >
> > > daan.hoogl...@shapeblue.com
> > > www.shapeblue.com ( http://www.shapeblue.com
> )
> > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > > @shapeblue
> > >
> > > rohit.ya...@shapeblue.com
> > > www.shapeblue.com
> > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > > @shapeblue
> > >
> > >
> > >
> > >
> >
>

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

2017-05-08 Thread Rajani Karuturi 
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 should be tagged?
>
>
> - Si
>
>
> 
> From: Rohit Yadav 
> Sent: Monday, May 8, 2017 6:43 AM
> To: dev@cloudstack.apache.org
> Subject: 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 
> Sent: 08 May 2017 16:20:01
> To: dev@cloudstack.apache.org
> Subject: 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 shouldn't be
> the goal in my opinion. We should move towards faster
> releases/release cycles.
>
> Thanks,
>
> ~ Rajani
>
> http://cloudplatform.accelerite.com/
>
> On May 8, 2017 at 2:11 PM, Daan Hoogland
> (daan.hoogl...@shapeblue.com) 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 stopped by them. Therefore, I propose we will
> fork on the first RC branches for future releases, so that
> development is not stopped for it. If the release process takes
> too long and to nice features get merged in between we can always
> decide to re-branch before releasing.
>
> Thoughts..?
> Daan
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com ( http://www.shapeblue.com )
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

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

2017-05-08 Thread Rajani Karuturi 
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
>
> 
>
> On Mon, May 8, 2017 at 9:53 AM, 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 should be tagged?
> >
> >
> > - Si
> >
> >
> > 
> > From: Rohit Yadav 
> > Sent: Monday, May 8, 2017 6:43 AM
> > To: dev@cloudstack.apache.org
> > Subject: 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 
> > Sent: 08 May 2017 16:20:01
> > To: dev@cloudstack.apache.org
> > Subject: 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 shouldn't be
> > the goal in my opinion. We should move towards faster
> > releases/release cycles.
> >
> > Thanks,
> >
> > ~ Rajani
> >
> > http://cloudplatform.accelerite.com/
> >
> > On May 8, 2017 at 2:11 PM, Daan Hoogland
> > (daan.hoogl...@shapeblue.com) 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 stopped by them. Therefore, I propose we will
> > fork on the first RC branches for future releases, so that
> > development is not stopped for it. If the release process takes
> > too long and to nice features get merged in between we can always
> > decide to re-branch before releasing.
> >
> > Thoughts..?
> > Daan
> >
> > daan.hoogl...@shapeblue.com
> > www.shapeblue.com ( http://www.shapeblue.com )
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
>

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

2017-05-08 Thread Rajani Karuturi 
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 should be
> avoiding and instead have our resources spent on fixing the release
> blockers, thanks.
>
>
> Regards.
>
> 
> From: Rajani Karuturi 
> Sent: 08 May 2017 16:20:01
> To: dev@cloudstack.apache.org
> Subject: 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 shouldn't be
> the goal in my opinion. We should move towards faster
> releases/release cycles.
>
> Thanks,
>
> ~ Rajani
>
> http://cloudplatform.accelerite.com/
>
> On May 8, 2017 at 2:11 PM, Daan Hoogland
> (daan.hoogl...@shapeblue.com) 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 stopped by them. Therefore, I propose we will
> fork on the first RC branches for future releases, so that
> development is not stopped for it. If the release process takes
> too long and to nice features get merged in between we can always
> decide to re-branch before releasing.
>
> Thoughts..?
> Daan
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com ( http://www.shapeblue.com )
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

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

2017-05-08 Thread Will Stevens 
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 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: dev@cloudstack.apache.org
> Subject: 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 
> Sent: 08 May 2017 16:20:01
> To: dev@cloudstack.apache.org
> Subject: 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 shouldn't be
> the goal in my opinion. We should move towards faster
> releases/release cycles.
>
> Thanks,
>
> ~ Rajani
>
> http://cloudplatform.accelerite.com/
>
> On May 8, 2017 at 2:11 PM, Daan Hoogland
> (daan.hoogl...@shapeblue.com) 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 stopped by them. Therefore, I propose we will
> fork on the first RC branches for future releases, so that
> development is not stopped for it. If the release process takes
> too long and to nice features get merged in between we can always
> decide to re-branch before releasing.
>
> Thoughts..?
> Daan
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com ( http://www.shapeblue.com )
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

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

2017-05-08 Thread Simon Weller 
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: dev@cloudstack.apache.org
Subject: 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 
Sent: 08 May 2017 16:20:01
To: dev@cloudstack.apache.org
Subject: 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 shouldn't be
the goal in my opinion. We should move towards faster
releases/release cycles.

Thanks,

~ Rajani

http://cloudplatform.accelerite.com/

On May 8, 2017 at 2:11 PM, Daan Hoogland
(daan.hoogl...@shapeblue.com) 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 stopped by them. Therefore, I propose we will
fork on the first RC branches for future releases, so that
development is not stopped for it. If the release process takes
too long and to nice features get merged in between we can always
decide to re-branch before releasing.

Thoughts..?
Daan

daan.hoogl...@shapeblue.com
www.shapeblue.com ( http://www.shapeblue.com )
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue

rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

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

2017-05-08 Thread Rohit Yadav 
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 
Sent: 08 May 2017 16:20:01
To: dev@cloudstack.apache.org
Subject: 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 shouldn't be
the goal in my opinion. We should move towards faster
releases/release cycles.

Thanks,

~ Rajani

http://cloudplatform.accelerite.com/

On May 8, 2017 at 2:11 PM, Daan Hoogland
(daan.hoogl...@shapeblue.com) 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 stopped by them. Therefore, I propose we will
fork on the first RC branches for future releases, so that
development is not stopped for it. If the release process takes
too long and to nice features get merged in between we can always
decide to re-branch before releasing.

Thoughts..?
Daan

daan.hoogl...@shapeblue.com
www.shapeblue.com ( http://www.shapeblue.com )
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

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

2017-05-08 Thread Rene Moser 
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 we have a lot of integration
running on master, it is a far less expensive to branch of master
instead of having a "next" branch.

I would rather see devs working on bug fixing and features than merge
conflicts.

René

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

2017-05-08 Thread Daan Hoogland 
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 enough attention. There is no point in adding
features on already broken/blocked master which is not
releasable. "un-freezing" master for new features shouldn't be
the goal in my opinion. We should move towards faster
releases/release cycles.

Thanks,

~ Rajani

http://cloudplatform.accelerite.com/

On May 8, 2017 at 2:11 PM, Daan Hoogland
(daan.hoogl...@shapeblue.com) 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 stopped by them. Therefore, I propose we will
fork on the first RC branches for future releases, so that
development is not stopped for it. If the release process takes
too long and to nice features get merged in between we can always
decide to re-branch before releasing.

Thoughts..?
Daan

daan.hoogl...@shapeblue.com
www.shapeblue.com ( http://www.shapeblue.com )
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue


daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue

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

2017-05-08 Thread Rajani Karuturi 
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 shouldn't be
the goal in my opinion. We should move towards faster
releases/release cycles.

Thanks,

~ Rajani

http://cloudplatform.accelerite.com/

On May 8, 2017 at 2:11 PM, Daan Hoogland
(daan.hoogl...@shapeblue.com) 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 stopped by them. Therefore, I propose we will
fork on the first RC branches for future releases, so that
development is not stopped for it. If the release process takes
too long and to nice features get merged in between we can always
decide to re-branch before releasing.

Thoughts..?
Daan

daan.hoogl...@shapeblue.com
www.shapeblue.com ( http://www.shapeblue.com )
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue