Marek Skalický

Good point. Because we almost every time release (rebase to upstream) all images together, so there is no reason to test changes to already released s2i-base. I'll try change CI...

@bazulay How it should work? (linux containers are very specific environments)

(I'm taking this issue as general discussion about all our images. If it wasn't meant so, then I'm sorry. Development of postgresql image is one of "the most active" ones,...

> Well, the question is whether we shouldn't do something about it -- namely, whether we shouldn't delay the release the new version of CentOS images till RHEL images are...

> I'm not sure I understand this. What implies that we should change sources for every build? Build only when base image is released (same as for RHEL now) ->...

So minor version should be increased by every commit with NEWS entry? Or it was meant that not for every build but for every build where sources changed? If so,...

> Not really. Minor version should be bumped if something is worth having added to NEWS entry, and we already released all the previous set of changes. So first commit...

> Well, I don't want to sound too definitive ... we are just discussing, and I'm just presenting what I personally feel is natural if we were about to maintain...

LGTM. I like a way how to configure the image. And I think there should be no problem with this... I also think it should be good to allow/document users...

@aliscott Whats you experience with mongodb+glusterfs?