You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Nigel Jones (JIRA)" <ji...@apache.org> on 2017/06/02 12:59:05 UTC

[jira] [Commented] (ATLAS-1855) Atlas version/release & dependency management/policy

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

Nigel Jones commented on ATLAS-1855:
------------------------------------

The main dependencies I can think of currently include : titan (0.54 -> janus), java (7->8->9), hbase/berkelydb/etc (titan persistence), maven (inc. various plugins),  though there are others (task to document?). there are also optional pieces we work with - kafka, ranger, solr

Deprecation policy might be that when we decided to deprecate we a) document in user guide b) report audit event in log c) remind user to review log! Then in release+2 the interface is removed

general version compatibility policy may cover guidelines that many already consider of - seamless data migration, options to enable new behaviour before flipping defaults, optional parms etc. API docs need to carefully document such changes. Any predicted switching of defaults could be managed similarly to deprecation

> Atlas version/release & dependency management/policy
> ----------------------------------------------------
>
>                 Key: ATLAS-1855
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1855
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Nigel Jones
>
> For the Atlas project we need a clear approach to how we manage dependencies, and indeed the dependencies of other projects & users upon us.
> For example this should include
>  * A clear approach to how we support backwards (and possibly) forwards compatability of both our published external interfaces, as well as persistent data formats
>  * Agreeing approach to deprecation for when that might be required
>  * Regularly reviewing the version of dependent components, and having a strategy as to when/how to update (this includes both toleration of releases, and exploitation)
> I initially raised ATLAS-1849 to specifically capture the Java 8 dependency question which we could use specifically for java, but there are general principles we should discuss/agree/document too as part of making Atlas an enterprise ready component



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)