[RESULT] [VOTE] Apache Ambari 2.4.0 RC0

[Jayush Luniya]

Hello,
The voting process for Apache Ambari 2.4.0 RC0 has completed. The vote is in 
favor of releasing Apache Ambari 2.4.0 RC0.

The final votes are as follows:
8  +1  (6 PMCs, 1 committer, 1 other)
0  +0
0  -1

The following is a list of the votes:

Alejandro Fernandez (PMC) +1
Mahadev Konar (PMC) +1
Robert Nettleton (PMC) +1
Jonathan Hurley (PMC) +1
Nate Cole (PMC) +1
Jayush Luniya (PMC) +1
Mithun Mathew (Committer) +1
Venkat (Contributor) +1

I will begin the process of creating the release artifacts for Ambari-2.4.0 
based on RC0. Thanks to all who participated in the voting process.

Regards,
Jayush Luniya
Apache Ambari 2.4.0 Release Manager

Re: [VOTE] Apache Ambari 2.4.0 RC0

[Alejandro Fernandez]

+1, Apache Ambari 2.4.0 RC0 LGTM

Verification steps,

git clone --branch release-2.4.0-rc0
https://git-wip-us.apache.org/repos/asf/ambari.git
apache-ambari-2.4.0-src-mine
cd apache-ambari-2.4.0-src-mine
git clean -xdf
cd ambari-web
npm install
ulimit -n 2048
brunch build
rm -rf node_modules
mv public public-static
cd ../..
tar --exclude=.git --exclude=.gitignore --exclude=.gitattributes -zcvf
apache-ambari-2.4.0-src-mine.tar.gz apache-ambari-2.4.0-src-mine

# Verify signature,
gpg --verify apache-ambari-2.4.0-src.tar.gz.asc
apache-ambari-2.4.0-src.tar.gz

# Before doing build, make sure ratcheck passes
cp -R apache-ambari-2.4.0-src-mine apache-ambari-2.4.0-ratcheck
cd apache-ambari-2.4.0-ratcheck
mvn clean apache-rat:check


Thanks,
Alejandro Fernandez
Apache Ambari PMC


On 8/25/16, 2:50 PM, "Venkat"  wrote:

>+1
>
>On Wed, Aug 24, 2016 at 10:38 PM, Mithun Mathew 
>wrote:
>
>> Looks like the only choice is fixing it in the next release rather than
>> delaying the current release to fix it.
>> Something to be noted: We had 2+ months to fix a *critical* bug, but it
>> still remains open.
>>
>> Since I do not have complete context of the whole discussion, it would
>>be
>> great to see this bug fixed in the next release.
>> Shall resort to documenting this issue for the current release...
>>
>> Matt
>>
>>
>> On Wed, Aug 24, 2016 at 12:27 PM, Mahadev Konar
>>
>> wrote:
>>
>> > Mithun,
>> >
>> >  That¹s a good concern but on the Apache jira looks like we agreed to
>> move
>> > it out from 2.4.0. Ideally we should look at real blockers and any
>>issues
>> > with licenses/artifacts to vote for the release. User exp is a good
>>thing
>> > to look at ­ but we can look at fixing later?  Are you ok moving ahead
>> with
>> > this in a later release?
>> >
>> >
>> > Thanks
>> > mahadev
>> >
>> > On 8/24/16, 12:03 PM, "Mithun Mathew"  wrote:
>> >
>> > *-1*
>> >
>> > I was going through the task of adding HAWQ and PXF to stack HDP
>>2.4
>> > through the install cluster wizard, for documentation purposes.
>> >
>> > The experience with version definition has changed the experience
>> > compared
>> > to Ambari 2.2.2.
>> > The experience for users has become worse because custom
>>repositories
>> > do
>> > not show up on the UI like in Ambari 2.2.2. If I switch to default
>> > version
>> > definition, I see the custom repositories, but end up with old
>> HDP-2.4
>> > url
>> > links.
>> >
>> > I see a lot of potential for user errors from this page. I myself,
>> > ended up
>> > with a broken cluster stuck on the Install wizard page.
>> >
>> > I saw some conversation here
>> > https://issues.apache.org/jira/browse/AMBARI-17285
>> > I still cannot support release of a product which has user
>>experience
>> > worse
>> > than the older version.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Mon, Aug 22, 2016 at 12:45 PM, Jayush Luniya <
>> > jlun...@hortonworks.com>
>> > wrote:
>> >
>> > > Hello,
>> > >
>> > > I have created an apache-ambari-2.4.0 release candidate.
>> > >
>> > > GIT source tag (release-2.4.0-rc0)
>>https://git-wip-us.apache.org/
>> > > repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/
>> > release-2.4.0-rc0
>> > >
>> > > Staging site:
>>http://home.apache.org/~jluniya/apache-ambari-2.4.0-
>> > rc0/
>> > >
>> > > PGP release keys (signed using CD23CAAE> > > 11371/pks/lookup?op=get&search=0x4BC59EDACD23CAAE>)
>> > > http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=
>> > 0x4BC59EDACD23CAAE
>> > >
>> > > One can look into the issues fixed in this release at
>> > > https://issues.apache.org/jira/browse/AMBARI/
>> fixforversion/12334239/
>> > ?
>> > > selectedTab=com.atlassian.jira.jira-projects-plugin:
>> > version-summary-panel
>> > >
>> > > Vote will be open for 72 hours.
>> > > [ ] +1 approve
>> > > [ ] +0 no opinion
>> > > [ ] -1 disapprove (and reason why)
>> > >
>> > > Regards,
>> > > Jayush Luniya
>> > > Apache Ambari 2.4.0 Release Manager
>> > >
>> >
>> >
>> >
>> > --
>> > *Mithun Mathew* (Matt)
>> >
>> >- www.linkedin.com/in/mithunmatt/
>> >
>> >
>> >
>>
>>
>> --
>> *Mithun Mathew* (Matt)
>>
>>- www.linkedin.com/in/mithunmatt/
>>
>
>
>
>-- 
>Regards
>
>Venkat

