phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (PHOENIX-8) Apache Phoenix 3.0
Date Tue, 21 Jan 2014 19:15:21 GMT

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

James Taylor edited comment on PHOENIX-8 at 1/21/14 7:14 PM:
-------------------------------------------------------------

I'd like to release an Apache Phoenix 2.2.3 for the following reasons:
1) It's ready (it's sitting in a branch on Github), while 3.0 is still a month away (will
send out the outstanding work remaining in a separate email).
2) Existing customers can easily cut over to it - it'll only require a minor, automatic upgrade
at startup time.
3) Existing customers will have a path to migrate to 3.0, as they otherwise wouldn't be able
to migrate directly from Github Phoenix 2.x to Apache Phoenix 3.0 (though we could arguably
make this possible).
4) It'll give us an opportunity to get the license, notice, source release, binary release
correct, so it'll be a breeze when we do it for 3.0

What's the downside of doing a Phoenix Apache 2.2.3 release?


was (Author: jamestaylor):
I'd like to release an Apache Phoenix 2.2.3 for the following reasons:
1) It's ready (it's sitting in a branch on Github), while 3.0 is still a month away (will
send out the outstanding work remaining in a separate email).
2) Existing customers can easily cut over to it - it'll only require a minor, automatic upgrade
at startup time.
3) Existing customers will have a path to migrate to 3.0, as they otherwise wouldn't be able
to migrate directly from Github Phoenix 2.x to Apache Phoenix 3.0 (though we could arguably
make this possible).
4) We can get this out immediately, while .
5) It'll give us an opportunity to get the license, notice, source release, binary release
correct, so it'll be a breeze when we do it for 3.0

What's the downside of doing a Phoenix Apache 2.2.3 release?

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

Mime
View raw message