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

Posted to dev@bahir.apache.org by ckadner <gi...@git.apache.org> on 2016/07/27 03:19:54 UTC

[GitHub] bahir pull request #:

Github user ckadner commented on the pull request:

    https://github.com/apache/bahir/commit/91e82f42bac58fd8d912e892a5ebfca79f6b8268#commitcomment-18407931
  
    In pom.xml:
    In pom.xml on line 98:
    @lresende - why this change?
    
    I suppose the `2.0.0` version should be used to build and upload any new Bahir `2.0.0` releases which is what most Bahir consumers would be using via `spark-submit --packages ...`
    
    For continuous development and integration testing however, should we not build off of the latest Spark development SNAPSHOT to make sure we catch possible regressions and API breakages? To make sure we have correct alignment, I suppose we create the appropriate branch in Bahir to go with the `2.0.0` version of Spark.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---