Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/team/template-release-note.txt Дата изменения: Fri Oct 19 11:37:17 2001 Дата индексирования: Sun Apr 13 22:49:06 2008 Кодировка:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! this file must be named according to rules defined at: !!
!! http://www.eso.org/projects/dfs/team/integration-proc.html#note !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

==> DFS COMPONENT NAME:

==> DFS COMPONENT RELEASE NUMBER:

==> DFS RELEASE TYPE (commissioning, patch, other):

==> DELIVERED BY: ON:

==> MAIN REASON OF THE DELIVERY (patch to fix a critical bug, new release to
implement some bugs or change request, new OS, new compiler version,
new DB structure, new release to support a given instrument
dry-run, ...):




==> DEADLINE FOR DELIVERY OUTSIDE DFS GROUP (=Package deadline= deadline for
delivering the official release outside the DFS Group; this information is
essential if the release has to fix a blocking/critical bug or implement an
important change request: according to it, SEG will set the highest priority
to perform non-regression tests and prepare the delivery package).




==> CONFIGURATION REQUIRED FOR INTEGRATION TESTS (OS, VLT sofware,
libraries, ..., versions to be used, specific configuration features to
apply (e.g. a specific DB server) ...)





==> LIST AND LOCATION OF SPECIFIC TEST DATA TO BE RETRIEVED AND USED FOR
INTEGRATION TESTS (specific FITS file, Instruments Packages, frames, ...):





==> POINTS ALREADY CHECKED DURING UNIT TESTS (e.g. Purify/Quantify results):





==> POINTS TO BE CAREFULLY CHECKED DURING INTEGRATION TESTS
(specific checks, any recommendation from developer to integration tester,
...):






==> COMPLETE LIST OF ACTION ITEMS/PROBLEMS REPORTS ADDRESSED BY THIS RELEASE:




==> COMPLETE LIST OF ACTION ITEMS/PROBLEMS REPORTS WHICH ARE NOT SOLVED YET
(can be a link to a web page. Anyway, a list of SPR not solved yet, while they
should, is strongly recommended here):





==> LIST AND ISSUE OF UPDATED DOCUMENTS (User's Manual, Design document, ...):




==> ADDITIONAL COMMENTS: