Routine Maintenance Procedures

  1. January:

  2. February:

  3. March.:
    • Development, bugs fix, features enhancement.

  4. April:
    • Development, bugs fix, features enhancement.

  5. May:
    • Development, bugs fix, features enhancement.

  6. June:
    • Development, bugs fix, features enhancement.
    • Freeze Lexicon.
    • Generate Lexicon tables from LexBuild.
    • Test new Lexicon data on lvg (Canonical, antiNorm, fruitful, etc.)

  7. July:
    • Final frozen Lexicon, try latest data on lvg.
    • Get atoms.data (from OCCS) for Canonical data.
    • Prepare lvg release
    • Prepare lvg Gui Tool
    • Prepare lvg web Tool
    • Update lvg api document

  8. August:
    • Unit test & performance test.
    • Support Metathesaurus group for testing.
    • Update lvg design document
    • Update lvg user document
    • Update lvg development web site (lexlx1).
    • Update lvg development web tool (lexlx1).
    • Finalize lvg official release (not major functionality changed should be made after this release).

  9. September:
    • Internal lvg release to OCCS, Metathesaurus group, & Apelon. This is the first version of lvg annual release, which includes new Lexicon data, latest software.
    • Support internal users for new release.
    • Deploy testing version of lvg web site (lexdev)
    • Deploy testing version of lvg web tool (lexdev)
    • Install testing version of lvg command line tools for internal users (nfsvol/nls/bin -> lexdev)

  10. October:
    • Prepare AMIA tutorial demo.

  11. November:
    • AMIA tutorial
    • lvg Documents

  12. December:
    • Final annual official lvg release to OCCS, Metathesaurus group & Apelon
    • Prepare final LEX package for official distribution.
    • Support Metathesaurus group for lvg operation (Oracle).