geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Smith <dsm...@pivotal.io>
Subject Re: Ready for release candidate?
Date Wed, 06 Jan 2016 23:58:20 GMT
So to be clear, even though we are creating a release branch, nothing
should be checked in to develop that is not intended for the 1.0.0 release.
I'm fine with that. It does mean as we get close to 1.0.0 we will need to
"lock down" develop so we don't check things in that might break the 1.0.0
release. That seems slightly contrary to the way I thought git flow was
supposed to work.

-Dan

On Wed, Jan 6, 2016 at 3:41 PM, Jianxia Chen <jchen@pivotal.io> wrote:

> +1
>
> On Wed, Jan 6, 2016 at 3:38 PM, Anthony Baker <abaker@pivotal.io> wrote:
>
> > I was expecting we would always create release branches from develop.
> >
> >
> > > On Jan 6, 2016, at 3:35 PM, Dan Smith <dsmith@pivotal.io> wrote:
> > >
> > >>
> > >> I believe we are farther away from the actual '1.0.0' release, so it
> > does
> > >> not make sense to have the long standing release branch.
> > >>
> > >
> > > Maybe I'm confused about where the next alpha or beta branch will be
> > > created from. Are you thinking it will be created from the
> > > release-1.0.0-alpha branch, or the develop branch?
> > >
> > > -Dan
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message