Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DRAFT PROPOSAL FOR COMMENTS

The following items are expected to be completed for the project to Pass the Release Candidate Milestone.

This template must be filled out for every Release Candidate Milestone (RC0, 1, 2, x)

RC Release Candidate Milestone overview is available in wiki.

...

titleUsage

...

wiki.

...

Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre all tasks associated with the release been marked as "Done" in Jira?YesUsecase UI Backlog
Release Management
(For RC0 only) As the project team identified the reduced set of Committers who will proceed with Code Merge after RC0?Yes

Provide the name of committers. Recommendation is 3 committers max per project (1 per geographic area)?

Tao Shen

Huabing Zhao

Xin Jin



Have all findings from previous milestones been addressed?YesProvide link to JIRA findings
DevelopmentHave all Defects of priority Highest and High been in status "Done" in Jira?Yes

Provide link to JIRA issue (type bug) of priority Highest and High. 

Jira
serverONAP JIRA
jqlQueryproject=usecaseui and type=Bug and fixversion="Amsterdam Release" and Priority=High
counttrue
serverId425b2b0a-557c-3c0c-b515-579789cceedb


Are all JIRA issues used as a reference in a commit in status "Done" in Jira?Yes
Very often, some JIRA issue remains in status "Todo" in JIRA while the commit they are referenced to is successful.
Is there any pending commit
request 
related to Highest and High priority issues older than
24
36 hours in Gerrit? In case there are messages going back and forth between authors and reviewers, it is acceptable to be above 36 hours.No

Are all the Jenkins jobs successfully passed (verify + merge jobs)?Yes

Provide link to "Merge job" as evidence in Jenkins project tab

Usecase UI

jenkins job

Jenkins Job


Has the team delivered all their release artifacts in Nexus

Releases

Release or Nexus Staging repo?

There should be at least ONE version of each artifacts available in Nexus

Releases

Release or Nexus Staging repo.

In processing

Yes

Usecase UI Staging repo

Refer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?Yes
Usecase UI jenkins jobHave all end-to-end CSIT (created by Integration Team) been identified (for RC0) and passed (for RC1)?
Provide link to evidence. As things are moving fast, we want to ensure CSIT are still "green".
Is there a Docker images available for each repository?Yes

Provide link to evidence

Usecase UI docker

images

image list


Has the project code successfully passed the Daily Build process?Yes
Usecase UI jenkins job

Goal is to ensure the latest project commit has not broken the Integration Daily Build 
Documentation

For RC0, for project delivering binaries, has the team populated and validated all the sections

in the Documentation template? These information must be useful for installation, configuration, and usage.

of either the Platform Component or SDK template?


YesUsecase UI docs

Most teams have already created the high level file structures in readthedocs, and populated some actual documentation. However, the remaining sections of the appropriate teamplate must be completed.

Platform: A&AI, APP-C, CLAMP, CLI, DCAE, DMaaP, Holmes, MSB, OOM, Policy, Portal, SDN-C SDC, SO, UseCase UI, VFC, VID

SDKs: AAF, CCSDK, External API Framework, Multi VIM/Cloud, VNFSDK

For RC1, has the team addressed

to

any issue (recorded in JIRA) provided by the Documentation team?




For RC2

, have all remaining issues been addressed

, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate?




For RC2, has the Documentation Team provided the final approval for your project documentation?
In processingDocumentation Team is using ReadTheDocs for documenting user facing documentation.