not be considered as *real*, or at the minimum it will be much harder to analyse to find the actual issue.
-If your inputs are sensitive, then it is possible to create private `issues <issue tracker>`_
+If your inputs are sensitive, then it is possible to create private
+`issues <https://gitlab.com/gromacs/gromacs/-/issues/>`_
so that the developer team can have access to solve the problem, while preventing widespread
visibility on the internet.
For this testing, we use Ubuntu 18.04 or 20.04 operating system.
Other compiler, library, and OS versions are tested less frequently.
For details, you can have a look at the
-`continuous integration server used by GROMACS <gitlab>`_,
+`continuous integration server used by GROMACS <https://gitlab.com/gromacs/gromacs/>`_,
which uses GitLab runner on a local k8s x86 cluster with NVIDIA and
AMD GPU support.
introduced into the release-2016 branch since it diverged from
release-5-1. These will not appear in the final release notes, because
no formal release is thought to have had the problem. Of course, the
-tracked `issues <issue tracker>`_ remain available should further discussion arise.
+tracked `issues <https://gitlab.com/gromacs/gromacs/-/issues/>`_
+remain available should further discussion arise.
Fixed bug in v-rescale thermostat & replica exchange
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""