Allright, I will send a separate email to start the "official" discussion for 1.26.0.
Best, Ruben Le mer. 23 sept. 2020 à 17:17, Julian Hyde <[email protected]> a écrit : > I agree, this is a good time for a release. Remember that releases > always take a week or two longer than we think. > > Danny, I need your help on > https://issues.apache.org/jira/browse/CALCITE-4259 (supporting JDK 15 > and removing log4j), which is a must-fix for 1.26. > > Julian > > > On Wed, Sep 23, 2020 at 2:30 AM Danny Chan <[email protected]> wrote: > > > > Thanks so much, Ruben ~ > > > > Can the RC date be one week in advance, say about 3th-8th October, > because I need some time for the upgrade of Flink side. > > > > Before the RC, I need amount of local tests for Flink and I would have > to make sure that the 1.26.0 is production ready for the nest Flink release. > > > > And it would be great if we can make this sooner, this is important > because I can fire the upgrade PR sooner and actually we have many features > developed based on current master branch. > > > > Best, > > Danny Chan > > 在 2020年9月23日 +0800 PM4:15，Ruben Q L <[email protected]>，写道： > > > Hello Danny, > > > > > > As the release manager for 1.26.0, I think what you say sounds > reasonable. > > > We had 1.25 around mid-August, I think we could definitely aim mid/end > > > October for 1.26. I would propose to have a RC by 10th-15th October. > > > According to the Jira dashboard [1] there are still 6 unresolved > issues, > > > let us try to focus on that before adding new stuff into the next > version. > > > > > > Best regards, > > > Ruben > > > > > > [1] > > > > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 > > > > > > > > > Le mer. 23 sept. 2020 à 06:31, Danny Chan <[email protected]> a > écrit : > > > > > > > Is there any possibility that 1.26.0 can be released in the following > > > > weeks, e.g. within the October ? > > > > > > > > Apache Flink would release next major version in the end of October, > if we > > > > can use the latest Calcite code, that would be awesome ~ > > > > > > > > Best, > > > > Danny Chan > > > > >
