Difference between revisions of "User:Aeric/Writing and Publishing Guide"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
Line 95: | Line 95: | ||
| '''Versioned ISV Release''' | | '''Versioned ISV Release''' | ||
| valign="top"| | | valign="top"| | ||
In AA Dev wiki: | |||
* Move "Release Notes" page to "Version ## Platform" | * Move "Release Notes" page to "Version ## Platform" | ||
* Activate the redirect on the release notes page | * Activate the redirect on the release notes page | ||
* Change the link that goes to the earlier-version release notes at the top of the page | * Change the link that goes to the earlier-version release notes at the top of the page | ||
* | * If needed, create the [[ISV Release Notes]] page. | ||
* Fix the [[ISV Release Notes]] redirect to point to Version ##.# Installable | * Fix the [[ISV Release Notes]] redirect to point to Version ##.# Installable | ||
* Fix the [[Installable Version Release Notes]] redirect to point to Version ##.# Installable | * Fix the [[Installable Version Release Notes]] redirect to point to Version ##.# Installable | ||
* Regenerate and re-post Javadocs to dev wiki<br>(Does not apply to LJ, due to AA-specific APIs. E.g accessProfile.) | |||
* Modify readme to correct links for the listing on the SAG "Empower" page (HTML format). | * Modify readme to correct links for the listing on the SAG "Empower" page (HTML format). |
Revision as of 22:39, 20 January 2014
Release Model
- Dated Cloud Releases
- The platform running in the cloud is updated at 2, 3, or 4 week intervals.
- When an update occurs, the features previously regarded as "Coming Soon" are added to the Release Notes, with a date to indicate when the update occurred.
- Versioned ISV Releases
- When a new "installable version" is released, a snapshot of the cloud wiki is taken.
- The snamsphot is given a version number.
- The help link in the installable version points to that wiki so that, as features evolve in the cloud, accurate help remains available for the installable version.
- Wikis
- lj_wiki -- LongJump wiki in the cloud
- lj{v#} (ex: lj100) -- Versioned LJ ISV wiki
- aa_dev (to be renamed. currently mw_dev) -- pre-release AA wiki
- aa_wiki (to be renamed. currently mw_prod) -- AA wiki in the cloud
- aa(v#} (ex: aa100) -- Versioned AA ISV wiki
- Help Links
- The help link in the cloud points to the appropriate wiki:
- AgileApps ==> http://agileappslive.info/wiki, which references the aa_wiki.
- LongJump ==> http://lj.platformatyourservice.com/wiki, which references lj_wiki.
- Help links in the installable versions point to a versioned wiki:
- AgileApps ==> http://agileappslive.info/aa100 (for example)
- LongJump ==> http://isv.platformatyourservice.com/lj100 (for example)
- (Note that the "isv" subdomain is used for the versioned wiki, to activate the "whitelabel" skin.
Procedures
The procedure to use depends on the type of activity and the target of that activity (i.e., the product it applies to).
Activity | AgileApps | LongJump |
---|---|---|
Critical Bug Fix (feature not usable) |
|
|
Cosmetic Fix (typos, wording, better text) |
|
|
New Platform Feature |
|
|
New ISV Feature |
|
|
Dated Cloud Release |
|
|
Versioned ISV Release |
In AA Dev wiki:
|
|
Publishing the AA Dev Wiki
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