Re: Maintaining documentation consistency on readme.io

. As >>> discussed in this email thread below, please DO NOT create any new version >>> of the document until the release. If you want to add any new document >>> pertaining to the next release, create it within the document for the >>> current version and keep

Re: Maintaining documentation consistency on readme.io

Prachi: https://apacheignite.readme.io/v1.6/docs/aop-based-grid-enabling this doc is missing in the 1.7 version. 在 16/8/26 02:50, Prachi Garg 写道: Right! On Thu, Aug 25, 2016 at 10:28 AM, Dmitriy Setrakyan wrote: Got it. So essentially you are proposing to make the

Re: Maintaining documentation consistency on readme.io

Changes to the existing pages will still have to be copied manually; but since we are not maintaining two versions (current and future) at the same time, it may be a lesser overhead. Once a new version is released, we hardly go back to the previous versions to fix anything. -P On Wed, Aug 24,

Maintaining documentation consistency on readme.io

Igniters, Since readme.io does not automatically copy the changes from the current version to the subsequent version, I have the following suggestion: Create the document for future releases within the document for the current version, and keep the pages hidden. After the new release, create the