geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sai Boorlagadda <sai.boorlaga...@gmail.com>
Subject Re: [DISCUSS] Apache Geode 1.7.0 release branch created
Date Tue, 21 Aug 2018 22:54:10 GMT
If not late, I would also like to include GEODE-5594 (enabling hostname
verification)
and GEODE-5338 (using the default SSL context) into 1.7.0.

PRs for both are open and currently up for review.

On Tue, Aug 21, 2018 at 2:26 PM Dan Smith <dsmith@pivotal.io> wrote:

> I think we do want to wait for GEODE-5615 (DistributedTest OOMEs) and
> GEODE-5601 (AcceptanceTest port conflicts) to be fixed before cutting the
> new 1.7 branch. It would be better if we don't create a release branch from
> a point where we have these systematic issues with our pipeline.
>
> -Dan
>
> On Tue, Aug 21, 2018 at 12:48 PM, Nabarun Nag <nnag@apache.org> wrote:
>
> > I will wait for a day to give all developers sometime to commit any new
> > fixes into develop that is needed  in 1.7.0. Please do let me know if
> there
> > is any concern.
> >
> > Regards
> > Nabarun Nag
> >
> > On Tue, Aug 21, 2018 at 12:42 PM Nabarun Nag <nnag@apache.org> wrote:
> >
> > > Yeah , I can continue with the release manager tasks. My understanding
> > > from Dan's email is that every JIRA that was closed as 1.8 needs to be
> > > changed to 1.7 after we rebase develop over release/1.7 branch.
> > >
> > >
> > > Regards
> > > Nabarun Nag
> > >
> > >
> > > On Tue, Aug 21, 2018 at 11:57 AM Dan Smith <dsmith@pivotal.io> wrote:
> > >
> > >> +1 to updating the 1.7 branch.
> > >>
> > >> There is also a 1.8 version in JIRA, and I think a bunch of things are
> > >> marked as resolved in 1.8. So if you update the release branch you
> > should
> > >> probably update the fixed version on all these issues.
> > >>
> > >> -Dan
> > >>
> > >> On Tue, Aug 21, 2018 at 11:39 AM, Alexander Murmann <
> > amurmann@pivotal.io>
> > >> wrote:
> > >>
> > >> > Hi everyone!
> > >> >
> > >> >
> > >> > We cut this release branch 3 months ago and then the release got
> > >> stalled.
> > >> > Since then we’ve added another 432 commits to develop. We also have
> 83
> > >> > resolved Jira tickets marked as 1.8 and another 91 Jira tickets that
> > are
> > >> > labeled as 1.7, but were resolved after the 1.7 branch was cut 🙄.
> > >> >
> > >> >
> > >> > Given all the above, I am proposing to update the release/1.7.0
> branch
> > >> to
> > >> > include everything that’s currently on develop. What are everyone's
> > >> > thoughts on this?
> > >> >
> > >> >
> > >> > Nabarun, you previously volunteered to be the release manager for
> 1.7.
> > >> > Would you still be willing to fill that role if we decide to pick
> this
> > >> back
> > >> > up?
> > >> >
> > >> > On Wed, May 23, 2018 at 9:59 AM, Nabarun Nag <nnag@apache.org>
> wrote:
> > >> >
> > >> > > +1
> > >> > >
> > >> > > On Wed, May 23, 2018 at 9:29 AM Michael Stolz <mstolz@pivotal.io>
> > >> wrote:
> > >> > >
> > >> > > > +1
> > >> > > >
> > >> > > > --
> > >> > > > Mike Stolz
> > >> > > > Principal Engineer, GemFire Product Lead
> > >> > > > Mobile: +1-631-835-4771 <(631)%20835-4771>
> > >> > > > Download the GemFire book here.
> > >> > > > <
> > >> > > > https://content.pivotal.io/ebooks/scaling-data-services-
> > >> > > with-pivotal-gemfire
> > >> > > > >
> > >> > > >
> > >> > > > On Wed, May 23, 2018 at 12:24 PM, Barbara Pruijn <
> > >> bpruijn@pivotal.io>
> > >> > > > wrote:
> > >> > > >
> > >> > > > > +1
> > >> > > > >
> > >> > > > > > On May 23, 2018, at 8:33 AM, Joey McAllister <
> > >> > jmcallister@pivotal.io
> > >> > > >
> > >> > > > > wrote:
> > >> > > > > >
> > >> > > > > > +1 for including these. They are documentation-only
changes
> > that
> > >> > are
> > >> > > > > > applicable to 1.7.
> > >> > > > > >
> > >> > > > > > On Wed, May 23, 2018 at 8:24 AM Karen Miller <
> > >> kmiller@apache.org>
> > >> > > > wrote:
> > >> > > > > >
> > >> > > > > >> Geode devs,  I think that my merges of commits
for
> GEODE-5071
> > >> and
> > >> > > > > >> GEODE-5242 really
> > >> > > > > >> belong in Geode 1.7.  They just missed making
it in before
> > the
> > >> > > release
> > >> > > > > >> branch was cut.  I'm going to
> > >> > > > > >> cherry pick them into the 1.7 release branch.
 If anyone
> > >> disagrees
> > >> > > > with
> > >> > > > > >> this, let's discuss why, and we
> > >> > > > > >> can always revert the commits.  Thanks!
> > >> > > > > >>
> > >> > > > > >>
> > >> > > > > >> On Mon, May 21, 2018 at 4:39 PM, Nabarun Nag
<
> > nnag@apache.org>
> > >> > > wrote:
> > >> > > > > >>
> > >> > > > > >>> Hello Geode dev community,
> > >> > > > > >>>
> > >> > > > > >>> We have created a release branch for Apache
Geode 1.7.0 -
> > >> > > > > "release/1.7.0"
> > >> > > > > >>>
> > >> > > > > >>> Please do review and raise any issue with
the release
> > branch.
> > >> > > > > >>>
> > >> > > > > >>> If no concerns are raised we will start
with voting for
> > >> release
> > >> > > > > candidate
> > >> > > > > >>> within a week.
> > >> > > > > >>>
> > >> > > > > >>> Regards
> > >> > > > > >>> Nabarun Nag
> > >> > > > > >>>
> > >> > > > > >>
> > >> > > > >
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> >
>

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