*-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 <[email protected]> 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=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/
