Because the world wants me to suffer, a customer is making us rename our environments. So here's our current names:
---
My problems:
---
Customer's recommendations:
---
Mind you, this is for a fairly small team (one that we ran way busier before this), I don't think the over-complicating environments is worth the effort, but it's also an opportunity for me to clean up the names of our environment (even if they choose something silly for theirs).
My goal has always been to try to stick to some sort of industry-aligned naming scheme, we could always name our environments after version numbers if we wanted to, but it's clunky to only do it for 2, why not name the others "revision?", ehhh. I also wanted something less-awkward for laymen.
Ideas? What do you name your environments?
Hotfix- Things that must go out soon, usually <24 hoursStaging- Next less-rushed release, usually at least once a week, sometimes a few times a weekCore- For longer-term releases, something to take 3-6 weeks to developSid- I've never been a big fan of this, this was the name thrown at it by our system engineer, it's for an environment to manually deploy things to and test the ever living hell out of in isolation.Sandbox- An environment for allowing 3rd parties to work on code that may be in lockstep with production, but we may push new 3rd party APIs to so that partners can work against cutting-edge APIs.Production- Well duh
---
My problems:
- I hate
Core- it's not really descriptive, I've been fighting with LLMs and looking at all kinds of environment layouts, I got some options likeNextandEdgeandPreview Sidwas cute but nondescript,Testis probably better,Sandboxactually works great hereSandbox- Well ifSidbecomesSandbox, this needs to become something else,Partner?
---
Customer's recommendations:
HotfixBugfix - A place to do less-urge bugfixes that are less urgent than Hotfix but more urgent than StagingMinor - Replaces staging, I don't like this because it's a version number and not an environment nameMajor - Replaces core, see aboveTest - Even though I mention it above, I prefer Sandbox because these are all test environments!---
Mind you, this is for a fairly small team (one that we ran way busier before this), I don't think the over-complicating environments is worth the effort, but it's also an opportunity for me to clean up the names of our environment (even if they choose something silly for theirs).
My goal has always been to try to stick to some sort of industry-aligned naming scheme, we could always name our environments after version numbers if we wanted to, but it's clunky to only do it for 2, why not name the others "revision?", ehhh. I also wanted something less-awkward for laymen.
Ideas? What do you name your environments?