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 bl
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
> 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
> > >
> > >
> > >
pache/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.ap
ere 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,
&
t; >
> >
> > - 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
ink 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: [PR
:
> 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] br
.
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
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
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 w
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
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 sho
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 relea
14 matches
Mail list logo