Re: [VOTE] Apache Ambari 2.4.0 RC0

[Venkat]

+1

On Wed, Aug 24, 2016 at 10:38 PM, Mithun Mathew  wrote:

> Looks like the only choice is fixing it in the next release rather than
> delaying the current release to fix it.
> Something to be noted: We had 2+ months to fix a *critical* bug, but it
> still remains open.
>
> Since I do not have complete context of the whole discussion, it would be
> great to see this bug fixed in the next release.
> Shall resort to documenting this issue for the current release...
>
> Matt
>
>
> On Wed, Aug 24, 2016 at 12:27 PM, Mahadev Konar 
> wrote:
>
> > Mithun,
> >
> >  That’s a good concern but on the Apache jira looks like we agreed to
> move
> > it out from 2.4.0. Ideally we should look at real blockers and any issues
> > with licenses/artifacts to vote for the release. User exp is a good thing
> > to look at – but we can look at fixing later?  Are you ok moving ahead
> with
> > this in a later release?
> >
> >
> > Thanks
> > mahadev
> >
> > On 8/24/16, 12:03 PM, "Mithun Mathew"  wrote:
> >
> > *-1*
> >
> > I was going through the task of adding HAWQ and PXF to stack HDP 2.4
> > through the install cluster wizard, for documentation purposes.
> >
> > The experience with version definition has changed the experience
> > compared
> > to Ambari 2.2.2.
> > The experience for users has become worse because custom repositories
> > do
> > not show up on the UI like in Ambari 2.2.2. If I switch to default
> > version
> > definition, I see the custom repositories, but end up with old
> HDP-2.4
> > url
> > links.
> >
> > I see a lot of potential for user errors from this page. I myself,
> > ended up
> > with a broken cluster stuck on the Install wizard page.
> >
> > I saw some conversation here
> > https://issues.apache.org/jira/browse/AMBARI-17285
> > I still cannot support release of a product which has user experience
> > worse
> > than the older version.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Mon, Aug 22, 2016 at 12:45 PM, Jayush Luniya <
> > jlun...@hortonworks.com>
> > wrote:
> >
> > > Hello,
> > >
> > > I have created an apache-ambari-2.4.0 release candidate.
> > >
> > > GIT source tag (release-2.4.0-rc0) https://git-wip-us.apache.org/
> > > repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/
> > release-2.4.0-rc0
> > >
> > > Staging site: http://home.apache.org/~jluniya/apache-ambari-2.4.0-
> > rc0/
> > >
> > > PGP release keys (signed using CD23CAAE > > 11371/pks/lookup?op=get&search=0x4BC59EDACD23CAAE>)
> > > http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=
> > 0x4BC59EDACD23CAAE
> > >
> > > One can look into the issues fixed in this release at
> > > https://issues.apache.org/jira/browse/AMBARI/
> fixforversion/12334239/
> > ?
> > > selectedTab=com.atlassian.jira.jira-projects-plugin:
> > version-summary-panel
> > >
> > > Vote will be open for 72 hours.
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> > > Regards,
> > > Jayush Luniya
> > > Apache Ambari 2.4.0 Release Manager
> > >
> >
> >
> >
> > --
> > *Mithun Mathew* (Matt)
> >
> >- www.linkedin.com/in/mithunmatt/
> >
> >
> >
>
>
> --
> *Mithun Mathew* (Matt)
>
>- www.linkedin.com/in/mithunmatt/
>



