Patch Verification (Certified -> Verified)

As part of the EGEE Workflow (see the Developers Guide), A Product Team is responsible for Patch development up to, and including certification. As part of the QA process there is a new stage verified that must be undertaken (presently by SA3) before the patches can be signed and released into the staged rollout workflow. See also the CertificationReportTemplate. (A list of InternalPatch is maintained)

The following report should be cut n pasted into savannah


*Verification Check*
Release Notes - Y/N
Certification report - Y/N
- Installation yum log - 
- Installation YAIM log - 
- upgrade yum log - 
- upgrade YAIM log - 
Information Provider / BDII OK - Y/N
Generic node tests run - Y/N
All Bugs updated - Y/N
- Evidence of individual tests - Y/N
- New Regression tests - Y/N
EMT notified - Y/N
Licence / Copyright  - 
----
_Other Comments_:

this is presently a work in progress

Other tests that should be performed include Licence checking (see script from Francesco) and library path checks (see script from Andrew) Check in etics that there are no static dependencies (.....)

-- AndrewElwell - 12-Feb-2010

Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r10 - 2010-07-28 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback