Debian Stretch becomes debian stable (debian v9.0) later this month (6-17). Seems reasonable that future development move to debian:stretch based images instead of debian:jessie.
Current development strategy in this repo uses Makefiles to sync changes made to the base Dockerfile for each container (used for the latest tag) into the Dockerfiles for the specific versions. This was mostly for convenience during early development of those images; in general Dockerfiles will need to diverge between versions and cannot be sync'd. Also makes sense to avoid changing version-tagged Dockerfiles whenever possible anyway, now that we've established a stable pattern.
Still, it would be relatively straight-forward to get old versions building on Debian stretch, (particularly as this has already been implemented for the latest and devel images, see the stretch branch, which would give those old images the benefit of newer software (compilers etc) available on on stretch (and a longer window of security updates etc).
Looks like official images such as gcc have migrated the most recent versions to stretch while leaving older versions on jessie, so it is probably best we do likewise (prioritizing stability of older versions)
cboettig
commented
7 years ago
Debian Stretch becomes debian stable (debian v9.0) later this month (6-17). Seems reasonable that future development move to
debian:stretchbased images instead ofdebian:jessie.Current development strategy in this repo uses Makefiles to sync changes made to the base Dockerfile for each container (used for the
latesttag) into the Dockerfiles for the specific versions. This was mostly for convenience during early development of those images; in general Dockerfiles will need to diverge between versions and cannot be sync'd. Also makes sense to avoid changing version-tagged Dockerfiles whenever possible anyway, now that we've established a stable pattern.Still, it would be relatively straight-forward to get old versions building on Debian stretch, (particularly as this has already been implemented for the
latestanddevelimages, see the stretch branch, which would give those old images the benefit of newer software (compilers etc) available on onstretch(and a longer window of security updates etc).Looks like official images such as
gcchave migrated the most recent versions tostretchwhile leaving older versions onjessie, so it is probably best we do likewise (prioritizing stability of older versions)