This is an automated email from the ASF dual-hosted git repository. rouazana pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/james-project.git
commit 3ed970f33975b24977f21ecd0f110735297a3e49 Author: Antoine DUPRAT <[email protected]> AuthorDate: Fri Aug 30 09:22:18 2019 +0200 Post about latest docker images --- .../_posts/2019-08-30-latest-image-changes.markdown | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/src/homepage/_posts/2019-08-30-latest-image-changes.markdown b/src/homepage/_posts/2019-08-30-latest-image-changes.markdown new file mode 100644 index 0000000..be8ac52 --- /dev/null +++ b/src/homepage/_posts/2019-08-30-latest-image-changes.markdown @@ -0,0 +1,21 @@ +--- +layout: post +title: "Apache James `latest` Docker images changes" +date: 2019-08-30 09:09:47 +0100 +categories: james update +--- + +We have decided to change the `latest` Docker images behaviour. + +Until nowadays, such images were built on the `master` branch for each products (`linagora/james-memory`, `linagora/james-cassandra-rabbitmq-ldap-project`, ...). +This is not the way `latest` docker image should be, this [blog post](https://blog.container-solutions.com/docker-latest-confusion) is explaining this kind of misunderstood. + +So we decided to follow the global Docker users behaviour which is to clone the _latest stable release_ as the Docker `latest` images. + +For those of you who are willing to use a Docker image on top of the master branch, you can use the newly created `branch-master` tag, +which is published on each merge on the master branch. + +NB: you should not use the `latest` image in a production deployment, otherwise you are at risk of jumping from one major release to another unexpectedly. + +Thanks for reading, +Antoine \ No newline at end of file --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