-- 
Regards

Venkat

Re: [VOTE] Apache Ambari 2.4.0 RC0

[Mahadev Konar]

+1 for RC0.

On 8/25/16, 9:17 AM, "Robert Nettleton"  wrote:

+1 for RC0

I verified the signatures of the tarball download, and ran some basic diff 
checks against the src tree. 


> On Aug 25, 2016, at 11:01 AM, Jonathan Hurley  
wrote:
> 
> +1 for RC0 
> 
> Verified hashes, source files, and pom.xml to include 2.4.0.0.0
> 
>> On Aug 25, 2016, at 1:38 AM, Mithun Mathew  wrote:
>> 
>> Looks like the only choice is fixing it in the next release rather than
>> delaying the current release to fix it.
>> Something to be noted: We had 2+ months to fix a *critical* bug, but it
>> still remains open.
>> 
>> Since I do not have complete context of the whole discussion, it would be
>> great to see this bug fixed in the next release.
>> Shall resort to documenting this issue for the current release...
>> 
>> Matt
>> 
>> 
>> On Wed, Aug 24, 2016 at 12:27 PM, Mahadev Konar 
>> wrote:
>> 
>>> Mithun,
>>> 
>>> That’s a good concern but on the Apache jira looks like we agreed to 
move
>>> it out from 2.4.0. Ideally we should look at real blockers and any 
issues
>>> with licenses/artifacts to vote for the release. User exp is a good 
thing
>>> to look at – but we can look at fixing later?  Are you ok moving ahead 
with
>>> this in a later release?
>>> 
>>> 
>>> Thanks
>>> mahadev
>>> 
>>> On 8/24/16, 12:03 PM, "Mithun Mathew"  wrote:
>>> 
>>>   *-1*
>>> 
>>>   I was going through the task of adding HAWQ and PXF to stack HDP 2.4
>>>   through the install cluster wizard, for documentation purposes.
>>> 
>>>   The experience with version definition has changed the experience
>>> compared
>>>   to Ambari 2.2.2.
>>>   The experience for users has become worse because custom repositories
>>> do
>>>   not show up on the UI like in Ambari 2.2.2. If I switch to default
>>> version
>>>   definition, I see the custom repositories, but end up with old HDP-2.4
>>> url
>>>   links.
>>> 
>>>   I see a lot of potential for user errors from this page. I myself,
>>> ended up
>>>   with a broken cluster stuck on the Install wizard page.
>>> 
>>>   I saw some conversation here
>>>   https://issues.apache.org/jira/browse/AMBARI-17285
>>>   I still cannot support release of a product which has user experience
>>> worse
>>>   than the older version.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>   On Mon, Aug 22, 2016 at 12:45 PM, Jayush Luniya <
>>> jlun...@hortonworks.com>
>>>   wrote:
>>> 
 Hello,
 
 I have created an apache-ambari-2.4.0 release candidate.
 
 GIT source tag (release-2.4.0-rc0) https://git-wip-us.apache.org/
 repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/
