[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4143: Refresh docker builder images
Tahoe-LAFS
trac at tahoe-lafs.org
Tue Dec 10 17:47:40 UTC 2024
#4143: Refresh docker builder images
------------------------------------+-----------------------
Reporter: btlogy | Owner: btlogy
Type: task | Status: new
Priority: normal | Milestone: undecided
Component: dev-infrastructure | Version: n/a
Resolution: | Keywords:
Launchpad Bug: |
------------------------------------+-----------------------
Description changed by btlogy:
Old description:
> We have a couple of opened tickets which requires new/updated docker
> images:
>
> - #4131 needs an update of `oraclelinux-8` to phase out python to 3.8
> (EOL)
> - #4137 needs a new `fedora-41` images to phase out `fedora-35` (EOL)
>
> I think it also makes sense to prepare new images to start
> building/testing on:
>
> - `debian-12` before phasing out `debian-11`
> - `ubuntu-24.04` before phasing out `ubuntu-20.04`
> - `oraclelinus-9` before phasing out `oraclelinux-8`
>
> I propose to PR the addition/update of those new images in the `images`
> workflow first, so we can phase the older ones in the `ci` workflow
> later.
New description:
We have a couple of opened tickets which requires new/updated docker
images:
- #4131 needs an update of `oraclelinux-8` to phase out python to 3.8
(EOL)
- #4137 needs a new `fedora-41` images to phase out `fedora-35` (EOL)
I think it also makes sense to prepare new images to start
building/testing on:
- `debian-12` before phasing out `debian-11`
- `ubuntu-24.04` before phasing out `ubuntu-20.04`
- `oraclelinux-9` before phasing out `oraclelinux-8`
I propose to PR the addition/update of those new images in the `images`
workflow first, so we can phase the older ones in the `ci` workflow later.
--
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4143#comment:2>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list