On Thu, Sep 29, 2016 at 04:45:08PM -0700, Josh Berkus wrote:
Take everyone's favorite destruction test case, PostgreSQL. For
Postgres, replication doesn't necessarily work between major versions,
so once we put out a major version we need to keep it out.
If we have a PostgreSQL-9.5.3 image on Fedora 24 Base out there, then:
A. it's OK to replace it with a PostgreSQL-9.5.4 image on Fedora 24
B. it's OK to replace it with a PostgreSQL-9.5.4 image on Fedora 25
C. it's NOT OK to drop it any only have a PostgreSQL-9.6.1 image available
I have mixed feelings about whether or not we should do (B) as policy.
In cases like this, I usually come down to: what's easier? Freezing the
base image for the major version of the application, or advancing it?
Hmmm - this seems like exactly the problem Modularity is aiming at.
One thing we can do to ameliorate that is make sure we name images
after
the major version of the app and not after the patch release, i.e. the
PostgreSQL container will be
registry.fedoraproject.org/postgresql:9.5
In the modularity terminology discussion from earlier, this'd be the
"stream". Or whatever equivalent term to that is chosen.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader