THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
6.3.2. Update sources snapshot version in the master branch
Execute the script from Ignite project root directory, this will update version in the master branch :
...
and commit changes. This step is not required if minor release was issued,e.g. 2.7.5
6.3.2.1 Update sources snapshot version in the ignite-extensions repository
The dependency of ignite-extensions must be updated according to the new version in the master branch.
See the example below:
Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key IGNITE-13993
6.3.4. Publish technical documentation
Publish the technical documentation on the website: How to Document - Publishing to the website
6.3.5. Update references to API docs on the website, SEO updates
Update the latest APIs doc reference on ignite.apache.org:
- Update the new version number on the .htaccess file: RewriteRule ^releases/latest/(.*)$ /releases/2.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.
- Commit changes to the GIT.
This script do some Search engine optimization (SEO) updates to new/old .html files, like adding NOINDEX metatag to older version; add canonical URL to latest docs; and add GA code.
6.3.6. Prepare HTML release notes from text release notes
Checkout GIT repository for Apache Ignite site: https://gitbox.apache.org/repos/asf/ignite-website.git
Just copy-paste latest release notes from previous release, replace text formatting with headers, lists items.
Place these notes to corresponding release folder, for example releases/2.7.5. If folder is absent, check results of step 6.2.3.
Commit and push changes. File should be available on the site automatically.
...
Overview
Content Tools
Apps