Better explain testing dashboard in Stackspin

README.md

@@ -154,11 +154,20 @@ might behave differently in the local development environment compared to a
 regular Stackspin instance, i.e., one that's not a local/cluster hybrid. In
 this case, you'll want to run your new version in a regular Stackspin cluster.
 
-To do that, make sure to increase the chart version number in `Chart.yaml`, and
-push your work to a MR. The CI pipeline should then publish your new chart
-version in the Gitlab helm chart repo for the dashboard project, but in the
-`unstable` channel -- the `stable` channel is reserved for chart versions that
-have been merged to the `main` branch.
+To do that:
+* Push your work to an MR.
+* Set the image tags in `values.yaml` to the one created for your branch; if
+  unsure, check the available tags in the Gitlab container registry for the
+  dashboard project.
+* Make sure to increase the chart version number in `Chart.yaml`, preferably
+  with a suffix to denote that it's not a stable version. For example, if the
+  last stable release is 1.2.3, make the version 1.2.4-myawesomefeature in your
+  branch.
+
+The CI pipeline should then publish your new chart version in the Gitlab helm
+chart repo for the dashboard project, but in the `unstable` channel -- the
+`stable` channel is reserved for chart versions that have been merged to the
+`main` branch.
 
 Once your package is published, use it by