geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Murmann <amurm...@pivotal.io>
Subject Re: [DISCUSS] and the NEW Apache Geode 1.7.0 release branch has been created
Date Wed, 12 Sep 2018 17:11:18 GMT
Hi everyone,

It seems like that PR doesn't address the missing SHA issue either and I am
not aware of any proposals to properly fix this. How viable is it to revert
the relevant Gradle build changes on support/1.7?
We could continue make the new Gradle approach work with our release
process on develop and hopefully release 1.8 with these changes.

Are there any other proposals to unblock this?

On Tue, Sep 11, 2018 at 5:41 PM, Anthony Baker <abaker@pivotal.io> wrote:

> Slight clarification—the issue I mentioned is when a user builds Geode
> from the source distribution.  The source distribution that the release
> manager creates has the correct .buildinfo file, it’s just ignored by the
> build.  In short, the release manager can’t work around the problem.
>
> Does [1] help with this?
>
> Anthony
>
> [1] https://github.com/apache/geode/pull/2457 <https://github.com/apache/
> geode/pull/2457>
>
>
> > On Sep 11, 2018, at 3:16 PM, Alexander Murmann <amurmann@pivotal.io>
> wrote:
> >
> > What's the consensus on the version info issue Anthony is calling out?
> Does
> > anyone have a proposal for fixing this for this release? Should Nabarun
> as
> > the release manager manually correct this for the release and we find a
> > permanent solution for 1.8?
> >
> > On Mon, Sep 10, 2018 at 12:33 PM, Anthony Baker <abaker@pivotal.io>
> wrote:
> >
> >> Unfortunately it would require a fix to the build—it’s not about
> producing
> >> the release candidate. It’s when a user builds from the source release
> that
> >> the version info is ignored.
> >>
> >> Anthony
> >>
> >>> On Sep 10, 2018, at 10:02 AM, Nabarun Nag <nnag@apache.org> wrote:
> >>>
> >>> Hello Anthony,
> >>>
> >>> I plan to do that while creating the release candidate. If there are no
> >>> concerns raised on the release branch, I will start with the process
> >> soon.
> >>>
> >>> Regards
> >>> Nabarun Nag
> >>>
> >>>> On Mon, Sep 10, 2018 at 8:51 AM Anthony Baker <abaker@pivotal.io>
> >> wrote:
> >>>>
> >>>> Looks good Naba!  Only thing I see right now is that building from the
> >>>> source distribution does not use the .buildinfo file, leaving the
> >> version
> >>>> string empty.
> >>>>
> >>>> Anthony
> >>>>
> >>>>
> >>>>> On Sep 7, 2018, at 9:15 AM, Nabarun Nag <nnag@apache.org>
wrote:
> >>>>>
> >>>>> CORRECTION: if '*no*' concerns are raised, we will start with the
> >> voting
> >>>>> for the release candidate soon.
> >>>>>
> >>>>> Regrads
> >>>>> Nabarun Nag
> >>>>>
> >>>>>> On Fri, Sep 7, 2018 at 9:08 AM Nabarun Nag <nnag@pivotal.io>
wrote:
> >>>>>>
> >>>>>> Hello Geode Dev Community,
> >>>>>>
> >>>>>> We have created a new release branch for Apache Geode 1.7.0
-
> >>>>>> "release/1.7.0"
> >>>>>>
> >>>>>> Previous branch was deleted and has been replaced with a fresh
one.
> >>>>>>
> >>>>>> Please do review and raise any concern with the release branch.
> >>>>>>
> >>>>>> If concerns are raised, we will start with the voting for the
> release
> >>>>>> candidate soon.
> >>>>>>
> >>>>>> Regards
> >>>>>> Nabarun Nag
> >>>>>>
> >>>>
> >>>> --
> >>> Regards
> >>> Nabarun Nag
> >>
>
>

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