Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/to-do-list/vst-to-do-open.txt Дата изменения: Wed Jun 27 18:22:46 2001 Дата индексирования: Sat Dec 22 23:28:21 2007 Кодировка:

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

Last update: Wed Jun 27 16:22:46 MET DST 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
----------------------------------------------------------------------------------------------

0001 VST OCAM-P-M#1/2000-12-13 ACTION HIGH 2001-02-19 SB PROGRESS
Send the following documentation to OmegaCAM consortium:
- PRO dictionary
- product header generation guidelines
- QC dictionary example
- QC1LogWriter documentation & code
PROGRESS: PRO dictionary, product header generation guidelines and QC1LogWriter documentation & code
has been provided. Missing is still the QC1 dictionary example. Will be given to them at next contact
group meeting.

0002 VST OCAM-P-M#1/2000-12-13 ACTION HIGH ??? SB PROGRESS
Install OmegaCAM pipeline V0.1 on TBD machine as soon as delivered by OmegaCAM consortium.
PROGRESS: Access to OmegaCAM CVS repository was granted and first version checked out.
No tests yet done.

0003 VST mperon/Jan 2001 ACTION HIGH 2001-03-16 SB SUSPEND
Prepare HW/SW resource plan for OmegaCAM pipeline

0004 VST mperon/Jan 2001 ACTION HIGH 2001-03-16 SB SUSPEND
Prepare development plan for OmegaCAM pipeline