............................... Date: Mon, 22 Feb 1999 13:11:10 Who: Tim Conrow Subject: READ!!! Planfile deliveries Original file: /home/tab/jb.t ............................... From listmaster Mon Feb 22 13:11 PST 1999 Sender: tim Date: Mon, 22 Feb 1999 13:11:10 -0800 From: Tim Conrow To: Carol Lonsdale CC: WIRE mail list Subject: READ!!! Planfile deliveries Carol Lonsdale wrote: > > Tim - there was apparantly some delivery mistakes yesterday in SO. I'm > not clear yet [what the problem was]. In any case, it caused > Yi several hours of trouble. > > Could you figure out what happened and generate a one page summary of list of > rules for SO to follow? As I understand it, without going into the specifics of the particular event that caused Yi trouble, the problem is there's no formal planfile delivery process. Well, now there is one. Comment quickly; this will set into concrete with blinding speed. You will probably be required to use this delivery and utlilzation scheme THIS WEEK! Yi, if the proposal here looks like it burdens you too much, speak up. We'll find another way to distribute the work. Planfile deliveries ------------------- 0) Yi will be in charge of planfiles once delivered. Delivered and accepted planfiles may not be modified without here coordination and acceptance. Yi will get permission of the CCB for planfile changes and replacements. "Coordination" means Yi will confirm that the change/delivery will not disrupt any work underway by any planfile user, and that the delivered planfile meets any tests she may decide are necessary (such as basic format checks; can software read the file correctly?). 1) When a planfile author has a plan they're happy with, it goes to the pf_delivery directory specified by Yi, as is done now. 2) When a planfile change/delivery has been approved and coordinated, Yi will copy the delivered planfile to a pf_accepted directory (the location of which Yi will publicize). NO ONE MAY ALTER A PLANFILE IN PF_ACCEPTED. 3) Yi will announce the new delivery to all users. 4) ALL USERS, when using a planfile for ops work, rather than testing, will use planfiles ONLY from pf_accepted. This is a departure from current practice, where users are left pretty much to their own devices in figuring out what planfiles to read. 5) If multiple versions of planfiles must be maintained (e.g. currently in use vs. next latest and greatest) these will co-exist in pf_accepted according to a naming scheme Yi will invent and utilize. Deliverers don't need to worry about the naming scheme; Yi will apply it when delivering to pf_accepted. If users are unclear on which of the co-existing planfiles to use, the final word rests with Yi. -- -- Tim Conrow tim@ipac.caltech.edu work:626-397-9578 fax:626-397-7354