I believe we want to keep copy of the version docs in the website SVN? You can take a look at Flink website example [1].
So it splits the doc into generic information, stored in that svn, and release specific that stick with src [2] . For each release we add versioned doc in the SVN "site/docs" directory as new directory for each version. - Henry [1] https://svn.apache.org/repos/asf/flink [2] git://git.apache.org/flink.git On Wed, Jan 21, 2015 at 12:18 PM, Dmitriy Setrakyan <[email protected]> wrote: > Additionally, I wanted to find out if any one has any experience having > "versioned" documentation. For example, in GridGain, every time we do a new > release, we create a copy of our documentation space for the new release > and make changes there. This way we have a separate documentation space for > every GridGain version. > > How is documentation versioning generally handled in Apache? Can we just > continue to have a space per version? > > D. > > On Wed, Jan 21, 2015 at 11:53 AM, Dmitriy Setrakyan <[email protected]> > wrote: > >> Hi, >> >> Just wanted to let everyone know that I have filed INFRA ticket to do the >> initial import of the GridGain Open Source documentation into Apache Ignite >> space on Apache confluence wiki: >> >> https://issues.apache.org/jira/browse/INFRA-9048 >> >> Let's hope this can be done. >> >> D. >>