>>> release-2.4.0-rc0
 
 Staging site: http://home.apache.org/~jluniya/apache-ambari-2.4.0-
>>> rc0/
 
 PGP release keys (signed using CD23CAAE)
 http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=
>>> 0x4BC59EDACD23CAAE
 
 One can look into the issues fixed in this release at
 https://issues.apache.org/jira/browse/AMBARI/fixforversion/12334239/
>>> ?
 selectedTab=com.atlassian.jira.jira-projects-plugin:
>>> version-summary-panel
 
 Vote will be open for 72 hours.
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 Regards,
 Jayush Luniya
 Apache Ambari 2.4.0 Release Manager
 
>>> 
>>> 
>>> 
>>>   --
>>>   *Mithun Mathew* (Matt)
>>> 
>>>  - www.linkedin.com/in/mithunmatt/
>>> 
>>> 
>>> 
>> 
>> 
>> -- 
>> *Mithun Mathew* (Matt)
>> 
>>  - www.linkedin.com/in/mithunmatt/
> 

Re: [VOTE] Apache Ambari 2.4.0 RC0

[Mahadev Konar]

Thanks Mithun! 

On 8/24/16, 10:38 PM, "Mithun Mathew"  wrote:

Looks like the only choice is fixing it in the next release rather than
delaying the current release to fix it.
Something to be noted: We had 2+ months to fix a *critical* bug, but it
still remains open.

Since I do not have complete context of the whole discussion, it would be
great to see this bug fixed in the next release.
Shall resort to documenting this issue for the current release...

Matt


On Wed, Aug 24, 2016 at 12:27 PM, Mahadev Konar 
wrote:

> Mithun,
>
>  That’s a good concern but on the Apache jira looks like we agreed to move
> it out from 2.4.0. Ideally we should look at real blockers and any issues
> with licenses/artifacts to vote for the release. User exp is a good thing
> to look at – but we can look at fixing later?  Are you ok moving ahead 
with
> this in a later release?
>
>
> Thanks
> mahadev
>
> On 8/24/16, 12:03 PM, "Mithun Mathew"  wrote:
>
> *-1*
>
> I was going through the task of adding HAWQ and PXF to stack HDP 2.4
> through the install cluster wizard, for documentation purposes.
>
> The experience with version definition has changed the experience
> compared
> to Ambari 2.2.2.
> The experience for users has become worse because custom repositories
> do
> not show up on the UI like in Ambari 2.2.2. If I switch to default
> version
> definition, I see the custom repositories, but end up with old HDP-2.4
> url
> links.
>
> I see a lot of potential for user errors from this page. I myself,
> ended up
> with a broken cluster stuck on the Install wizard page.
>
> I saw some conversation here
> https://issues.apache.org/jira/browse/AMBARI-17285
> I still cannot support release of a product which has user experience
> worse
> than the older version.
>
>
>
>
>
>
>
>
>
> On Mon, Aug 22, 2016 at 12:45 PM, Jayush Luniya <
> jlun...@hortonworks.com>
> wrote:
>
> > Hello,
> >
> > I have created an apache-ambari-2.4.0 release candidate.
> >
> > GIT source tag (release-2.4.0-rc0) https://git-wip-us.apache.org/
> > repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/
> release-2.4.0-rc0
> >
> > Staging site: http://home.apache.org/~jluniya/apache-ambari-2.4.0-
> rc0/
> >
> > PGP release keys (signed using CD23CAAE > 11371/pks/lookup?op=get&search=0x4BC59EDACD23CAAE>)
> > http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=
> 0x4BC59EDACD23CAAE
> >
> > One can look into the issues fixed in this release at
> > https://issues.apache.org/jira/browse/AMBARI/fixforversion/12334239/
> ?
> > selectedTab=com.atlassian.jira.jira-projects-plugin:
> version-summary-panel
> >
> > Vote will be open for 72 hours.
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > Regards,
> > Jayush Luniya
> > Apache Ambari 2.4.0 Release Manager
> >
>
>
>
> --
> *Mithun Mathew* (Matt)
>
>- www.linkedin.com/in/mithunmatt/
>
>
>


-- 
*Mithun Mathew* (Matt)

   - www.linkedin.com/in/mithunmatt/

