This repository has been archived by the owner on May 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 70
Handling new and end of life distro versions
James O. D. Hunt edited this page Jan 18, 2018
·
4 revisions
- EOL - end-of-life.
- OBS - SuSE's Open Build Service.
-
$version
- refers to the particular distro version the section applies to.${version}+1
refers to the next version and${version}-1
refers to the previous version.
This page captures the required process which should be triggered when either a new distro version is released, or an existing version is retired (EOL).
Currently manual - see https://github.com/clearcontainers/tests/issues/857.
NOTE: We need an automated notification for new versions and EOL versions (ideally before the event!)
For EOL versions, the tasks below will need to:
- Remove the EOL versions.
- Replace them with a "reasonable" newer version (denoted as
${version}+1
) where "reasonable" will probably be one of:- the latest version.
- the latest LTS version.
- the latest version known to support Clear Containers.
Note: the task below should be performed in the order listed.
- Raise a tracking issue and paste in this checklist section. As activities are completed, check the boxes so progress is clear.
- Raise an issue to update the install guide for the distribution.
- Raise a Jenkins issue to add a new CI Jenkins node for each repository. For EOL, also request the EOL version nodes be retired.
- Re-test osbuilder:
- On a host system running the new version.
- Specifying the new version in the
Dockerfile
(then raise a PR to update that file).
- Raise a packaging issue for new OBS packages to be created.
- Raise a test issue to test distro upgrading:
- For EOL versions, test upgrading from
${version}
to${version}+1
. - For new versions, test upgrading from
${version}-1
to${version}
. - In both cases, ensure it is still possible to create a Clear Container and that tests pass.
- For EOL versions, test upgrading from
- Review the following documents to see if any changes need to be made:
- Announce availability of new versions on the public mailing list, irc and slack.
Usage
Development
Process