Rename the Deployment direction to Delivery direction
Why is this change being made?
When the current "Deployment direction" was created there was a rather unfortunate misunderstanding about the words Delivery and Deployment
delivery (landing on infrastructure) and deploying (making available to users)
is just the other way around.
- Deployment = landing on infrastructure
- Delivery = making available to users, typically includes deployment and release
This MR would like to fix the above misunderstanding. This would make our directions follow the industry standard terminology and would simplify a few related topics.
A few words on the terminology
Delivery is often mentioned in the context of Continuous Delivery. Here we refer to delivery in the broader sense of Application Delivery. For brevity and consistency with other stages, the recommendation is to call the direction "Delivery". Still, the direction page content will clarify that we mean Application delivery inclusive of Continuous Delivery.
Where does the poor terminology shows its consequences already? Related direction pages got confusing
The Release direction correctly states in their mission
Help our customers deploy software to production
But as it's derived from the current "Deployment direction", there is much confusion with calling "deployment" the act of "delivery" or "release".
The "Deployment management" direction is in a better position as the "parent" direction is called "Deployment" direction. The issue here is the correct scoping: what's the difference between deployment and deployment management?
We have issues on Deployment Direction should be inclusive of del... (Product#4053 - closed)
What is NOT in scope
This MR and change have no immediate effect on our product categories. No category would be renamed. The change would only clean up the confusing terminology used in the Deployment direction.
Approvals
-
Ready for review, @nagyv-gitlab -
Approved by @ogolowinski -
Approved by @david