AgileApps Support Wiki Pre Release

Difference between revisions of "User:Aeric/Writing and Publishing Guide"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 15: Line 15:
| Minor Fix or<br>Cosmetic Improvement
| Minor Fix or<br>Cosmetic Improvement
| valign="top"|
| valign="top"|
*
* Modify the AA page.
| valign="top"|
| valign="top"|
*
'''''When an equivalent AA page is reorganized:'''''
* Reflect the reorg in the LJ wiki to ensure that future changes can be made without difficulty.
 


|-
|-

Revision as of 20:35, 20 January 2014

Procedures

The procedure to use depends on the type of activity and the target of that activity.

Activity AgileApps LongJump
Critical Bug Fix
Minor Fix or
Cosmetic Improvement
  • Modify the AA page.

When an equivalent AA page is reorganized:

  • Reflect the reorg in the LJ wiki to ensure that future changes can be made without difficulty.


New Feature
  • Add to wiki
  • Add a "Coming soon" entry w/link to docs

(There is no "pre-release" wiki.)

Dated Release


Versioned (ISV) Release

New Features

  1. Document new features in the Dev wiki
    http://agileappslive.info/mw_dev
  2. Put a Coming Soon entry into the platform features page, with a Learn More link to that documentation:
    http://agileappslive.info/mw_dev/Platform_Features
  3. When that entry is good enough for use, copy it to the production wiki (minus the Learn More link):
    http://agileappslive.info/wiki/Platform_Features

Publication Process

First, prepare the development wiki for publication. Then execute the publishing process.

Preparation:

Publication:

  1. Using PuTTY, log in to the Rackspace server
  2. Run scripts/publishDevWiki to copy the contents of the
    development wiki (mw_dev) to the production wiki mw_prod
    This process makes a backup of the production wiki.
    If there is ever any need to revert to a previous version,
    run scripts/restoreWikiInstructions for a list of steps

Backup Process

User:Aeric/Backup

Versioning Process

User:Aeric/Version