Number: 48

Date: 17-Mar-84  0':02':06

Submitter: Sannella.PA


Subject: Archive old <Lisp>Library> packages

Lisp Version: 

Description: '
Date': 13 MAR 84 11':56 PST'
Date': 13 Mar 84 10':39 PST'
Subject': [KMatysek.henr': Re': Archiving Trillium Releases]'
To': LispCore↑.PA'
Please arrange that the old versions of the LispUsers and Library packages be kept in {Phylum}...>OLD>... too.'
     ----- Forwarded Messages -----'
Date': 13 Mar 84 09':09 EST'
From': KMatysek.henr'
Subject': Re': Archiving Trillium Releases'
In-reply-to':''s message of Mon, 12 Mar 84 21':10 PST'
cc':, TrilliumCore↑.pa'
It sounds like what you''ve been archiving for Trillium is quite sufficient. Actually, Tim mentions a more difficult problem - saving back releases of lisp (and lispusers packages). Though this was a bigger concern in the Chorus-to-Fugue transition, it concerns me that there appears to be no careful distinction of versions with the lispusers and lisp>library files and not all of the releases get archived. Is this true? (Tim''s mention of no Chorus files on Phylum).'
In our case - since I only pull over lispusers files as we need them due to space constraints - if we need a file that goes with the previous release (since Trillium is always a bit behind the new lisp release), I can''t be assured that I''ll find the compatible file (the file on {phylum}<lispusers> may be updated for the new release, and the old one is gone). For example, Doug decided to try running Lafite about a month ago, but due to the Carol release I don''t think he was able to find all of the files that he needed. We''re now only able to run Lafite on Carol which is not compatible with Halloween. This doesn''t seem like an easy thing to control, but maybe the only solution is to keep a full copy of {phylum}<lispusers> on Aztec.'
Any thoughts?'
     ----- End of Forwarded Messages -----'


Test Case: 

Edit-By: Masinter.PA

Edit-Date: 17-Aug-84 21':47':05


Assigned To: 


Disposition: '
[Date': 14 Mar 84 19':39 PST'
Subject': AR # 48'
To': LispSupport'
You should assign System/Subsystem and (hopefully Attn) to as many AR''s if you can. This one is in "Support/Archive procedures."'
It also turns into an action item for you.]

System: Other Software

Subsystem: Release Procedure



Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Difficulty: Moderate

Frequency: Intermittent

Impact: Moderate

Priority: Hopefully

Status: Open

Problem Type: Documentation

Source Files: