Andrei, Do you know when you might be available? Two weeks have passed since your last note.
We originally wanted to release in December, then it was pushed back to mid-January. We can't wait much longer. Julian On Wed, Jan 22, 2020 at 8:07 AM Andrei Sereda <and...@sereda.cc> wrote: > > Hello, > > I would like to ask community if it is OK if 1.22 release gets delayed by > 2-3 weeks ? > > I have tried to book 1 week from work but, unfortunately, right now it is > not easy (things should be better in February). > > Another option is to swap with somebody doing next (1.2[345]) release. > > Please let me know what you think and apologies for the inconvenience. > > Andrei. > > > On Wed, Dec 4, 2019 at 4:55 PM Julian Hyde <jh...@apache.org> wrote: > > > I don’t mind whether the release happens in December or January, but > > either way, let’s start burning down the backlog of PRs now. > > > > > > > On Dec 2, 2019, at 11:43 PM, Enrico Olivelli <eolive...@gmail.com> > > wrote: > > > > > > Andrei > > > > > > Il mar 3 dic 2019, 08:21 Rui Wang <amaliu...@apache.org <mailto: > > amaliu...@apache.org>> ha scritto: > > > > > >> Thank you for this notification. > > >> > > >> Please try to make CALCITE-3272[1] into 1.22 (change the fix version to > > >> 1.22 already). > > >> > > >> > > >> [1]: https://github.com/apache/calcite/pull/1587 > > >> > > >> -Rui > > >> > > >> On Mon, Dec 2, 2019 at 6:35 PM Chunwei Lei <chunwei.l...@gmail.com> > > wrote: > > >> > > >>> Thank you for your work, Anderi. > > >>> > > >>> Let's get CALCITE-1581[1] into 1.22. > > >>> > > >>> +1 for release at early-mid January '20 (to have more time to review > > >> prs). > > >>> > > >>> > > >>> [1] https://github.com/apache/calcite/pull/1138 > > >>> > > >>> > > >>> Best, > > >>> Chunwei > > >>> > > >>> > > >>> On Tue, Dec 3, 2019 at 8:02 AM Andrei Sereda <and...@sereda.cc> wrote: > > >>> > > >>>> Hello, > > >>>> > > >>>> Calcite 1.21 was released about 3 months ago (2019-09) and it is time > > >> to > > >>>> start preparation for 1.22. > > >>>> > > >>>> Current open issues and pull requests can be seen in [1] and [2]. > > There > > >>> are > > >>>> many PRs left from previous releases and it would be nice to review as > > >>> many > > >>>> as possible. Please change "fix version" in JIRA to 1.22 if you would > > >>> like > > >>>> the contribution be considered for this release. It is also helpful to > > >>> mark > > >>>> PR with "LGTM-will-merge-soon" label so other contributors are aware > > of > > >>>> your review. > > >>>> > > >>>> Committers please go over existing PRs and try to prioritize / > > finalize > > >>>> them. Also let me know which changes (in your opinion) are ready or > > >>> should > > >>>> be considered for this release. Don't forget that current policy of > > >>>> frequent releases allows better work scheduling without blocking > > >> existing > > >>>> release plan. > > >>>> > > >>>> In terms of dates, let's agree on release time frame late December '19 > > >> or > > >>>> early-mid January '20 ? > > >> > > > > > > I (from HerdDB community) would prefer late December if possible, as we > > are > > > stuck to an older 1.19 version of Calcite. > > > Current Calcite master is is great shape from our point of view > > > > > > Thanks for driving this > > > Enrico > > > > > > > > > > > > > > > > > >>> > > >>>> Let me know if I have missed anything or if current plan is > > >> inconvenient. > > >>>> > > >>>> Thanks, > > >>>> Andrei. > > >>>> > > >>>> [1] > > >>>> > > >>> > > >> > > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 > > < > > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 > > > > > >>>> [2] https://github.com/apache/calcite/pulls < > > https://github.com/apache/calcite/pulls> > >
