I thought documentation can be updated after the release. Isn’t it? > Is there anybody who can do that?
I can do it. > 2 марта 2020 г., в 18:44, Maxim Muzafarov <mmu...@apache.org> написал(а): > > Denis, > > Thank you, I think yes. > But I don't expect that the release will be delayed since we still > need some time for documentation preparation. > > On Mon, 2 Mar 2020 at 18:40, Denis Magda <dma...@apache.org> wrote: >> >> Hi Maxim, >> >> This sounds like an option but can take delay the release for more than a >> week. Alternatively, someone from the PMC group can execute this step for >> you. Is there anybody who can do that? >> >> - >> Denis >> >> >> On Mon, Mar 2, 2020 at 6:21 AM Maxim Muzafarov <mmu...@apache.org> wrote: >> >>> Ignite PMCs, >>> >>> >>> Hopefully, if not the current release voting, but one of the next one >>> get success soon we'll get the 2.8.0 release candidate accepted. >>> >>> To execute the next release scripts for an accepted release candidate >>> (release_*.sh from a release archive) I need some permissions to >>> upload a release candidate to official release directory. According to >>> Apache documentation [1]: "The PMC can also vote to let >>> non-PMC-members update the dist/release area. To get this set up, >>> please open a JIRA ticket at the INFRA JIRA referencing the PMC vote." >>> >>> As the release manager of Apache Ignite 2.8, I ask your help if you >>> consider it necessary to give me the required agreement for upload >>> release. After that, I'll file a JIRA ticket to INFRA. >>> >>> >>> [1] http://www.apache.org/legal/release-policy.html#upload-ci >>>
