On 03-Oct-17 03:58, Abhilash Raj wrote:
The container images have stable releases of Mailman components, so those changes will make in to the container when a new Core release happens.
The next image release is pending a version upgrade of Hyperkitty, to 1.1.3, but other changes are just meant to make the process of setting up Mailman better. They do not include changes from git repo after the release.
Considering the evolving state of MM3, the complexity of installing it, and the problems that people have trying to use it for testing/production: you might consider packaging an 'unstable' Docker version from git 'head', perhaps weekly. Building it ought to be something that you can script...and a regular cycle would give developers a target for merges.
This would get you early testing & would help those trying to be early adopters - waiting months for the next point release will turn off the enthusiasm.
FWIW
.