Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
https://www.mail-archive.com/server-dev@james.apache.org/msg70107.html
Hello there, Following the 3.6.0 release I experimented with dockerhub and pushed the following images: - apache/james:memory-3.x.x built from https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/memory - apache/james:jpa-3.x.x built from https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/jpa - apache/james:demo-3.x.x built from https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/provisioned - apache/james:cassandra-3.x.x build from https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/cassandra - apache/james:distributed-3.x.x built from https://github.com/apache/james-project/tree/master/dockerfiles/run/guice/cassandra-rabbitmq I however do not have the rights to manage the repository, hence can't add a description / overview just like apache/tika repo did. I opened INFRA-21718 regarding this. I also propose to timely edit the existing configuration to: - No longer use linagora repository for Apache James docker images distribution - Only rely on released docker images (no longer branch master) to better fit in Apache release policies [... the JIB proposition is out of scope here ...]