Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/team/delivery-proc.html
Дата изменения: Wed Apr 13 18:07:49 2005
Дата индексирования: Sun Apr 13 22:48:58 2008
Кодировка:
DFS group delivery procedure
 [ ESO ]

DFS Department
DFS delivery process



For every new DFS component delivery, following process should be applied. It should involve different DFS Department roles (DFS Department Head, SEG members, DFS Department projects managers or developers, DFS QA manager) and ESO project scientists or representative end-users.

The delivery process must be preceeded by the integration process. The delivery process must start only when the latter has been performed. A delivery process encompasses following steps:

The delivery package preparation

The delivery package preparation :


Go to top of page

The Delivery Note

The Delivery Note is the text file to be sent to the mountain by email giving all detailed information about the new DFS patch or release, plus the specific installation instructions to be applied by the mountain. The Delivery Note file is named:
It also has to be archived via webcheck by the SEG member responsible for preparing the delivery package. It is then automatically published on the web: see here.
This file contains following information:



Go to top of page

The Delivery History file

In order to trace every delivery prepared by SEG, a text file called 'dfs-delivery-history.txt' has also to be updated and archived via webcheck by the SEG member responsible for preparing the delivery package. It is then automaticly published on the web. See following page.
This file gives an history of ALL previous deliveries (sorted by reverse chronological order: last one first), while the Delivery Note is specific to one patch (or one DFS release) only. The Delivery History file contains following information:
The Delivery History file will then give, for every delivery, a complete description of its content, and progress information about the way installation has actually been performed on-site.


Go to top of page

Delivery kick-off meeting

A special meeting should take place just before starting the actual delivery. Participants should be:

Topics to be discussed:

Minutes are done by the DFS QA manager.


Authorization for sending delivery packages to the mountain

A delivery package must be sent to the mountain only if:
For packages sent to the mountain, the SEG member responsible for preparing it must get progress information in order to accordingly update the Delivery History file.


the DFS commissioning process

These steps are fully described in following link.


Delivery ending meeting

A special meeting should take place after the delivery has been performed. Participants should be:

Topics to be discussed:

Minutes are done by the DFS QA manager.


Go to top of page


 [Project and Developments]  [Overview page for this document]  [ESO]  [Index]  [Search]  [Help]  [News]