Date: Fri, 29 Mar 2024 07:51:47 +0000 (UTC) Message-ID: <1153981336.1474.1711698707660@759870d846b0> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1473_417797140.1711698707659" ------=_Part_1473_417797140.1711698707659 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Note: This plan was developed based on input received in the Sept 10, = 2021 Release Process Meeting
The purpose of this document is to describe how and when release artifac= ts produced from the Anuket Release Process will be hosted and published.= p>
Documentation must follow the existing Read-The-Docs organization, forma= tting, and process flow (see DOCs project). Containers must use the D= ocker format. There are no requirements or restrictions on other type= s of release artifacts.
Regardless of artifact type or format, all projects should observe the f= ollowing principles.
All release artifacts will be "accessible" to community members and end = users. This means that release artifacts will be in a widely used, op= en format that is available to most users, regardless of company affiliatio= n or region.
The documentation, updated for every release, will clearly explain the i= nstallation requirements, the installation process, and the use and operati= on of all release artifacts. The documentation will provide release-specifi= c pointers to all release artifacts.
Docker containers will be published to the Anuket registry on Docker Hub= : https://hub.docker.com/u/anuket. There are exis= ting releng jobs that may be used to facilitate this (additional details).
In addition, docker containers will be published to GitLab (following tr= ansition). This will enable projects to take advantage of security sc= anning in GitLab, and also avoid access limits in Docker Hub.
However, publishing to GitLab will only be used to facilitate Anuket bui= ld processes. Docker Hub will be the "official" registry for end user= s, and will be the location published by projects in their documentati= on.
Note that older images that are referenced in prior RC releases will con= tinue to be maintained in OPNFV in order to avoid breaking those releases.<= /p>
Other software artifacts will be published to S3. There are existi= ng releng jobs that may be used to facilitate this.
Software release artifacts will be prepared for release between M5 and M= 6 (1 week) of the Anuket release process, as follows:
The website will include a release section, or page, with subsections, o= r pages, for each release. Within the release-specific page or sectio= n will be listed links to the documentation for each participating project.= It will be the responsibility of each project to provide updated des= criptions of the installation process, including release-specific links to = release artifacts. It's important to note that the website will NOT i= nclude links to software release artifacts, but only links to documentation= .
TBD