Mixminion release criteria (draft)

[Nick Mathewson <nickm@alum.mit.edu>]

Hi, all!  I wrote this list of draft release requirements last night. 
If everybody thinks this is a good start, I'll check them in, and we can
edit them from there.

My goal here is to make sure that we don't release a half-finished
specification or implementation.  Remember, this needs to be usable; we
can't leave things as an 'exercise for the user.'

Here are the Milestones I list below:
    SPEC: The specification is done enough to implement.
    DOC: The rest of the spec and documentation is done.
    ALPHA: The first alpha of the implementation is ready to release.
    BETA: The implementation is feature-complete.

SPEC:
	- The main protocol is specified.
	- Dummy traffic is specified.
	- All client operations are specified.
	- MMTP/SSL is fully specified.
	- Node status queries are specified.
	- Fetching node lists is specified.
	- We have a "transition plan" from MixMaster 2. (maybe?)
	- We have specifications for several 'delivery' formats,
          including compression, fragmentation, SMTP delivery,
          NNTP posting, and 'relay to a local alias.'

DOC:
	- We have a complete design document, separate from the 
          specification.
	- We have complete user-level documentation, and API 
          documentation for our client libraries.

ALPHA:
	- Implementation of all relay features, but not necessarily 
          all delivery mechanisms.
        - Implementation robust against hostile inputs from network.
	- Simple command-line clients for all client features.

BETA:
        - Robust against future server compromise (e.g., nothing  
          dangerously swapped to HD.)
	- Efficient implementation.
	- Usable clients, and client libraries for integration with 
          mailers.
	- Clients run on Windows, Unix, Mac.

What have I missed?  What's too much of a reach?
-- 
Nick