[
https://issues.apache.org/jira/browse/PHOENIX-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878290#comment-13878290
]
Lars Hofhansl commented on PHOENIX-8:
-------------------------------------
Yeah, some major feature will require breaking wire compatibility, at which
point we might want to change the major version.
What I meant was that from 3.0 we could at least be compatible with 3.1.x,
3.2.x, etc, and hence only add features there that do not violate that, but not
be limited strictly to bugfixes.
That way it is a predictable story and we can still break wire compatibility
for large new features, it just needs a major version change.
Then users can choose (for example with versions 3 and 4):
* absolute stability, just bugfixes: Stay within (say) 3.1.x
* wire and backward compatibility: Stay within 3.x
* new major features: move to 4.x (but that break compatibility)
(The above is the model we are shooting for with HBase as per the last PMC
meetup)
> Apache Phoenix 3.0
> ------------------
>
> Key: PHOENIX-8
> URL: https://issues.apache.org/jira/browse/PHOENIX-8
> Project: Phoenix
> Issue Type: Task
> Reporter: Andrew Purtell
>
> Given the GitHub hosted Phoenix project is already up to the release series
> 2.0.x, I propose the first version of Phoenix released under the Apache roof
> should be 3.0.0.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
