Release Order

Definitions

Added: May have been installed previously; now expected to work

Four States

  1. C+B (Crash and Burn)
  2. Alpha--locker owners prepare to build their stuff
  3. Beta--locker owners expect to build cleanly and test
  4. Release--OUT TO THE FIELD

For each state, there are entry and exit criteria.

Crash and Burn State

To exit development and enter C+B, required software is:

  1. vendor release (includes patches required by vendor and necessary X functionality)
  2. xterm
  3. mwm
  4. twm
  5. console
  6. AFS (for Athena 8.0, this is version 3.4a (GA))
  7. Kerberos
  8. hesiod
  9. tcsh
  10. Install Process (Server, etc.)
  11. Update Process

To enter C+B, system must pass:

  1. Install
  2. Update
  3. Login

To exit C+B, required alpha software is added.

  1. C compiler
  2. a debugger
  3. zephyr
  4. motd (get_message)
  5. MH
  6. lpr
  7. attach
  8. Login
  9. Emacs
  10. rcs
  11. imake
  12. sendbug
  13. Athena Development Environment
    1. libraries (X, Motif)
    2. include files

Alpha State

To enter alpha, system must pass:

  1. alpha tests, including a make using Athena imake rules

During alpha, developers and locker owners prepare to build their stuff. In particular, we expect

  1. Andrew
  2. mkserv
  3. gnu

Also during alpha, briefings for other development team members should be provided, including:

  1. changes and problem areas in port
  2. "architecture diagrams" or other helps to orient people to peculiarities of port

To exit alpha, required beta software is added and required bug fixes incorporated.

  1. FORTRAN compiler
  2. olc (x, tty, olta, owl, olc_answers)
  3. Athena Man
  4. TeX (LaTeX, dvips, xdvi, dvi2tty)
  5. Andrew/EZ (ezviewer, ez2ascii)
  6. olh
  7. delete
  8. xmh
  9. eos, neos
  10. notes
  11. discuss, xdsc
  12. dash
  13. perl
  14. register
  15. enscript
  16. MIT libraries software
  17. SIS
  18. xscreensaver
  19. lert
  20. idle screen/pre-login motd
  21. reg_extra
  22. techinfo (x, tty) [STILL NEEDED?]
  23. xinfo
  24. xmitdir
  25. xcluster, cview
  26. moira, listmaint, mailmaint, blanche
  27. infoagents (mosaic, netscape, etc.)
  28. Postscript previewer

Beta State

To enter beta, system must pass:

  1. beta tests, including tests of alpha bug fixes.

During beta, developers and locker owners expect to build cleanly and test. In most cases, we advise locker owners to rebuild at this point to insure libraries, include files, and other changes are kept in sync.

Also during beta, Faculty Liaisons, Consultants, Documentation, Training should be provided with:

  1. question and answer meetings
  2. list of changes in port
  3. list of expected problem areas for users
  4. provide support for these groups in getting ready for port

To exit beta, required release software is added and required bug fixes incorporated.

Major Locker Software

  1. SAS
  2. Xess
  3. Maple
  4. Tecplot
  5. AutoCAD
  6. Frame
  7. Matlab
  8. S-Plus
  9. Consult
  10. netnews
  11. lotteries

Release State

To enter release, system must pass:

  1. release tests, including tests of alpha and beta bug fixes.
  2. mkserv operates correctly?

DONE!

Test plans for transitions are being developed.