Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/to-do-list/saf-to-do-open.txt Дата изменения: Tue Apr 24 18:00:08 2001 Дата индексирования: Sat Dec 22 23:28:18 2007 Кодировка: Поисковые слова: http astrokuban.info astrokuban

================================
* LIST OF OPEN ACTION ITEMS *
================================

Last update: Fri Mar 23 13:20:02 MET 2001

----------------------------------------------------------------------------------------------
ID Chronological number (to be updated manually).
Comp Name of the DFS project or component (SAF, VCSOlac, FrameIngest, DO, RBS,
-pipe, ...). In most of the cases, it's enough to have a To-Do list
per DFS project (e.g. SAF). However, project managers may decide to have a
To-Do list per component, if appropriate.
Origin Meeting name/review/date during which the action item was originated.
Type ACTION= for a normal action item;
BUG= for an item related to a bug report;
CHANGE= for an item related to a change request.
Prior Priority= LOW, HIGH, CRITIC
DueDate Either a specific date (YYYY-MM-DD) or a specific new release (in that case,
corresponding date has to be specified in associated DFS component schedule).
Resp Responsible name; even if several persons can be involved in the action item, one
should be responsible for follow-up.
Status INIT= to be started; SUSPEND= suspended, waiting for external inputs;
PROGRESS= action in progress.
Description
Detailed description. For BUG and CHANGE, specify the SPR number and a short
description: the complete description of the SPR must be found in Action Remedy.

----------------------------------------------------------------------------------------------
ID Comp Origin Type Prior DueDate Resp Status
Description
----------------------------------------------------------------------------------------------
0003 APE ? ACTION HIGH ? JKN PROGRESS
Improve handling of timeouts + killing of remotely/locally running processes.
---
0009 Previews internal ACTION HIGH 01-Mar-2001 AWI PROGRESS
produce previews for FORS1 imaging
---
0010 SAF/DB_RD internal ACTION LOW 01-Jul-2001 AWI PROGRESS
top level build 1 requirements document for SAF/DB
priority has been lowered due to other actions
---
0011 SAF/DB_DD internal ACTION HIGH 01-Aug-2001 AWI PROGRESS
design document for build 1 of SAF/DB
priority has been lowered due to other actions
---
0012 SAF/APE internal ACTION HIGH 15-May-2001 AWI PROGRESS
write APE wrappers
---
0017 SAF/FTT internal ACTION HIGH 01-Mar-2001 AWI PROGRESS
get requirements/implementations for specific FTT
to be used after closing of action 0013
---
0019 SAF/OPSLOG internal ACTION HIGH 05-May-2001 AWI PROGRESS
Define strategy for opslog DB: hardware, Sybase, interfaces
0020 EIS/Rel internal ACTION HIGH
10-May-2001 AWI PROGRESS
Re-Release of EIS deep data