Routine Maintenance Procedures

1. January:
   • None

2. February:
   • None

3. March.:
   • Create a new project in SCRT for the next release of TC
   • Create a new TC baseline for the next release
   • Generate tables for JDI and STI
   • Development, bugs fix, features enhancement

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

5. May:
   • Update TC API document
   • Update TC design document
   • Update TC user document
   • Update TC web site
   • Update TC web tool
   • Deliver TC official release
   • Install TC command line tools for internal users (nfsvol/nls/bin -> lexdev)
   • Officially deploy TC public web site (lexsrv3).
   • Officially deploy TC public web tool (lexsrv3).

6. June:
   • None

7. July:
   • None

8. August:
   • None

9. September:
   • None

10. October:
    • None

11. November:
    • None

12. December:
    • None