parrot/parrot.github.com — Issue #6: Automate publication of documents to 'parrot.github.com' and archiving of previous documentation release in the relevant repo
Author: ayardley
Created: 2012-01-24 12:10:58+00:00
State: open

Because of the size of Parrot's historical documentation, we have had to split all of this documentation across multiple repos (see 'parrot/parrot-docs0', 'parrot/parrot-docs1', 'parrot/parrot-docs2', 'parrot/parrot-docs3', and 'parrot/parrot-docs4'). All of these documents are, now, accessible through 'parrot.github.com'. The consequence of this is, it is a'bit tricky to juggle the documentation, especially given the "old" versions of the documentation are stored in gh-pages branch of the various repos. (Though it may be possible not to use gh-pages for these repos. This is something I will test over this week.)

Presently, I am writing a 'README_release.pod' document -- to which the 'docs/project/release_manager_guide.pod' now refers for instructions on how to hand-roll all of this -- for the 'parrot.github.com' repo. This document will serve as the basis for a perl script, e.g., 'tools/release/upd_parrot_github_com_docs.pl', on which I am also presently working, to automate this process.