Re: Creating Apache Ambari branch-2.5

[Jayush Luniya]

Hi all,
I have created the branch-2.5. However, please do not commit to the branch yet. 
I will follow up and let you know once the branch is ready for commits with 
further details.
Thanks
Jayush

From: Jayush Luniya mailto:jlun...@hortonworks.com>>
Date: Tuesday, August 23, 2016 at 9:52 AM
To: "dev@ambari.apache.org" 
mailto:dev@ambari.apache.org>>
Subject: Creating Apache Ambari branch-2.5

Hi all,

I would like to propose creating branch-2.5 for Apache Ambari 2.5.X releases. 
This branch will be created with branch-2.4 as parent and not trunk. Trunk has 
long term features that we don't want to pull into the 2.5.X releases. We 
should cherry pick the changes from trunk that we want to be included in 2.5.0 
release into this branch.  If you have any questions feel free to reach out.

Regards
Jayush

Re: [VOTE] Apache Ambari 2.4.0 RC0

[Robert Nettleton]

+1 for RC0

I verified the signatures of the tarball download, and ran some basic diff 
checks against the src tree. 


> On Aug 25, 2016, at 11:01 AM, Jonathan Hurley  wrote:
> 
> +1 for RC0 
> 
> Verified hashes, source files, and pom.xml to include 2.4.0.0.0
> 
>> On Aug 25, 2016, at 1:38 AM, Mithun Mathew  wrote:
>> 
>> Looks like the only choice is fixing it in the next release rather than
>> delaying the current release to fix it.
>> Something to be noted: We had 2+ months to fix a *critical* bug, but it
>> still remains open.
>> 
>> Since I do not have complete context of the whole discussion, it would be
>> great to see this bug fixed in the next release.
>> Shall resort to documenting this issue for the current release...
>> 
>> Matt
>> 
>> 
>> On Wed, Aug 24, 2016 at 12:27 PM, Mahadev Konar 
>> wrote:
>> 
>>> Mithun,
>>> 
>>> That’s a good concern but on the Apache jira looks like we agreed to move
>>> it out from 2.4.0. Ideally we should look at real blockers and any issues
>>> with licenses/artifacts to vote for the release. User exp is a good thing
>>> to look at – but we can look at fixing later?  Are you ok moving ahead with
>>> this in a later release?
>>> 
>>> 
>>> Thanks
>>> mahadev
>>> 
>>> On 8/24/16, 12:03 PM, "Mithun Mathew"  wrote:
>>> 
>>>   *-1*
>>> 
>>>   I was going through the task of adding HAWQ and PXF to stack HDP 2.4
>>>   through the install cluster wizard, for documentation purposes.
>>> 
>>>   The experience with version definition has changed the experience
>>> compared
>>>   to Ambari 2.2.2.
>>>   The experience for users has become worse because custom repositories
>>> do
>>>   not show up on the UI like in Ambari 2.2.2. If I switch to default
>>> version
>>>   definition, I see the custom repositories, but end up with old HDP-2.4
>>> url
>>>   links.
>>> 
>>>   I see a lot of potential for user errors from this page. I myself,
>>> ended up
>>>   with a broken cluster stuck on the Install wizard page.
>>> 
>>>   I saw some conversation here
>>>   https://issues.apache.org/jira/browse/AMBARI-17285
>>>   I still cannot support release of a product which has user experience
>>> worse
>>>   than the older version.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>   On Mon, Aug 22, 2016 at 12:45 PM, Jayush Luniya <
>>> jlun...@hortonworks.com>
>>>   wrote:
>>> 
 Hello,
 
 I have created an apache-ambari-2.4.0 release candidate.
 
 GIT source tag (release-2.4.0-rc0) https://git-wip-us.apache.org/
 repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/
>>> release-2.4.0-rc0
 
 Staging site: http://home.apache.org/~jluniya/apache-ambari-2.4.0-
>>> rc0/
 
 PGP release keys (signed using CD23CAAE)
 http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=
>>> 0x4BC59EDACD23CAAE
 
 One can look into the issues fixed in this release at
 https://issues.apache.org/jira/browse/AMBARI/fixforversion/12334239/
