[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-06-14 Thread Francis Chuang (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16513091#comment-16513091
 ] 

Francis Chuang commented on CALCITE-2330:
-

Thanks for merging the PRs [~risdenk] [~elserj] and [~laurentgo].

I am currently waiting for CALCITE-2299 to be reviewed and merged (thanks 
[~risdenk]).CALCITE-2322 seems to have stalled, so I am not sure if it will 
make it into 1.12.

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We are targeting the second week of June for release; last release (1.11) was 
> March 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-06-14 Thread Kevin Risden (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512684#comment-16512684
 ] 

Kevin Risden commented on CALCITE-2330:
---

[~francischuang] - CALCITE-2361 would be good to pull into Avatica 1.12.

[~julianhyde] - I am taking a look at CALCITE-2299.

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We are targeting the second week of June for release; last release (1.11) was 
> March 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-06-14 Thread Julian Hyde (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512539#comment-16512539
 ] 

Julian Hyde commented on CALCITE-2330:
--

Can someone review and commit the Avatica part of CALCITE-2299? It would be get 
that into this release.

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We are targeting the second week of June for release; last release (1.11) was 
> March 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-05-30 Thread Francis Chuang (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495897#comment-16495897
 ] 

Francis Chuang commented on CALCITE-2330:
-

That makes sense! I'll use the same approach for this release.

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We are targeting the second week of June for release; last release (1.11) was 
> March 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-05-30 Thread Julian Hyde (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495895#comment-16495895
 ] 

Julian Hyde commented on CALCITE-2330:
--

My personal preference is to close master from the start of the vote until the 
end (success or fail). Then the release will be a commit on the main code line.

Other folks aren't totally comfortable with this. If we were a project with 
multiple commits per day and multiple maintenance branches then I would agree 
with them, but at the current dev rates I don't think it's too much of a 
hardship for people to hold back their commits for a few days.

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We are targeting the second week of June for release; last release (1.11) was 
> March 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-05-30 Thread Francis Chuang (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495890#comment-16495890
 ] 

Francis Chuang commented on CALCITE-2330:
-

[~julianhyde] Thanks, that makes a lot of sense. Is there some guideline for 
when master should be declared closed? I am assuming once we get all the PRs 
and changes we want for this release in, we close master.

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We are targeting the second week of June for release; last release (1.11) was 
> March 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-05-30 Thread Julian Hyde (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495884#comment-16495884
 ] 

Julian Hyde commented on CALCITE-2330:
--

[~francischuang], May I suggest a different strategy. As RM you own 
branch-avatica-1.12 and only you should merge or push to it. For now the 
repository is "open" for commits, and committers will merge to the master 
branch. But at some point you can declare the repository "closed".

Force-pushing to master is discouraged, but you are welcome to force-push to 
branch-avatica-1.12 (as you are the only person using it). You should probably 
rebase the release branch onto master periodically, until you declare master 
closed. In the release branch you can start writing release notes, update 
version numbers in documentation, and so forth.

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We are targeting the second week of June for release; last release (1.11) was 
> March 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-05-30 Thread Francis Chuang (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495879#comment-16495879
 ] 

Francis Chuang commented on CALCITE-2330:
-

[~elserj], Thanks! Let's do all our work on branch-avatica-1.12 from now 
onwards.

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We are targeting the second week of June for release; last release (1.11) was 
> March 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-05-30 Thread Josh Elser (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495854#comment-16495854
 ] 

Josh Elser commented on CALCITE-2330:
-

I'm grabbing this and pulling it into master now.

I'll let you grab it into the release branch if you want it, [~francischuang].

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We are targeting the second week of June for release; last release (1.11) was 
> March 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-05-30 Thread Karan Mehta (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495851#comment-16495851
 ] 

Karan Mehta commented on CALCITE-2330:
--

Can you also merge CALCITE-2294? 

The PR: [https://github.com/apache/calcite-avatica/pull/48] was reviewed by 
[~elserj]

Thanks!

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We are targeting the second week of June for release; last release (1.11) was 
> March 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-05-30 Thread Julian Hyde (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495821#comment-16495821
 ] 

Julian Hyde commented on CALCITE-2330:
--

How ironic. And, thanks!

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We are targeting the second week of June for release; last release (1.11) was 
> March 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-05-29 Thread Kevin Risden (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494567#comment-16494567
 ] 

Kevin Risden commented on CALCITE-2330:
---

[~julianhyde] Fixed Calcite in 
[https://git-wip-us.apache.org/repos/asf?p=calcite.git;a=commit;h=542d51265d683dfd736c5e04f556e065b3667667]
 to avoid the problem now and when Avatica is upgraded to 1.12.0. It was an 
invalid assumption about isValid.

 

 

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We are targeting the second week of June for release; last release (1.11) was 
> March 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-05-29 Thread Julian Hyde (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494407#comment-16494407
 ] 

Julian Hyde commented on CALCITE-2330:
--

[~risdenk], Can you address the comment I added to CALCITE-1520. We need to be 
sure that we can make the Calcite test pass after we upgrade to Avatica 1.12.

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We currently have no estimated release date; last release (1.11) was March 
> 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-05-29 Thread Julian Hyde (JIRA)


[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494150#comment-16494150
 ] 

Julian Hyde commented on CALCITE-2330:
--

I will review and merge CALCITE-2303 and CALCITE-1884.

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We currently have no estimated release date; last release (1.11) was March 
> 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CALCITE-2330) Release Avatica 1.12

2018-05-25 Thread Karan Mehta (JIRA)

[ 
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16491470#comment-16491470
 ] 

Karan Mehta commented on CALCITE-2330:
--

Please include CALCITE-2294 as well. Its going to be in it soon and required 
for us for some additional changes to PQS

> Release Avatica 1.12
> 
>
> Key: CALCITE-2330
> URL: https://issues.apache.org/jira/browse/CALCITE-2330
> Project: Calcite
>  Issue Type: Bug
>  Components: avatica
>Reporter: Julian Hyde
>Priority: Major
> Fix For: avatica-1.12.0
>
>
> Release Avatica 1.12.
> We currently have no estimated release date; last release (1.11) was March 
> 2018 and the one before (1.10) that was May 2017.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)