Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]
+1! -- Ilya Kasnacheev ср, 29 мар. 2023 г. в 23:13, Vladimir Steshin : > +1 > > 29.03.2023 21:56, Alex Plehanov пишет: > > Dear Ignite Community! > > > > I suggest starting Apache Ignite 2.15 release activities. > > > > We've accumulated more than two hundred resolved issues [1] with new > > features and bug fixes which are waiting for release. > > The major changes related to the proposed release: > > - Incremental snapshots. > > - Java thin client improvements (logging, connections balancing, > > events listening, endpoints discovery) > > - Calcite based SQL engine improvements (memory quotas, index scans > > optimisations). > > - Reworked permission management for system tasks. > > - Removed some deprecated functionality (daemon nodes, visorcmd, legacy > JMX > > beans) > > etc. > > > > I want to propose myself to be the release manager of the planning > release. > > > > I propose the following timeline: > > > > Scope Freeze: April 08, 2023 > > Code Freeze: April 15, 2023 > > Voting Date: April 22, 2023 > > Release Date: April 29, 2023 > > > > [1]. > > > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27) > > > > WDYT? > > >
Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]
+1 29.03.2023 21:56, Alex Plehanov пишет: Dear Ignite Community! I suggest starting Apache Ignite 2.15 release activities. We've accumulated more than two hundred resolved issues [1] with new features and bug fixes which are waiting for release. The major changes related to the proposed release: - Incremental snapshots. - Java thin client improvements (logging, connections balancing, events listening, endpoints discovery) - Calcite based SQL engine improvements (memory quotas, index scans optimisations). - Reworked permission management for system tasks. - Removed some deprecated functionality (daemon nodes, visorcmd, legacy JMX beans) etc. I want to propose myself to be the release manager of the planning release. I propose the following timeline: Scope Freeze: April 08, 2023 Code Freeze: April 15, 2023 Voting Date: April 22, 2023 Release Date: April 29, 2023 [1]. https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27) WDYT?
Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]
+1 On Wed, 29 Mar 2023 at 20:57, Alex Plehanov wrote: > > Dear Ignite Community! > > I suggest starting Apache Ignite 2.15 release activities. > > We've accumulated more than two hundred resolved issues [1] with new > features and bug fixes which are waiting for release. > The major changes related to the proposed release: > - Incremental snapshots. > - Java thin client improvements (logging, connections balancing, > events listening, endpoints discovery) > - Calcite based SQL engine improvements (memory quotas, index scans > optimisations). > - Reworked permission management for system tasks. > - Removed some deprecated functionality (daemon nodes, visorcmd, legacy JMX > beans) > etc. > > I want to propose myself to be the release manager of the planning release. > > I propose the following timeline: > > Scope Freeze: April 08, 2023 > Code Freeze: April 15, 2023 > Voting Date: April 22, 2023 > Release Date: April 29, 2023 > > [1]. > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27) > > WDYT?
Apache Ignite 2.15 RELEASE [Time, Scope, Manager]
Dear Ignite Community! I suggest starting Apache Ignite 2.15 release activities. We've accumulated more than two hundred resolved issues [1] with new features and bug fixes which are waiting for release. The major changes related to the proposed release: - Incremental snapshots. - Java thin client improvements (logging, connections balancing, events listening, endpoints discovery) - Calcite based SQL engine improvements (memory quotas, index scans optimisations). - Reworked permission management for system tasks. - Removed some deprecated functionality (daemon nodes, visorcmd, legacy JMX beans) etc. I want to propose myself to be the release manager of the planning release. I propose the following timeline: Scope Freeze: April 08, 2023 Code Freeze: April 15, 2023 Voting Date: April 22, 2023 Release Date: April 29, 2023 [1]. https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27) WDYT?
Re: JIRA Ticket - IGNITE-18875.
Thank you Ilya. -- Gael. On Wed, 29 Mar 2023 at 03:15, Ilya Kasnacheev wrote: > Hello! > > I have added you to Contributors role - you may now assign tickets to > yourself. > > Please read > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > Regards, > -- > Ilya Kasnacheev > > > ср, 29 мар. 2023 г. в 00:26, Gael Yimen Yimga : > > > Hello Ignite Community! > > > > My name is Gael. I want to contribute to Apache Ignite and want to start > > with this issue - IGNITE-18875, my JIRA username yimengael. Any help on > > this will be appreciated. > > > > Thanks! > > -- > > Gael. > > >
A Message from the Board to PMC members
Dear Apache Project Management Committee (PMC) members, The Board wants to take just a moment of your time to communicate a few things that seem to have been forgotten by a number of PMC members, across the Foundation, over the past few years. Please note that this is being sent to all projects - yours has not been singled out. The Project Management Committee (PMC) as a whole[1] is tasked with the oversight, health, and sustainability of the project. The PMC members are responsible collectively, and individually, for ensuring that the project operates in a way that is in line with ASF philosophy, and in a way that serves the developers and users of the project. The PMC Chair is not the project leader, in any sense. It is the person who files board reports and makes sure they are delivered on time. It is the secretary for the project, and the project’s ambassador to the Board of Directors. The VP title is given as an artifact of US corporate law, and not because the PMC Chair has any special powers. If you are treating your PMC Chair as the project lead, or granting them any other special powers or privileges, you need to be aware that that’s not the intent of the Chair role. The Chair is a PMC member peer with a few extra duties. Every PMC member has an equal voice in deliberations. Each has one vote. Each has veto power. Every vote weighs the same. It is not only your right, but it is your obligation, to use that vote for the good of the project and its users, not to appease the Chair, your employer, or any other voice in the project. Every PMC member can, and should, nominate new committers, and new PMC members. This is not the sole domain of the PMC Chair. This might be your most important responsibility to the project, as succession planning is the path to sustainability. Every PMC member can, and should, respond when the Board sends email to your private list. You should not wait for the PMC Chair to respond. The Board views the entire PMC as responsible for the project, not just one member. Every PMC member should be subscribed to the private@ mailing list. If you are not, then you are neglecting your duty of oversight. If you no longer wish to be responsible for oversight of the project, you should resign your PMC seat, not merely drop off of the private@ list and ignore it. You can determine which PMC members are not subscribed to your private list by looking at your PMC roster at https://whimsy.apache.org/roster/committee/ Names with an asterisk (*) next to them are not subscribed to the list. We encourage you to take a moment to contact them with this information. Thank you for your attention to these matters, and thank you for keeping our projects healthy. Rich, for The Board of Directors [1] https://apache.org/foundation/how-it-works.html#pmc-members
Re: JIRA Ticket - IGNITE-18875.
Hello! I have added you to Contributors role - you may now assign tickets to yourself. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev ср, 29 мар. 2023 г. в 00:26, Gael Yimen Yimga : > Hello Ignite Community! > > My name is Gael. I want to contribute to Apache Ignite and want to start > with this issue - IGNITE-18875, my JIRA username yimengael. Any help on > this will be appreciated. > > Thanks! > -- > Gael. >
