| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 2577.1 | I don't get it. | TOOK::MCPHERSON | Save a tree: kill an ISO working group. | Mon Mar 16 1992 20:27 | 14 | 
|  | >	After all the time and effort taken to find patches for V1.1.
Huh?  What about note 1267.* ?  Is there something I'm missing here?  A "SHOW
CONFERENCE" in here will point you to the exact note...
>	I would be gratefully if there was ONE notes entry for all
>	the patches for each BaseLevel.
We don't issue patches for FT software.  That's the point of having FT
baselevels... You issue Patches for products that have already SHIPPED and have
bugs that can't wait until the next relase to be fixed.
/doug 
 | 
| 2577.2 | see conference notice | TOOK::CALLANDER | MCC = My Constant Companion | Tue Apr 07 1992 11:40 | 3 | 
|  |     the note is also pointed to by the conference notice
    (show conference)
    
 | 
| 2577.3 | TwO entry for AMs (patches and kits) | SEDSWS::MALLOY |  | Thu Apr 23 1992 14:43 | 21 | 
|  |     The patches and Kit note entries are becoming  a mess.
    
    Each AM should have a kit note entry and patch notes entry
    eg
    		SNMP ------> snmp Am  patches
    		SNMP -----> snmp (TCPIP_Am) kit location
                TSAM -----> TSAM patches  
                TSAM------> TSAM kit location
    
    The number of AMs is growing and therefore 3.**** and 1267.****.
    I have the time or energy to go hunting for patches or kit locations.
    I have customer problems to fix
                                                                        
    Each BMS version should have a patch note entry
    	eg
    		BMS V1.1 -------> BMS V1.1 patches
    		BMS V1.2--------> BMS V1.2 patches
    
    One entry for all BMS kits
    
    
 |