+1 from my side. Count on my support if somethings need to be done from PMC
This link works for me (without pre-selected issue in URL JIRA displays more predictable results): https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.14%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority and one more filter with open issues https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20('2.14'))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20not%20in%20('CLOSED'%2C%20'RESOLVED')%20ORDER%20BY%20priority There are only 40, for now. пн, 8 авг. 2022 г. в 16:01, Taras Ledkov <tled...@apache.org>: > Dear Ignite Community! > > I suggest starting Apache Ignite 2.14 release activities. > > We've accumulated a hundred resolved [1] issues with new > features and bug fixes which are waiting for their release date. For > example, > - bunch of Calcite based SQL engine fixes and improvements; > - thin clients improvements; > - fixes at the core: update counters, binary meta, etc. > > I want to propose myself to be the release manager of the planning release. > > I propose the following timeline: > > Scope Freeze: August 17, 2022 > Code Freeze: August 24, 2022 > Voting Date: September 7, 2022 > Release Date: September 14, 2022 > > [1]. > https://issues.apache.org/jira/browse/IGNITE-16958?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.14%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority > > -- > With best regards, > Taras Ledkov >
