Talk:Continuous delivery

Clarification needed

"Continuous Deliver is ... and, when releasing the software, without doing so manually"

"continuous deployment (also abbreviated CD), a similar approach in which software is also produced in short cycles but through automated deployments rather than manual ones"

Do these two not contradict? 2A10:8003:1BB1:0:6C28:BA44:DF5:69E (talk) 04:59, 15 December 2022 (UTC)

It was worded ambiguously. I just now clarified. Michaelmalak (talk) 11:19, 15 December 2022 (UTC)

Yeah, I thought so too. Someone really needs to go back on the history and evolution of these terms. For me: deployment is about deploying software to run server side -continuous deployment is therefore the extension of Continuous Integration where you go beyond build and test to pushing out to staging and potentially production

whereas "delivery" is that of delivering working software-covers client side and is about a process of continually developing features and pushing them out (with feature flags etc). You can have Continuous Deployment (the technology) without Continuous Delivery (the process) - but not the other way around. Which is why the term Continuous Deployment was in use by 2001 but Continuous delivery is newer and still evolving SteveLoughran (talk) 16:25, 20 February 2024 (UTC)

Seeking consensus regarding "Strategies to overcome adoption challenges"

This section to me does not feel very encyclopedic. See WP:NOTHOWTO -- Very Fantastic Dude (talk) 22:34, 19 January 2022 (UTC)

@Very Fantastic Dude and Talk: WP:SOFIXIT. Walter Görlitz (talk) 07:13, 31 January 2022 (UTC)