Designing a release procedure

Designing a release procedure
Pipelines. They can leak. Duh.

Release procedures are often done ad-hoc with the project development. Getting it right from the start can benefit overall project health in the long term and take a toll away from the team.

There are a lot of tools to choose from for the job but what matters most is to clearly define requirements, procedures, and environments.

All the code is almost always stored in some kind of version control system. Let's say, Git (Which is the choice in most cases).

The first thing that comes to your mind should be the branching strategy.

So be it, we can choose a top-to-bottom or bottom-to-top approach when designing any process.

Already have an account? Sign in.

Subscribe to qdnqn

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
Join other 12 members. Unsubscribe whenever you want.