Difference between revisions of "Live GIS Review"

From OSGeo
Jump to navigation Jump to search
Line 29: Line 29:
  
 
For completely new docs:
 
For completely new docs:
 +
* Ensure the new doc is referenced from the main [http://adhoc.osgeo.osuosl.org/livedvd/docs/en/overview/overview.html Contents page].
 
* Ensure the doc follows overview outline, as per the example doc: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/overview/en/postgis_overview.rst
 
* Ensure the doc follows overview outline, as per the example doc: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/overview/en/postgis_overview.rst
  
 
= Application Quickstarts =
 
= Application Quickstarts =

Revision as of 02:39, 30 January 2011

-- DRAFT: This page is still being developed --

This page describes our quality control processes for OSGeo-Live.

Background

OSGeo-Live has built a reputation around maintaining a high level of quality for all included applications. To ensure we maintain this quality, we need to not only test to make sure everything works as expected, but also keep track of testing status can show a clean report card on what works, and also take action when something is not working as expected.

Below are the testing and verification processes to follow for each of our artefacts:

Status Spreadsheets

OSGeo-Live applications status
Status of applications to be updated by packagers.
Translations status
Documentation translation status, to be updated by translators.

Overview Doc Checklist

Reviewing can start once authors have completed a project's Overview and set "Overview status" = latest-version_draft, in the Status spreadsheet

Reviewers checklist:

  • Check the difference between this version and last to determine what has changed.
    • Determine the version of "en" docs for last two osgeo releases (eg, between "en" and "4.0en") from the Translation summary
    • From svn directory, View updates by selecting
"doc.rst"->"revision log"-> "[View Changes]"
  • View document which should be linked from the Nightly build docs
    • Verify all images show up
    • Verify the version number matches the status spreadsheet
    • Ensure all new text is grammatically and syntactically correct.

For completely new docs:

Application Quickstarts