Agreed. There's no point in a branch if we aren't committing new features
to trunk, and I don't think we should yet.
On Thu, Aug 29, 2019 at 3:50 PM Dinesh Joshi wrote:
> We should not branch trunk at least until the RC is out.
>
> Dinesh
>
> > On Aug 29, 2019, at 3:32 PM, Sankalp Kohli
> wrote
We should not branch trunk at least until the RC is out.
Dinesh
> On Aug 29, 2019, at 3:32 PM, Sankalp Kohli wrote:
>
> I do not think we should branch and is -1 on it. The reason we have trunk
> frozen was for our focus to be on 4.0. I think we still need that focus till
> a few more release
I do not think we should branch and is -1 on it. The reason we have trunk
frozen was for our focus to be on 4.0. I think we still need that focus till a
few more releases like these.
> On Aug 30, 2019, at 12:24 AM, Nate McCall wrote:
>
> On Fri, Aug 30, 2019 at 10:11 AM Benedict Elliott Smit
On Fri, Aug 30, 2019 at 10:11 AM Benedict Elliott Smith
wrote:
>
> Seems to make sense to branch, right?
>
> Feels like a good line in the sand. +1
Seems to make sense to branch, right?
On Thu, Aug 29, 2019 at 11:10 PM +0100, "sankalp kohli"
wrote:
Will we cut alpha1 and later alpha releases from trunk or create a new
branch?
On Friday, August 30, 2019, Nate McCall
Will we cut alpha1 and later alpha releases from trunk or create a new
branch?
On Friday, August 30, 2019, Nate McCall wrote:
> >
> >
> > I think the next decision is should we just cut 4.0-alpha1 now given
> > that Michael has some cycles regardless of the known issues and start
> > using th
>
>
> I think the next decision is should we just cut 4.0-alpha1 now given
> that Michael has some cycles regardless of the known issues and start
> using the new fix versions for the 4.0-alpha2 release? I personally
> feel we should cut 4.0-alpha1 with every imaginable "expect this
> release to br
We hashed this out a bit in slack and I think the current rough
consensus (please speak up if you don't agree) is that we update our
release guidelines [1] to allow API changes between alpha and beta as
the common artifact is useful for testing and we will probably end up
finding API breakage while
