Table of Contents |
---|
Assumptions:
- Release, Security and Documentation scopes are now tracked via JIRA
- Adoption to “Do not break the build” principle
- No Vendor equipment is required for this release
- No new VNF requirement identified by the project team
- Jenkins Jobs Failures are monitored and fixed by the project team
- Health check and regression tests issues are reported by the Integration Team
- Project Team defines their Sprint content based on TSC prioritization to meet the delivery deadlines
- Inform TSC about any descope content post-M1 before changing FixVersion
JIRA
Jira Legacy server System Jira columns key,summary,type,created,updated,due,priority,status,resolution,epic name maximumIssues 20 jqlQuery project = CIMAN AND labels = relman AND issuetype = Epic ORDER BY updated DESC serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
M1
- Scope with jira tickets labeled i.e. “El-Alto Early Drop” (intermediate delivery) AND fixVersion El-Alto (complete scope)
...