>>> ?
 selectedTab=com.atlassian.jira.jira-projects-plugin:
>>> version-summary-panel
 
 Vote will be open for 72 hours.
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 Regards,
 Jayush Luniya
 Apache Ambari 2.4.0 Release Manager
 
>>> 
>>> 
>>> 
>>>   --
>>>   *Mithun Mathew* (Matt)
>>> 
>>>  - www.linkedin.com/in/mithunmatt/
>>> 
>>> 
>>> 
>> 
>> 
>> -- 
>> *Mithun Mathew* (Matt)
>> 
>>  - www.linkedin.com/in/mithunmatt/
> 

Re: [VOTE] Apache Ambari 2.4.0 RC0

[Jonathan Hurley]

+1 for RC0 

Verified hashes, source files, and pom.xml to include 2.4.0.0.0

> On Aug 25, 2016, at 1:38 AM, Mithun Mathew  wrote:
> 
> Looks like the only choice is fixing it in the next release rather than
> delaying the current release to fix it.
> Something to be noted: We had 2+ months to fix a *critical* bug, but it
> still remains open.
> 
> Since I do not have complete context of the whole discussion, it would be
> great to see this bug fixed in the next release.
> Shall resort to documenting this issue for the current release...
> 
> Matt
> 
> 
> On Wed, Aug 24, 2016 at 12:27 PM, Mahadev Konar 
> wrote:
> 
>> Mithun,
>> 
>> That’s a good concern but on the Apache jira looks like we agreed to move
>> it out from 2.4.0. Ideally we should look at real blockers and any issues
>> with licenses/artifacts to vote for the release. User exp is a good thing
>> to look at – but we can look at fixing later?  Are you ok moving ahead with
>> this in a later release?
>> 
>> 
>> Thanks
>> mahadev
>> 
>> On 8/24/16, 12:03 PM, "Mithun Mathew"  wrote:
>> 
>>*-1*
>> 
>>I was going through the task of adding HAWQ and PXF to stack HDP 2.4
>>through the install cluster wizard, for documentation purposes.
>> 
>>The experience with version definition has changed the experience
>> compared
>>to Ambari 2.2.2.
>>The experience for users has become worse because custom repositories
>> do
>>not show up on the UI like in Ambari 2.2.2. If I switch to default
>> version
>>definition, I see the custom repositories, but end up with old HDP-2.4
>> url
>>links.
>> 
>>I see a lot of potential for user errors from this page. I myself,
>> ended up
>>with a broken cluster stuck on the Install wizard page.
>> 
>>I saw some conversation here
>>https://issues.apache.org/jira/browse/AMBARI-17285
>>I still cannot support release of a product which has user experience
>> worse
>>than the older version.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>On Mon, Aug 22, 2016 at 12:45 PM, Jayush Luniya <
>> jlun...@hortonworks.com>
>>wrote:
>> 
>>> Hello,
>>> 
>>> I have created an apache-ambari-2.4.0 release candidate.
>>> 
>>> GIT source tag (release-2.4.0-rc0) https://git-wip-us.apache.org/
>>> repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/
>> release-2.4.0-rc0
>>> 
>>> Staging site: http://home.apache.org/~jluniya/apache-ambari-2.4.0-
>> rc0/
>>> 
>>> PGP release keys (signed using CD23CAAE>> 11371/pks/lookup?op=get&search=0x4BC59EDACD23CAAE>)
>>> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=
>> 0x4BC59EDACD23CAAE
>>> 
>>> One can look into the issues fixed in this release at
>>> https://issues.apache.org/jira/browse/AMBARI/fixforversion/12334239/
>> ?
>>> selectedTab=com.atlassian.jira.jira-projects-plugin:
>> version-summary-panel
>>> 
>>> Vote will be open for 72 hours.
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>> 
>>> Regards,
>>> Jayush Luniya
>>> Apache Ambari 2.4.0 Release Manager
>>> 
>> 
>> 
>> 
>>--
>>*Mithun Mathew* (Matt)
>> 
>>   - www.linkedin.com/in/mithunmatt/
>> 
>> 
>> 
> 
> 
> -- 
> *Mithun Mathew* (Matt)
> 
>   - www.linkedin.com/in/mithunmatt/