[
https://issues.apache.org/jira/browse/CALCITE-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
