Marking a release amongst release candidates
It should be possible to mark/tag a specific release.
The reason is that we are building a lot of release candidates, but only some of those actually forms a final release, that can be installed at our customers environment.
By marking/tagging these and highlight them in the GUI, it is possible for people to see if an official release is installed at an environment or not.
This should always be the case in production, and it would be nice to quickly have an overview of that is the case or not.
See also this discussion:
http://help.octopusdeploy.com/discussions/questions/8125-marking-a-release-amongst-release-candidates
Troels Grosbøll-Poulsen
shared this idea
-
Darrell Tunnell
commented
We achieve this using channels and semantic versioning for our package releases. When we release a stable release that can go to a customer - we have a channel I'm octopus that targets stable release numbers. For unstable / pre-release packages, we have a separate channel. Each channel has its own life cycle. So this results in pre-releases only being able to go to our Ci environment, but stable releases can go to Dev, Staging and Production.