That sounds about right. There are often minor changes in process. I usually update HOWTO.md as I go along and include it in the final squashed commit that includes the release notes.
The other change of process this release is to generate a .sha512 file rather than a .mds. That will require a code change to pom.xml. Julian > On Aug 30, 2017, at 3:01 AM, Michael Mior <[email protected]> wrote: > > Just a note that it seems like a slight change in process is required. One > step is to check for resolved issues that do not have a fix version > assigned. It seems like this should now exclude Avatica issues since it is > no longer released in tandem. Please correct me if I'm wrong, otherwise > I'll update the documentation. > > -- > Michael Mior > [email protected] > > 2017-08-30 9:34 GMT+02:00 Michael Mior <[email protected]>: > >> Thanks Julian. I'll take a closer look at the remaining issues this >> evening. If there are any small ones I can take on myself, I'll do so. >> Otherwise, I'll move any remaining unassigned issues. >> >> -- >> Michael Mior >> [email protected] >> >> On Aug 28, 2017 23:20, "Julian Hyde" <[email protected]> wrote: >> >>> I don’t think there are any cases that absolutely HAVE to be in 1.14. If >>> people get a PR ready (working, and quality) in time, we’ll consider it. I >>> listed the 10 (yes, ten!) PRs I am currently reviewing in 1970. I don’t >>> think there will be many more. >>> >>> Julian >>> >>> >>>> On Aug 28, 2017, at 2:12 PM, Michael Mior <[email protected]> wrote: >>>> >>>> Sounds good. Just a heads up that I'll only be online sporadically the >>> rest >>>> of the week as well. I started off the release branch with an initial >>>> commit to change version numbers. Release tracking issue is linked >>> below. I >>>> marked all issues tagged for 1.13 as blockers. If anyone has issues they >>>> don't expect to be done, please unlink and change the target version. >>>> >>>> https://issues.apache.org/jira/browse/CALCITE-1970 < >>> https://issues.apache.org/jira/browse/CALCITE-1970> >>>> >>>> At this point I see two which seem unlikely to make it: >>>> >>>> https://issues.apache.org/jira/browse/CALCITE-1814 < >>> https://issues.apache.org/jira/browse/CALCITE-1814> >>>> https://issues.apache.org/jira/browse/CALCITE-1913 < >>> https://issues.apache.org/jira/browse/CALCITE-1913> >>>> >>>> Also, I noticed Oracle integration tests are suggested as part of the >>>> release process. As I don't have an Oracle install, if someone else >>> would >>>> be able to do this when the time comes, that would be great. >>>> >>>> -- >>>> Michael Mior >>>> [email protected] <mailto:[email protected]> >>>> >>>> 2017-08-28 22:37 GMT+02:00 Julian Hyde <[email protected] <mailto: >>> [email protected]>>: >>>> >>>>> That would be great, Michael. Thank you. >>>>> >>>>> You won’t need your signing key for a while. The first step is drafting >>>>> release notes, shepherding in the final PRs, and getting people to >>> hold off >>>>> risky changes so that the main line stabilizes. That takes a few days. >>>>> >>>>> I recommend creating a JIRA case (like https://issues.apache.org/ < >>> https://issues.apache.org/> >>>>> jira/browse/CALCITE-1837 <https://issues.apache.org/ < >>> https://issues.apache.org/> >>>>> jira/browse/CALCITE-1837>) so that you can track the remaining cases as >>>>> blockers. Create a mmior/branch-1.14 and start making the edits >>> described >>>>> in HOWTO. >>>>> >>>>> Julian >>>>> >>>>> >>>>>> On Aug 28, 2017, at 1:27 PM, Michael Mior <[email protected] >>> <mailto:[email protected]>> wrote: >>>>>> >>>>>> I'd be up for doing this although I'm out of the country until next >>> week >>>>>> and unfortunately I left my private key for signing at home. >>>>>> >>>>>> -- >>>>>> Michael Mior >>>>>> [email protected] <mailto:[email protected]> <mailto:[email protected] >>> <mailto:[email protected]>> >>>>>> >>>>>> 2017-08-28 21:20 GMT+02:00 Julian Hyde <[email protected] <mailto: >>> [email protected]> <mailto: >>>>> [email protected] <mailto:[email protected]>>>: >>>>>> >>>>>>> Any volunteers for a release manager? >>>>>>> >>>>>>>> On Aug 28, 2017, at 12:20 PM, Julian Hyde <[email protected] >>> <mailto:[email protected]>> wrote: >>>>>>>> >>>>>>>> Yes, the RM needs to be a committer. And in fact it is easier if >>> they >>>>>>> are a PMC member. >>>>>>>> >>>>>>>> But you can definitely help. You could manually run some tests: run >>> the >>>>>>> test suite against one of our supported back-end databases, e.g. >>>>>>> Elasticsearch or MySQL or MongoDB, and log bugs. Build and run tests >>> on >>>>>>> Windows (our coverage there is poor). Also look through the bugs that >>>>> have >>>>>>> been fixed this release [1] and see whether they are adequately >>> tested >>>>> and >>>>>>> documented. And, then there is a release candidate, try building it, >>> and >>>>>>> vote in the release thread. Your vote isn’t binding, but still >>> matters. >>>>>>>> >>>>>>>> Julian >>>>>>>> >>>>>>>> [1] https://issues.apache.org/jira/issues/?jql=project%20% < >>> https://issues.apache.org/jira/issues/?jql=project%20%> >>>>>>> 3D%20CALCITE%20AND%20fixVersion%20%3D%201.14.0 < >>>>> https://issues.apache.org/ <https://issues.apache.org/> < >>> https://issues.apache.org/ <https://issues.apache.org/>> >>>>>>> jira/issues/?jql=project%20=%20CALCITE%20AND%20fixVersion%20 >>> =%201.14.0> >>>>>>>> >>>>>>>>> On Aug 28, 2017, at 11:22 AM, Jesus Camacho Rodriguez < >>>>>>> [email protected] <mailto:[email protected]> <mailto: >>> [email protected] <mailto:[email protected]>> <mailto: >>>>> [email protected] <mailto:[email protected]> <mailto: >>> [email protected] <mailto:[email protected]>>>> wrote: >>>>>>>>> >>>>>>>>> I agree that we should create a new release soon to continue >>>>>>>>> with our normal release cadence. >>>>>>>>> >>>>>>>>> I would like CALCITE-1947 to go in before the release, I should >>>>>>>>> push it this week. >>>>>>>>> >>>>>>>>> @Michael, AFAIK you need to be a committer to be the RM. >>>>>>>>> >>>>>>>>> -Jesús >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On 8/25/17, 6:27 PM, "LogSplitter" <[email protected] >>> <mailto:[email protected]> <mailto: >>>>> [email protected] <mailto:[email protected]>> <mailto: >>>>>>> [email protected] <mailto:[email protected]>>> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> Do you have to be a committer to be release manager. >>>>>>>>>> >>>>>>>>>> Whats involved. I will volunteer anyway :-) >>>>>>>>>> >>>>>>>>>> Michael. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 08/25/2017 04:07 PM, Julian Hyde wrote: >>>>>>>>>>> It's about time we did a release. 1.13 was exactly 2 months ago. >>>>>>>>>>> >>>>>>>>>>> Does anyone have any constraints on the release date? (Must be >>>>> before >>>>>>>>>>> X, must be after Y?) >>>>>>>>>>> >>>>>>>>>>> Any volunteers to be release manager? >>>>>>>>>>> >>>>>>>>>>> Julian >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Fri, Aug 25, 2017 at 3:07 PM, LogSplitter < >>>>> [email protected] <mailto:[email protected]> >>>>>>> <mailto:[email protected] <mailto:[email protected]> >>> <mailto:[email protected] <mailto:[email protected]>>>> >>>>> wrote: >>>>>>>>>>>> Hello, >>>>>>>>>>>> >>>>>>>>>>>> I was wondering if there is any estimated of when calcite 1.14 >>>>> might >>>>>>> be >>>>>>>>>>>> released. >>>>>>>>>>>> >>>>>>>>>>>> I am tossing up whether I use a patched version 1.13 release or >>>>> wait >>>>>>> a >>>>>>>>>>>> little longer for real 1.14 for work I am needing to ship? >>>>>>>>>>>> >>>>>>>>>>>> thanks >>>>>>>>>>>> Michael >>> >>>
