Skip to end of metadata
Go to start of metadata

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.


Practice AreaCheckpointYes/NoEvidence - CommentHow to?
Product Management

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

N/AVNFRQTS does not produce APIs


Is there a final list of externally consumable APIs available?N/AVNFRQTS does not produce APIs

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

YesLink to Project backlogDifference between a Product and Sprint Backlog

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

YesLink to Project backlog
If applicable to your project, has your team been able to clear the project' blockers? If not provide status on the plan to close the blocker(s).N/AVNFRQTS project not found in blockers pageLink to blockers.
Release Management

Have all source code files been updated with License Apache 2 header?N/AVNFRQTS does not produce APIs
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)N/AVNFRQTS does not produce APIsGuidance 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?N/AVNFRQTS does not produce codeGuidance for source code file that can't be edited
Has the project FOSS Table been updated with latest third party code?N/AVNFRQTS does not produce APIs
Do you have a plan to address any issue raised by Fossology?N/AVNFRQTS does not produce code
DevelopmentFor new projects approved for this release, have all defined repositories source code been placed into Gerrit?Yes

all seed documentation available in vnfrqts/guidelines repo

and visible at onap.readthedocs.io

VNFRQTS-15

VNFRQTS-19

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)N/A

Goal: 30-50% for Incubation project

VNFRQTS does not produce code

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?NoVNFRQTS does not produce codeRefer 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.YesVNFRQTS-54
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

the deliverables from VNFRQTS are documentation that is collected by the Jenkins job controled by teh documnetation project and publishing to ONAP.ReadtheDocs.io

Are all snapshot binaries available in Nexus?YesProvide link to evidenceThis projects does not produce binaries in nexus, rather it produces documentation available at onap.readthedocs.io
Integration and Testing  Have functional test cases been documented in wiki?N/AVNFRQTS does not produce APIsVNFs may provide documentation indicating their degree of support for the VNF Requirements.
Have you implemented in Jenkins at least 1 functional test case for each of the project repository?YESJenkins job for all ONAP documentation is controlled by the documentation project .

As an example (provided by Integration Team)

The documentation jenkins job has a verify function testing for valid .rst format

Has the project code successfully passed the Build process?YESBuild process for documentation is Sphinx→ onap.readthedocs.io

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?Yes

VNFRQTS Documentation Structure

VNFRQTS<> Documentation project Workflow

AMsterdam release components are the VNF Guidelines and the VNF Requirments available at onap.readthedocs.io

5 Comments

  1. Steven Wright Could you update template above and Provide link to evidence in Nexus project folder? Thanks.

  2. Steven Wright on the question "For new projects approved for this release, have all defined repositories source code been placed into Gerrit?" I can see in Gerrit some repos (epics,testcases,usercases) are still empty? What is the plan to have content in these repos?

    1. I expect no code into these repos in the Amsterdam release.  Amsterdam release is focussed on the VNF Guidelines and VNF Requirements deliverables. 

  3. Steven Wright on the question "Have all the Jenkins jobs successfully passed (Merge-Jobs)?" I do not see any jobs in Jenkins at https://jenkins.onap.org/view/vnfrqts// Ideas?

  4. the Verify task associated with jenkins is blocking. LF tech support has been engaged. see also bug report at VNFRQTS-75