[Techniques] Are "Trunk is always releasable" and "Continuous Delivery" worth keeping separate?
Closed this issue · 0 comments
What change would you like to make to the tech radar?
Merge "Trunk is always releasable" and "Continuous Delivery" into a single thing (probably the latter).
Why do you believe this is valuable to Redgate?
Honestly, I think "Adopt" is a little crowded 😃
More seriously, I wonder if this is effective duplication. Let's check out the descriptions of the two entries:
From Accelerate: a development practice where software is in a deployable state throughout its lifecycle, and the team prioritizes keeping the software in a deployable state over working on new features. Fast feedback on the quality and deployability of the system is available to all team members, and when they get reports that the system isn't deployable, fixes are made quickly. Finally, the system can be deployed to production or end users at any time, on demand.
'Trunk as always releasable' is an ethos teams will follow and constantly strive to make true. We should have enough confidence in the product and automated tests that anyone can press the release button at any time. We release whenever we have something to release. We should act like trunk is always releasable at any time, and when we discover that it isn't/wasn't releasable, reflect on why and add the appropriate checks for next time. Typically our trunk is called 'master'.
...they seem pretty similar to me?
Where should this be on the tech radar?
Adopt.
If this should be in the Explore ring, who is committed to exploring it?
N/A.