depth: 1 adding: ((    1. Accomplishments in the past week
        * Solved the sample bugfix test question posed by Jeb.
        * Installed Visio from floppies.
        * Created a flow diagram of the Obsolete Bugfix Checkin use case
         * Hand-wrote proposed addition to initial pull-down so that it was
           completely manifest to the user how to edit the text of a bugfix
           checkin
         * Developed a "final common pathway" flow for re-submitting bugfix
           checkins that would be hooked into at two places in the original
           program flow --- the beginning from the new menu choice and when
           the entered bug # was already obsoleted
         * Presented this design and upon reflection decided that the
           man-hours for implementation could not justify such an elaborate
           implementation
         * Opted to simply move the entry of obsolescence to a new screen and
           parameterize it based on whether or not the bug was already
           obsoleted. 
        * Successfully went end-to-end after removing the "Reason for
          Obsolescence" text from PreDeleteForm.dhtml and added it to my
          new ObsoleteText.pm/.dhtml files.
           
))
depth: 2 adding: ((        1. General
            * Allow the editing of the text of already-obsoleted bug reports.
            * Automate generation of this report
            * Convert/print timesheet
            * Develop a deeper understanding of how the Web application framework
              actually works. Such an understanding is necessary if I want to
              write good error-checking and handling routines.
            
              Concomitant with the understanding, I am developing a tree of pod
              documentation for referral by me and other developers.
              
            * Implement error-checking in the newly developed ObsoleteText.pm.  
))
depth: 2 adding: ((        2. Vacations
            * None
))
depth: 2 adding: ((        3. Classes
            * None
))
depth: 1 adding: ((    2. Plans for the next week
        1. General
            * Allow the editing of the text of already-obsoleted bug reports.
            * Automate generation of this report
            * Convert/print timesheet
            * Develop a deeper understanding of how the Web application framework
              actually works. Such an understanding is necessary if I want to
              write good error-checking and handling routines.
            
              Concomitant with the understanding, I am developing a tree of pod
              documentation for referral by me and other developers.
              
            * Implement error-checking in the newly developed ObsoleteText.pm.  
        2. Vacations
            * None
        3. Classes
            * None
))
depth: 1 adding: ((    3. Outstanding issues
        * Bcc'ed mail ends up in my INBOX. Would rather it be automatically filed
          somewhere
        * Netscape doesn't remember email addresses that it should.
        * AruchkinForm.pm: how does the decode() function work?
        
            $driver_path_map =
              ARUDB::cache(
        "select decode(release_id, 999, '107', 1250, '107',
                       release_major_version || release_minor_version),
                release_id
         from   aru_releases
         where  obsolete <> 'Y' or obsolete is null");
        
        * Not sure how updates are done to the database.
))