ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yusaku Sako <yus...@hortonworks.com>
Subject Re: [VOTE] Apache Ambari 2.5.0 RC1
Date Tue, 28 Mar 2017 00:28:09 GMT
Hi all,

I was trying to push the release artifacts to the dist svn [1] but was unable to.
Apparently there is a 200MB limit [2] on the upload size.
I was looking into why the release artifact got much bigger compared to 2.4.2 which was much
under this limit.
It turns out that when the tarball for 2.5.0 RC1 [3] was created, we accidentally included
the ".git" folder.  This folder by itself was more than 200MB.
After removing that folder and creating another tarball, it is now around 70MB.
Aravindan, please re-generate the artifacts for RC2.
Since the only difference from RC1 will be that the ".git" folder is removed from the tarball
(and the md5/sha1 re-computed and the artifact re-signed), I don't think we need to go thru
the standard 72-hour voting process.
I propose that we keep it short and call for a 24-hour vote period so that the community has
a chance to verify.

Thanks,
Yusaku

[1] https://dist.apache.org/repos/dist/release/ambari/

[2] https://issues.apache.org/jira/browse/INFRA-13749
[3] http://home.apache.org/~avijayan/apache-ambari-2.5.0-rc1/apache-ambari-2.5.0-src.tar.gz



On 3/27/17, 11:39 AM, "Aravindan Vijayan" <avijayan@hortonworks.com> wrote:

>Hello all,
>
>The voting process for Apache Ambari 2.5.0 RC1 has completed. The vote is in favor of
releasing Apache Ambari 2.5.0 RC1.
>
>The final votes are as follows:
>5 +1 (4 PMCs, 1 Committer)
>0  +0
>0  -1
>
>The following is a list of the votes:
>
>Sumit Mohanty (PMC) +1
>Jayush Luniya (PMC) +1
>Nate Cole (PMC) +1
>Alejandro Fernandez (PMC) +1
>Aravindan Vijayan (Committer) +1
>
>I will begin the process of creating the release artifacts for Ambari-2.5.0 based on RC1.
Thanks to all who participated in the voting process.
>
>
>-- 
>Thanks and Regards,
>Aravindan Vijayan
>
>
>
>
>
>
>
>On 3/27/17, 11:18 AM, "Alejandro Fernandez" <afernandez@hortonworks.com> wrote:
>
>>+1 for 2.5.0 RC1
>>
>>Thanks,
>>Alejandro Fernandez
>>Apache Ambari PMC
>>
>>On 3/23/17, 2:11 PM, "Aravindan Vijayan" <avijayan@hortonworks.com> wrote:
>>
>>>Hello all,
>>>
>>>I have created an apache-ambari-2.5.0 release candidate.
>>>
>>>GIT source tag (release-2.5.0-rc1)
>>>https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=r
>>>efs/tags/release-2.5.0-rc1
>>>
>>>Staging site:  http://home.apache.org/~avijayan/apache-ambari-2.5.0-rc1/
>>>
>>>PGP release keys (signed using 088372a9) -
>>>http://pgp.mit.edu:11371/pks/lookup?search=0x088372A9&op=vindex
>>>
>>>One can look into the issues fixed in this release at
>>>https://issues.apache.org/jira/browse/AMBARI/fixforversion/12336060/?selec
>>>tedTab=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)
>>>
>>>My vote: +1
>>>
>>>FYI, the list of commits between rc0 and rc1
>>>70b4ba403dd7e890d7fcc5964b1cd231ee6e98c0 AMBARI-20516 create table
>>>failing with HiveAccessControlException (additional patch). (ababiichuk)
>>>7bb1e3335d41ab7adaf0c66ae5fd8df454178cd7 Revert "AMBARI-20488 Config
>>>types are validated before the cluster resources are persisted"
>>>95d7cc2c000c350dc0e5efa5a0660098f21da547 Revert "AMBARI-20542 Fixed
>>>configuration type validation in case of blueprint deployments."
>>>50b192979eca936bdb8ea1ecb9a1bb624c28e7fc AMBARI-20542 Fixed configuration
>>>type validation in case of blueprint deployments.
>>>
>>>--
>>>Thanks and Regards,
>>>Aravindan Vijayan
>>
>>
Mime
View raw message