Naming strategies can be difficult, as it mostly depends on your deployment process and goals. One possible solution here would to use a naming strategy in concert with channels e.g
This lets you define channel rules around the
-xxxxx tag so that only images with the
-production post fix can go through to the production environment. If desired you could also use
Production as a prefix (e.g.
Production- [applicationname].1.0.0-dev.12345) so you can
tag any release that you want to go through to your production environment.
As I mentioned at the start, this will very much come down to how you want to move packages through your Octopus Lifecycle (or lifecycles) so I can only give general advise. You might also want to look into branches as well, although I’m not 100% it’s relevant in this case.
I hope that helps, if there is anything else I can help with please let me know,