**********************************
* EMI Certification Report *
**********************************
- Component: FTS
- Savannah task: https://savannah.cern.ch/task/?18686
- ETICS Subsystem Configuration Name: emi-fts_R_2_2_6_3
- VCS Tag:
glite-data-agents-common_R_1_1_4
glite-data-config-service_R_2_6_7
glite-data-delegation-api-c_R_2_1_1
glite-data-delegation-cli_R_2_1_1
glite-data-sd2cache_R_1_1_2
glite-data-srm2-api-c_R_2_3_1
glite-data-srm-api-c_R_1_2_1
glite-data-srm-util-cpp_R_2_4_1
glite-data-test-utils_R_3_0_2
glite-data-transfer-agents_R_3_4_9
glite-data-transfer-cli_R_4_0_1
glite-data-transfer-fts_R_3_7_6
glite-data-transfer-interface_R_3_7_1
glite-data-transfer-proxyrenewal_R_1_0_1
glite-data-transfer-scripts_R_2_2_1
glite-data-transfer-url-copy_R_4_0_2
glite-data-util-c_R_1_3_1
glite-yaim-fts_R_4_1_11
- EMI Major Release: I
- Platform: SL5/x86_64
- Author: Oliver Keeble
- Date: 04/08/2011
**********************************************
1. CR entry exists in the release tracker with core info properly provided:
1.1. Proper component name AND version is specified [yes/no] yes
1.2. All the RfCs corresponding to the CR listed [yes/no] yes
1.3. All the RfCs are "Tested" or "Not Tested" yes
2. VCS tag available: [yes/no] yes
3. The ETICS configuration is specified in the Release Task: yes
3.1. The ETICS configuration is locked: yes
3.2. The ETICS configuration can be built in ETICS without errors: yes
4. Binary packages are available in EMI registered repo: [yes/no]
4.1. rpms [yes/no] yes
4.2. tarballs [yes/no] yes
5. Source packages are available in EMI registered repo:
5.1. rpms [yes/no] no
5.2. tarballs [yes/no] no
6. List of binary packages are specified in the tracker: [yes/no] yes
7. List of source packages are specified in the tracker: [yes/no] no
8. Licence information is provided in the tracker and the component has an "EMI-compatible" licence [yes/no/na] yes
***********
Testing
***********
9. The deployment of the new version of the product from the EMI repo
performed by the PT was succesful: yes
10. The Product Test Plan URL is specified in the Release Task: yes
11. The Product Test Report is attached to the Release Task: yes
12. The Test Report contains result/logs of :
12.1. static code analysis: no
12.2. unit tests: no
12.3. deployment tests: yes
12.4. functionality tests: yes
12.5. regression tests: yes
12.6. standard conformance tests: NA
12.7. performance tests: no
12.8. scalability tests: no
********************
Documentation
********************
13. Component Release notes are provided in the tracker [yes/no] yes
14. Are there documentation changes in this release? yes
15. If Yes, are the changes reported in the Component Release Notes? yes
16. Up-to-date Minimum Required Documentation URLs are specified in the Release Task for:
16.1: Functional Description yes
16.2: User Guide yes
16.3: Client Installation and Configuration yes
16.4: System Administrator Guide no
16.5: Service Reference Card yes
**********************************************
REMARKS:
--
OliverKeeble - 04-Aug-2011