+1 On Mar 24, 2017 4:41 PM, Sumit Mohanty <[email protected]> wrote: +1 for RC1
On a clean vagrant VM: * verified signature, md5 and sha1 hashes * keychain looks good * expanded the source tarball, compiled, and ran unit tests - compilation succeeded along with RAT check. Two ambari-server unit tests failed but that should not hold up the release. I will open a bug for the next release after verifying that they are not due to my VM environment. Thanks Aravindan. -Sumit ________________________________________ From: Aravindan Vijayan <[email protected]> Sent: Thursday, March 23, 2017 2:11 PM To: [email protected] Subject: [VOTE] Apache Ambari 2.5.0 RC1 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=refs/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/?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) 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
