at some point, we should start thinking if and how to tag scicatlive. Since we already have a tag 1.0, I think we could think of the changes we've made and tag accordingly.
Since we've done many changes already (subdomain changes, refactoring - in principle backwards compatible -, containers addition), maybe in this case we can simply create 1 tag which collects these together.
The next will probably be once we integrate the new be with fe etc.
We should also probably tag whenever we upgrade some dependency to a major version.
We should think the numbering to use, for example if we want to be anyhow consistent with the other scicat tags.
at some point, we should start thinking if and how to tag scicatlive. Since we already have a tag 1.0, I think we could think of the changes we've made and tag accordingly.
Since we've done many changes already (subdomain changes, refactoring - in principle backwards compatible -, containers addition), maybe in this case we can simply create 1 tag which collects these together.
The next will probably be once we integrate the new be with fe etc.
We should also probably tag whenever we upgrade some dependency to a major version.
We should think the numbering to use, for example if we want to be anyhow consistent with the other scicat tags.