THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
and commit changes. This step is not required if minor release was issued,e.g. 2.7.5
Post-release steps
After successful vote following actions should be done:6.3.4. Release documentaion on readme.io
Release all the documentation (Java, .NET, C++, etc.) on apacheignite.readme.io. Make sure to update a documentation's version to a version of the release.
6.3.5. Update reference to docs from site
Update the latest doc reference on ignite.apache.org:
- Update the new version number on the .htaccess file: RewriteRule ^releases/latest/(.*)$ /releases/1.9.0/$1 [L]
- Add the following tag to all .html files: <link rel="canonical" href="https://ignite.apache.org/releases/latest/LANGUAGE-DIR/FILENAME.html" />
- Use the script that automates the update or contact Mauricio Stekl (mauricio@gridgain.com) who can assist with this step.
6.3.6.
Update Ignite version in this file -Prepare HTML release notes from text release notes
Checkout SVN repository for Apache Ignite site: https://
ignitelatestFor speed up this operation make sure to limit branches in checkout operation.
Place these notes to corresponding release folder, for example releases/2.7.5
Commit changes. File should be available on the site automatically.
6.3.7. Update site with new download links
To update https://ignite.apache.org with new download links.
Update https://svn.apache.org/repos/asf/ignite/site/trunk/download.html
...
- add new release
...
- row to HTML tables
- source releases
- binary releases
- and mark
...
- prepared release as latest, if necessary; remove latest mark from previous release.
- add documentation (guide) link to readme.io docs from step 6.3.5.
Also make sure to use [preferred]/[distdir] and [disturl]/[distdir] for latest release.
Replace dist url to archive url for previous release. For example href="[preferred]/[distdir]/2.7.0/apache-ignite-2.7.0-src.zip" => href="https://archive.apache.org/dist/ignite/2.7.0/apache-ignite-2.7.0-src.zip"
Commit changes, check result at https://ignite.apache.org/download.cgi
Check provided links work fine.
6.3.8. Update version for generating users advices to update
Find latest text file in SVN repository for Apache Ignite site
Update Ignite version in this file. Commit changes and check result at https://ignite.apache.org/latest
- Mark JIRA version as released.
- Prepare the cloud images and update links to them here https://ignite.apache.org/download.cgi#docker. In addition, update the links to the images on the following documentation pages whenever is needed:
- Update Web Console docker image: https://hub.docker.com/r/apacheignite/web-console-standalone/tags/
- Delete previous releases from https://dist.apache.org/repos/dist/release/ignite/..., replace their download URLs by https://archive.apache.org/dist/ignite/...
- Upload .NET NuGet packages to nuget.org. Credentials can be found in https://svn.apache.org/repos/private/pmc/ignite/credentials/nuget.org (PMC only).
- Make sure that the artifacts were synced up to http://repo2.maven.org/maven2/org/apache/ignite/ and Maven Central. Refer to the recently happened issue (
)Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key INFRA-13073 - Announce the release by sending a single message to announce@apache.org and Ignite's user/dev lists. Refer to the examples below:
- Announce security vulnerabilities that were fixed in the release following the ASF process https://www.apache.org/security/committers.html. Check with security@ignite.apache.org if there are any vulnerabilities.
...
Overview
Content Tools
Apps