[interfacekit] Re: First whack at a schedule

Hey, I won't bother you about your crack prob -- er, hobby as long as
you share. ;)  I'm figuring that until we've completed design
discussions on each sub-project, the milestones are anything but set in
stone.  I'll add your stuff here to the main schedule and then I guess
we'd better get more animated in our discussions on app_server
architecture, eh? =P

Now about the registrar.  Are you referring to the MIME type
"database"?  BRoster?  What exactly?  I'm sure it'll be one of those
"Oh, THAT registrar" moments, but right now I'm drawing a blank.

e

DarkWyrm wrote:
> 
> Here's my attempt at a schedule. Some of this will probably need revision
> after M1 is complete. Don't bother telling me I'm on crack - I'm working on
> kicking the habit. ;) BTW Erik, there is one other project which has been
> neglected mention which is our baby as well - the registrar. Shouldn't be an
> excessively large project, but it does deserve mention.
> 
> App_Server schedule
> -----------------------------------------
> M1: Gathering of server tasks into basic groups (messaging, etc)
> M2: Interface specs complete for all parts of the server
> M3: Use cases complete
> M4: Unit tests complete
> M5: Design discussions complete
> M6: Can be transparently compiled as a server or as an app
> M7: Sets up own graphics modes
> M8: All necessary features to proceed to "blue screen" complete
> M9: Accepts messages
> M10: Dispatches input messages
> M11: Dispatches application messages
> M12: Can launch applications
> M13: Can kill applications
> M14: Team Monitor complete
> M15: Processes and consolidates, but does not perform, redraw messages
> M16: Graphics hook functions complete
> M17: Performs graphics updates
> M18: Alpha
> M19: Beta
> M20: Gamma
> M21: Release Candidate
> M22: Release 1.0
> 
> --DW

Other related posts: