ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Venkat <venkat...@gmail.com>
Subject Re: [VOTE] Apache Ambari 2.4.0 RC0
Date Thu, 25 Aug 2016 21:50:20 GMT
+1

On Wed, Aug 24, 2016 at 10:38 PM, Mithun Mathew <mithmatt@gmail.com> 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 <mahadev@hortonworks.com>
> 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" <mithmatt@gmail.com> 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 <
> > jluniya@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=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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message