Re: [DISCUSSION] Update documentation with GitHub Actions

[Maxim Muzafarov]

Hello,

+1, great improvement.

On Sat, 23 Apr 2022 at 17:26, Nikita Amelchev  wrote:
>
> Hello, Igniters.
>
> I propose to add a GitHub action to update documentation for released
> Ignite versions by a click. [1]
>
> For now, this is a complex manual work that requires understanding all
> the intermediate steps. [2]
>
> New process to update documentation:
> 1. Commit documentation changes to a released branch.
> 2. Run the action with a click.
> 3. Check the result.
>
> Moreover, this will also simplify the process of publishing a new release.
>
> ASF's GitHub Actions Policy allows automated services to push changes
> related to documentation. [3]
> Write access is required to run the workflow. So, only committers can
> run the action. [4]
>
> WDYT? Any objections?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-16895
> [2] 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85461527#HowtoDocument-UpdatingPublishedDocs
> [3] https://infra.apache.org/github-actions-policy.html
> [4] 
> https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow
>
> --
> Best wishes,
> Amelchev Nikita

Re: [VOTE] Release Apache Ignite 2.13.0 RC2

[Nikita Amelchev]

Hi Igniters, PMCs,

Please, verify a new release candidate.

The vote will continue until there are enough votes for a resolution. [1]

[1] https://www.apache.org/foundation/voting.html#ReleaseVotes

пт, 22 апр. 2022 г. в 08:24, Zhenya Stanilovsky :
>
>
> Nikita thanks for your effort !
> Download sources, run examples.
> +1 from me.
>
> >Dear Community,
> >
> >The release candidate is ready.
> >
> >I have uploaded a release candidate to:
> >https://dist.apache.org/repos/dist/dev/ignite/2.13.0-rc2/
> >https://dist.apache.org/repos/dist/dev/ignite/packages_2.13.0-rc2/
> >
> >The following staging can be used for testing:
> >https://repository.apache.org/content/repositories/orgapacheignite-1542
> >
> >Tag name is 2.13.0-rc1:
> >https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.13.0-rc2
> >
> >RELEASE_NOTES:
> >https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.13
> >
> >Complete list of resolved issues:
> >https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.13%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
> >
> >DEVNOTES:
> >https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.13
> >
> >Additional checks have been performed (available for users included
> >into the release group on TeamCity).
> >
> >TC [Check RC: Licenses, compile, chksum]
> >https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6399934
> >
> >TC [2] Compare w/ Previous Release
> >https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6399932
> >
> >The vote is formal, see voting guidelines
> >https://www.apache.org/foundation/voting.html
> >
> >+1 - to accept Apache Ignite 2.13.0-rc2
> >0 - don't care either way
> >-1 - DO NOT accept Apache Ignite Ignite 2.13.0-rc2 (explain why)
> >
> >See notes on how to verify release here
> >https://www.apache.org/info/verification.html
> >and
> >https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> >
> >This vote will be open for at least 3 days till Fri Apr 23, 2022,
> >20:00 UTC. Please, write me down the thread if you need additional
> >time to check the
> >release.
> >https://www.timeanddate.com/countdown/vote?iso=20220423T20&p0=0&msg=VOTE+on+the+Apache+Ignite+Release+2.13.0+RC2&font=sanserif
> >
> >--
> >Best wishes,
> >Amelchev Nikita
>
>
>
>



-- 
Best wishes,
Amelchev Nikita

[DISCUSSION] Update documentation with GitHub Actions

[Nikita Amelchev]

Hello, Igniters.

I propose to add a GitHub action to update documentation for released
Ignite versions by a click. [1]

For now, this is a complex manual work that requires understanding all
the intermediate steps. [2]

New process to update documentation:
1. Commit documentation changes to a released branch.
2. Run the action with a click.
3. Check the result.

Moreover, this will also simplify the process of publishing a new release.

ASF's GitHub Actions Policy allows automated services to push changes
related to documentation. [3]
Write access is required to run the workflow. So, only committers can
run the action. [4]

WDYT? Any objections?

[1] https://issues.apache.org/jira/browse/IGNITE-16895
[2] 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85461527#HowtoDocument-UpdatingPublishedDocs
[3] https://infra.apache.org/github-actions-policy.html
[4] 
https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow

-- 
Best wishes,
Amelchev Nikita