Understanding solved issues in Running releases of Docker-mailman
Newbie-question: This is more or less a GitHub / GitLab question, but specific to Mailman.
Now using Running releases<https://github.com/maxking/docker-mailman/blob/master/README.md#rolling-rele...> of Docker-mailman (and in general using Docker-mailman), I am wondering, how I can tell which issues having been solved in each release?
My goal is to understand when issues like (currently, but not limited to) Mailman-core issues #256<https://gitlab.com/mailman/mailman/issues/256>, #322<https://gitlab.com/mailman/mailman/issues/322>, #359<https://gitlab.com/mailman/mailman/issues/359> (all which states Closed in the Mailman-core Issue log) and Mailman-core issues #406<https://gitlab.com/mailman/mailman/issues/406>, #410<https://gitlab.com/mailman/mailman/issues/410> and MR !322<https://gitlab.com/mailman/mailman/merge_requests/322> (which all states Open) have been solved and included in the Docker-mailman latest running release and normal release.
I pulled the latest Running release<https://github.com/maxking/docker-mailman/blob/master/README.md#rolling-rele...> today, but as I have never been able to recreate the problems (above stated issues) my users experienced on several lists, I would like to make sure they have been solved, before I make a new attempt migrate my Mailman 2 lists to Mailman 3.
-- Henrik Rasmussen <her@adm.ku.dk<mailto:her@adm.ku.dk>> University of Copenhagen, Danmark
On Fri, 2017-11-24 at 09:40 +0000, Henrik Rasmussen wrote:
Newbie-question: This is more or less a GitHub / GitLab question, but specific to Mailman.
Now using Running releases<https://github.com/maxking/docker- mailman/blob/master/README.md#rolling-releases> of Docker-mailman (and in general using Docker-mailman), I am wondering, how I can tell which issues having been solved in each release?
Running releases are built weekly (and with every commit to docker-mailman repo), and use the git heads from gitlab for *all* the components.
To be more specific, you can get the commit version for each component and check that in the git tree to find out if any particular issue is fixed before that.
You can use docker inspect as mentioned in the docs to get the commit version.
My goal is to understand when issues like (currently, but not limited to) Mailman-core issues #256<https://gitlab.com/mailman/mailman/issues/256>, #322< https://gitlab.com/mailman/mailman/issues/322>, #359<https://gitlab.com/mailman/mailman/issues/359> (all which states Closed in the Mailman-core Issue log) and Mailman-core issues #406<https://gitlab.com /mailman/mailman/issues/406>, #410<https://gitlab.com/mailman/mailman/issues/4 10> and MR !322<https://gitlab.com/mailman/mailman/merge_requests/322> (which all states Open) have been solved and included in the Docker-mailman latest running release and normal release.
It is unlikely that the open issues are solved in the container images, but I'd have to try to reproduce #406 and #410 before I say more why they don't work.
I pulled the latest Running release<https://github.com/maxking/docker- mailman/blob/master/README.md#rolling-releases> today, but as I have never been able to recreate the problems (above stated issues) my users experienced on several lists, I would like to make sure they have been solved, before I make a new attempt migrate my Mailman 2 lists to Mailman 3.
If it is fixed in master branch, it should be fixed in rolling release (atleast, within a week).
Hope that helps!
thanks, Abhilash
participants (2)
-
Abhilash Raj -
Henrik Rasmussen