Difference between revisions of "User:Aeric/Writing and Publishing Guide"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 13: | Line 13: | ||
|- | |- | ||
| Minor | | Minor Fix or<br>Cosmetic Improvement | ||
<br> Cosmetic | |||
| | | | ||
* | * | ||
| Line 24: | Line 23: | ||
| | | | ||
* | * | ||
| | |||
* "Coming soon" entry, docs, link from docs | |||
|- | |||
| Dated Release | |||
| | | | ||
* | * | ||
| | |||
* | |||
|- | |||
| Versioned (ISV) Release | |||
| | |||
* | |||
| | |||
* | |||
|} | |} | ||
Revision as of 19:42, 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 ImprovementNew Feature - "Coming soon" entry, docs, link from docs
Dated Release
Versioned (ISV) Release
New Features
- Document new features in the Dev wiki
http://agileappslive.info/mw_dev - 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 - 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:
- Find and fix all transclusions of Template:TBD
- In the dev wiki, change the Coming Soon heading to reflect the release date.
http://agileappslive.com/mw_dev/Platform_Features - Leave unimplemented entries under Coming Soon or, if there are none, comment out that section
Publication:
- Using PuTTY, log in to the Rackspace server
- 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