Premissions to upload a release to official releases directory

[Maxim Muzafarov]

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

[dmagda]

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 <[hidden email]> 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
>

[Maxim Muzafarov]

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 <[hidden email]> 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 <[hidden email]> 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
> >

[Nikolay Izhikov-2]

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 <[hidden email]> написал(а):
>
> 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 <[hidden email]> 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 <[hidden email]> 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
>>>

[dmagda]

Nikolay, thanks for offering to help with this step of the process. If
Maxim is fine then I would let you publish the artifacts.

The docs should be completed this week and we need to develop the practice
to announce releases only after technical pages are updated and available.
The vote can run in parallel. Ignite users need to have a full release
package once a release is published - binaries, Docker images,
documentation, release notes, etc.


-
Denis


On Mon, Mar 2, 2020 at 7:54 AM Nikolay Izhikov <[hidden email]> wrote:

> 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 <[hidden email]>
> написал(а):
> >
> > 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 <[hidden email]> 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 <[hidden email]>
> 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
> >>>
>
>

[Maxim Muzafarov]

Nikolay,


Thank you for offering help.
I'll back to you tomorrow.

On Mon, 2 Mar 2020 at 18:59, Denis Magda <[hidden email]> wrote:

>
> Nikolay, thanks for offering to help with this step of the process. If
> Maxim is fine then I would let you publish the artifacts.
>
> The docs should be completed this week and we need to develop the practice
> to announce releases only after technical pages are updated and available.
> The vote can run in parallel. Ignite users need to have a full release
> package once a release is published - binaries, Docker images,
> documentation, release notes, etc.
>
>
> -
> Denis
>
>
> On Mon, Mar 2, 2020 at 7:54 AM Nikolay Izhikov <[hidden email]> wrote:
>
> > 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 <[hidden email]>
> > написал(а):
> > >
> > > 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 <[hidden email]> 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 <[hidden email]>
> > 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
> > >>>
> >
> >