Hi Dmitry, According to Infra, this has to be done through http://selfserve.apache.org/, but only PMC chairs have access.
Could you please assist with the creation of the Jira project and Confluence space? -Val On Tue, Sep 21, 2021 at 10:46 AM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Infra requests created: > > - https://issues.apache.org/jira/browse/INFRA-22349 > - https://issues.apache.org/jira/browse/INFRA-22350 > > -Val > > On Mon, Sep 20, 2021 at 10:50 AM Petr Ivanov <mr.wei...@gmail.com> wrote: > >> +1 >> >> Since we've agreed that there are two projects (that are Ignite2 and >> Ignite3), separate development environments seem to be logical and natural >> course of things. >> >> > On 18 Sep 2021, at 12:42, Alexander Polovtcev <alexpolovt...@gmail.com> >> wrote: >> > >> > +1 >> > This is a welcome proposal, because we already have some pending Ignite >> 3 >> > specific documents, and it is not clear where to put them at the moment. >> > >> > On Sat, Sep 18, 2021 at 4:22 AM Valentin Kulichenko < >> > valentin.kuliche...@gmail.com> wrote: >> > >> >> Igniters, >> >> >> >> I think it's clear to all of us that Ignite 2.x and 3.x will coexist >> for a >> >> while. They are developed in separate Git repos, but we still >> accumulate >> >> the tickets for both versions in the same Jira project, which seems to >> >> complicate the ticket management. >> >> >> >> For example, we use the "ignite-3" label for 3.x tickets, but this >> approach >> >> is fragile. If someone forgets to add the label to a new ticket, it's >> >> likely to be lost. We need a better separation. >> >> >> >> All the above is true for Wiki as well - we use a single Confluence >> space. >> >> >> >> I suggest creating a new Jira project and a new Confluence space for >> Ignite >> >> 3 and moving all the relevant tickets and pages there. >> >> >> >> Any thoughts or objections? >> >> >> >> -Val >> >> >> > >> > >> > -- >> > With regards, >> > Aleksandr Polovtcev >> >>
