Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

DRAFT PROPOSAL FOR COMMENTS

The following items are expected to be completed for the project to Pass the M2 Functionality Freeze Milestone.

M2 Release Functionality Freeze Milestone definition.


Usage

  1. Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
  2. Fill out the Yes/No column
  3. Provide link to evidence (when necessary)
Practice AreaCheckpointYes/NoEvidence - CommentHow to?
Product Management

Are all provisional APIs interface (stub) been defined (at beta-quality level)? 




Is there a final list of externally consumable APIs available?
Provide link to evidence

For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira?

YesAPPC Project backlogDifference between a Product and Sprint Backlog

Are all tasks associated with the completed Sprint Backlog Stories been marked as "Done" in Jira?




Release Management

Have all source code files been updated with License Apache 2 header?

Specific rules and instruction are available in ONAP wiki.
Has the year format in copyright header of all source code files been updated? (Rules for new files created in 2017 and existing files modified in 2017 are different)

Guidance on year format
In case source code can't be edited, has a "License.txt" file been placed at the root directory for which the license is applicable?

Guidance for source code file that can't be edited
Has the project FOSS Table been updated with latest third party code?
Provide link to evidenceYour project FOSS table is located under Project FOSS master page
Do you have a plan to address any issue raised by Fossology?Yes
If any issues arise with Fossology, they will be addressed

Have all API projects dependencies been captured?

YesProvide link to the "API Incoming Dependency" section within your project M1 Release Planning deliverable.The source of information for the API dependency is the "API Incoming Dependency" of the M1 Release Planning deliverable. Please update the source accordingly, and let The Release Manager aware of the changes.
DevelopmentFor new projects approved for this release, have all defined repositories source code been placed into Gerrit?N/A

Provide link to evidence

For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this example

Example

Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)No, this is work in progressGoal: 30-50% for Incubation project

Guidance on Code Coverage and Static Code Analysis

Tools: Sonar

Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository?Yes
Refer to CI Development Best Practices
Could you ensure that all proprietary trademarks, logos, product names, company name, etc. have been removed? All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.No
This item is currently under discussion between AT&T Legal & LF Legal
Is there any pending commit request older than 36 business hours in Gerrit?No

Have all the Jenkins jobs successfully passed (Merge-Jobs)?YesProvide link as evidence to Jenkins project tab

https://jenkins.onap.org/view/appc/

Are all snapshot binaries available in Nexus?YesProvide link to evidence in Nexus project folderhttps://nexus.onap.org/content/repositories/snapshots/
Integration and Testing  Have functional test cases been documented in wiki?In ProgressProvide link to evidence
Have you implemented in Jenkins at least 1 functional test case for each of the project repository?
As an evidence, provide a link to Jenkins (CSIT Jobs) that shows a sample test case implemented (1 job for each repo).

As an example (provided by Integration Team)


Has the project code successfully passed the Build process?

Goal is to ensure your project latest commits have not broken the build.

DocumentationHas the team identified and outlined the set of documentations to be delivered in this Release?


  • No labels