-1 (binding) Comments:
The pom.xml in https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=log;h=refs/tags/release-2.0.0-rc2 has a snapshot version. The source tarball also has 2.0.0-SNAPSHOT. Various bits of code ( views ) also have snapshot versions. Release contains a DISCLAIMER saying Ambari is still incubating. High time this was fixed. No CHANGES.txt or release notes in the release artifact? Release artifacts should ideally be named apache-ambari-*. Should the artifact be named *-src-* too ? sha file is named “.sha” but actually contains a sha1 sig. The release manager’s keys are not in the KEYS file. For future releases, you should really use dist for staging a release. Easier to have track and have history on what is being voted on. Likewise, the KEYS file should also be available on the download link for users to be able to verify the authenticity of the release. I remember there being a problem the last time around where the api jars were not deployed to nexus and verified as part of the release process. Have those steps been missed again? — Hitesh On Mar 26, 2015, at 1:52 AM, Jayush Luniya <[email protected]> wrote: > Hi, > > I have created an ambari-2.0.0 release candidate (RC2). > > GIT source tag: > https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=log;h=refs/tags/release-2.0.0-rc2 > > Staging site: http://people.apache.org/~jluniya/ambari-2.0.0-rc2/ > > PGP release keys (signed using CD23CAAE): > http://pgp.mit.edu:11371/pks/lookup?search=0xCD23CAAE&op=vindex > > One can look into the issues fixed in this release at > https://issues.apache.org/jira/browse/AMBARI/fixforversion/12327486 > > Total 2.0.0 JIRAs: 1723 > > Total JIRAs Resolved as Fixed: 1680 > > Released Feature List: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=30755705 > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my vote to start: +1 > > Thanks > > Jayush Luniya > > Ambari 2.0.0 Release Manager
