get_started:release_and_maintenance
This is an old revision of the document!
Terminology discussion: "Release", "Latest", etc.
"Release"
OPNFV defined fixed set of objects and artifacts. All objects and artifacts are specifically versioned: Using the versions it must be possible to reproduce the "release" for as long as the "release" is supported by OPNFV (i.e. not deprecated).
The "release" successfully deploys on a set of reference hardware/infrastructure (see below for "reference hardware"). Successful deployment means that all tests defined for a particular release pass.
OPNFV defined set of scenario tests associated with the release
Release content:
Bootable disk image (ISO) to install the jump host
Build script which allows the creation of the above mentioned ISO
Option: Deploy script which creates an equivalent installation of what the bootable disk image (ISO) creates.
Description of the reference hardware and its configuration that the code was tested on
Description of all components/artifacts used in the release, including their individual versions (and if applicable, a reference to where these artifacts are sourced from).
Documentation (installation and user-guide, release notes, licenses used, etc.)
Description of the tests performed along with the test results.
Approved by the TSC to be an official release of OPNFV
Community supported: Collections of bug-fixes etc. will be supplied as a "maintenance release" (see below), which has the same qualities as a "release".
"Maintenance release"
Fixed set of objects and artifacts defined by a specific existing (i.e. already released) OPNFV release.
The "maintenance release" successfully deploys on a set of reference hardware/infrastructure (see below for "reference hardware"). Successful deployment means that all tests defined for a particular release pass.
"Maintenance release" content is the same as that of a "release".
"Latest"
Fixed set of objects and artifacts defined by a specific OPNFV release (existing or planned). Rather than using a specific version of a particular component, the latest available components (could be binary artifacts or sources) from upstream repositories are used.
The "latest" successfully deploys on a set of reference hardware/infrastructure (see below for "reference hardware"). Successful deployment means that all tests defined for the particular release (existing or planned) pass. Main objective of "latest" is to give developers and testers immediate feedback at system level.
OPNFV defined set of scenario tests associated with the release
"Latest" does not imply a “supported” release, rather is the “latest” working merge working towards the next target ‘release’ (future or maintenance) from OPNFV.
Does not imply anything more than Jenkins smoke-test and may/may not work (Users should be aware)
get_started/release_and_maintenance.1430924307.txt.gz · Last modified: 2015/05/06 14:58 by Frank Brockners