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 <aba...@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 <n...@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 <aba...@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 <n...@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 <n...@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 >
