carbondata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chenliang613 <...@git.apache.org>
Subject [GitHub] incubator-carbondata pull request #392: change snapshot version number due t...
Date Sun, 04 Dec 2016 12:38:38 GMT
GitHub user chenliang613 opened a pull request:

    https://github.com/apache/incubator-carbondata/pull/392

    change snapshot version number due to new structure changes as per mailing proposal

    A rich set of features are planned to be included into next release, and more importantly
there will be external API changes introduced as will integrate with Spark 2.x, remove kettle
etc. 
    
    The next version number will use 1.0.0 for distinguishing major API changes, it would
be much helpful to reduce maintenance cost through distinguishing the major different version
due to major API changes.
    
    Please find the detailed discussion on dev@mailing list : http://apache-carbondata-mailing-list-archive.1130556.n5.nabble.com/CarbonData-propose-major-version-number-increment-for-next-version-to-1-0-0-td3131.html

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/chenliang613/incubator-carbondata version1.0.0

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-carbondata/pull/392.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #392
    
----
commit 05afe2ab2025554279a5aa967885f7c799d81cb6
Author: chenliang613 <chenliang613@apache.org>
Date:   2016-12-04T12:30:39Z

    change snapshot version number due to new structure changes

----


---
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.
---

Mime
View raw message