Page History

6.3.4. Release documentaion on readme.io

Release all the documentation (Java, .NET, C++, etc.) on https://apacheignite.readme.io/docs

If you don't have persmission to edit docs, request permissions on the dev.list. If you get permissions go to admin panel https://dash.readme.io/nite. 

Select project, find versions dropdown, select 'Manage versions'.

If verison is not created before: Click 'Create version', enter release number, prefix 'v' is not required. During process of creation you will be asked which version is to be used as base (fork) version. Enter version base release there.

If version exists, click to main version.

Repeat this process for all documentation projects for Ignite: Java, C#/.NET, C++, SQL, Integrations*, Ignite for Spark, Tools.  Create version 

6.3.5. Update reference to docs from site, SEO updates

Update the latest doc reference on ignite.apache.org:

1. Update the new version number on the .htaccess file: RewriteRule ^releases/latest/(.*)$ /releases/2.9.0/$1 [L]
2. Add the following tag to all .html files: <link rel="canonical" href="https://ignite.apache.org/releases/latest/LANGUAGE-DIR/FILENAME.html" />
3. Use the script that automates the update or contact Mauricio Stekl (mauricio@gridgain.com) who can assist with this step.

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 SVN repository for Apache Ignite site: https://svn.apache.org/repos/asf/ignite/site/trunk

For speed up this operation make sure to limit branches in checkout operation.

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 changes. File should be available on the site automatically.