Anuket Project

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 »

NameDescriptionOwned byPrerequisitesNotes
Name and version the release

Release naming scheme
Release versioning scheme

Heather has recommended a unified release name.
Specification reviewNeed a process for reviewing and providing feedback to RM an RA specifications prior to publication.
Specification review process
Code archive and configuration management

Code archive
SCM

Issue trackingNeed to be able to document and track requirements, bugs, tasks, etc.
Bug tracking systemOPNFV previously used Jira
Project release planPlan submitted by each participating project that describes what the project plans to accomplish, how the work will be tested, what documentation will be produced, and what artifacts will be released.
Release Plan templateShould we use the same template that was used for OPNFV Iruya?
Requirements planningWe need to agree as a project on which RM and RA requirements we will implement for a release. In addition, there may be other requirements, such as the Python 3 migration, that we may want to accomplish for a release.
Requirements planning processFor OPNFV Iruya, we had the idea of a requirements working group, which was a combination of TSC members and PTLs. 
Dependency planningWe need to agree as a project on which versions of major upstream dependencies (e.g., Functest, Openstack, Kubernetes, etc.) we will use
Dependency planning process
Project documentationIndividual projects have installation, programming, and user documentation.  
Documentation planThis documentation currently exists in OPNFV repos.  How will we bring it into Anuket? Will we release unified documentation?
RI & RC documentation

Documentation plan
RC validationRC conformance to each RA must be validated
RC validation plan
RI validationRI conformance to each RA must be validated
RI validation plan
Self ReleaseProjects that do not contribute directly to RC/RI will self-release.
Self-release process
Release artifact hostingHow will release artifacts be made available for distribution? 
Release artifact hosting planOPNFV artifacts were available from a download page.  Do we want to do this, or something else?













































  • No labels