Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 210B018420 for ; Tue, 2 Feb 2016 02:06:40 +0000 (UTC) Received: (qmail 4281 invoked by uid 500); 2 Feb 2016 02:06:40 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 4242 invoked by uid 500); 2 Feb 2016 02:06:40 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 4219 invoked by uid 99); 2 Feb 2016 02:06:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Feb 2016 02:06:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D01312C044E for ; Tue, 2 Feb 2016 02:06:39 +0000 (UTC) Date: Tue, 2 Feb 2016 02:06:39 +0000 (UTC) From: "Hadoop QA (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-14837) Versions: display all versions as tabs on left side, version details on selecting MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-14837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127445#comment-15127445 ] Hadoop QA commented on AMBARI-14837: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12785639/AMBARI-14837.patch against trunk revision . {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5147//console This message is automatically generated. > Versions: display all versions as tabs on left side, version details on selecting > --------------------------------------------------------------------------------- > > Key: AMBARI-14837 > URL: https://issues.apache.org/jira/browse/AMBARI-14837 > Project: Ambari > Issue Type: Task > Components: ambari-web > Affects Versions: 2.4.0 > Reporter: Xi Wang > Assignee: Xi Wang > Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-14837.patch, AMBARI-14837.patch, Screen Shot 2016-01-29 at 5.59.13 PM.png, Screen Shot 2016-01-29 at 5.59.28 PM.png, Screen Shot 2016-02-01 at 11.33.35 AM.png > > > This one is to implement" Manage Ambari > Versions" page. > 1. All versions show be displayed as tabs on the left side, each patch version should be a child of its parent stack version. > 2. On selecting a version (either patch version or original stack version), all the version definition info show up on the right side. > This look should be the same as register version page. "Details" and "Contents" are un-editable, "Repos" is editable and addable. > 3. Add a mark/icon to the patch versions to differentiate them from original stack versions. > Related API: > {code} > GET /api/v1/stacks/HDP/versions/2.3/repository_versions > PUT /api/v1/stacks/HDP/versions/2.3/repository_versions // for editing repo urls > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)