Mailing-List: contact dev-help@atlas.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@atlas.incubator.apache.org
Date: Thu, 19 Nov 2015 18:00:15 +0000 (UTC)
From: "Darshan Kumar (JIRA)" <jira@apache.org>
To: dev@atlas.incubator.apache.org
Message-ID: <JIRA.12913668.1447759382000.125650.1447956015366@Atlassian.JIRA>
In-Reply-To: <JIRA.12913668.1447759382000@Atlassian.JIRA>
References: <JIRA.12913668.1447759382000@Atlassian.JIRA>
 <JIRA.12913668.1447759382679@arcas>
Subject: [jira] [Commented] (ATLAS-331) UI: Keep UI, Backward compatibility.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ATLAS-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014038#comment-15014038 ] 

Darshan Kumar commented on ATLAS-331:
-------------------------------------

[~bergenholtz] UI should be backward compatible in a sense that after releasing a first version of an application some API response structure is changed. 
In this case, UI code should be written in a way that it should work with both the version with released and the new one[changed one]

For example: We had a release of ATLAS as 0.5-incubating. Now in new release 0.6-incubating backend API [ api/atlas/entity ] response structure is changed. 
So UI code should work with both the releases 0.5-incubating and 0.6-incubationg.

> UI: Keep UI, Backward compatibility.
> ------------------------------------
>
>                 Key: ATLAS-331
>                 URL: https://issues.apache.org/jira/browse/ATLAS-331
>             Project: Atlas
>          Issue Type: Task
>            Reporter: roshni gadiyar
>            Priority: Minor
>              Labels: Atlas-UI
>
> Keep UI, Backward compatibility.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)