You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@predictionio.apache.org by "Donald Szeto (JIRA)" <ji...@apache.org> on 2017/04/03 20:09:41 UTC

[jira] [Updated] (PIO-32) create component upgrade releases

     [ https://issues.apache.org/jira/browse/PIO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Donald Szeto updated PIO-32:
----------------------------
    Labels: gsoc2017  (was: )

> create component upgrade releases
> ---------------------------------
>
>                 Key: PIO-32
>                 URL: https://issues.apache.org/jira/browse/PIO-32
>             Project: PredictionIO
>          Issue Type: New Feature
>    Affects Versions: future release
>            Reporter: Pat Ferrel
>              Labels: gsoc2017
>             Fix For: future release
>
>
> Create a method for component upgrades that break binary compatibility like Spark 2.x, Scala 2.11, and those that require source changes like Elasticsearch 2.x
> If not 2 release branches then someone needs to propose an alternative. Maven profiles would still require different versions of PIO source to be used for ES 2.x--not sure about other upgrades. Profiles are fine for different dependency libs. 



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