Page Comparison

...

1. CI-CD: tools and processes
   1. Self-commit:
      1. automate Docker release version
      2. When time is critical, allow PTLs to merge their change. This should allow be applicable to LF IT (CI-Management).
   2. Increase CI-Management committers list
   3. CD: use of OPNFV Clover. Helen/Integration
2. Testing
3. Release milestones
   1. Enforcement (respect and act upon automated results): (naming and shaming if criteria not met) on TLabs starting at M2 for Casablanca.(increase lab coverage over time, over release)
      1. HealthCheck: must not be broken for more than 48 hours
      2. Use case (VFW vDNS are automated): must not be broken for more than 48 hours
      3. CSIT: must not be broken for more than 48 hours
      4. Daily Build: must not be broken for more than 48 hours
      5. What for new projects?: HealthCheck after M4
      6. Perform testing Staging and Prod env: Gary.
4. Labs and Infrastructure
   1. Resource (hardware
5. Packaging 
6. Code Coverage and License scan
7. Security
8. SLA with LF: Idea Use JIRA to prioritize tasks.

...