Dmitriy, Fully support this requirement. It took us an unreasonable amount of time to complete post-process steps for this release.
I've involved Python, PHP and Node.JS contributors into our another discussion. As for other outstanding items, please create tasks in Ignite JIRA and assign to a person who is knowledgable about a release step. I would insert JIRA tickets in the release process document highlighting who is in charge of instructions for the next release. - Denis On Tue, Jun 25, 2019 at 9:53 AM Nikolay Izhikov <nizhi...@apache.org> wrote: > +1. > > В Вт, 25/06/2019 в 11:08 +0300, Dmitriy Pavlov пишет: > > Hi Developers, and, especially, PMCs, > > > > As 2.7.5 release manager, I've faced with a number of unclear steps in > our > > process. > > > > I would like to share this talk given by Mark Thomas, the Board member: > > > > https://youtu.be/MO_AVjSPuBw?t=109 > > > > Please find 4 minutes to cover section related to release. > > > > I grateful to contributors prepared various packages, I only ask > Committers > > and PMCs to avoid accepting contributions of any entity into release, > which > > is not automated and/or documented. > > > > You can share information in our process > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process > and/or > > send a draft directly to me. > > > > Difficulties in our release process may stall the whole project. > > > > Sincerely, > > Dmitriy Pavlov >
