Cruikshanks
commented
4 years ago Boy, this turned out to be a beast! I think its because we are having to handle 2 different kinds of service, each built using different technologies and deployed in different ways 😩 😁
The good news is it still pretty much follows a process used in 3 other services I have worked on so there will be familiarity with it outside the team. Plus when you have been through it a couple of times it becomes clear
- it's not nearly as scary as set out here 😨
- the actions individually are quick and repeatable
- a normal release to production will span at least 3 weeks from start to finish. This is not a process that is done all in one go!
So after all this work, my expectation is this document will quickly be forgotten about once we have a few releases under our belt 🎉
This change adds a document that details the release process for the charging-module-api and the tactical-charging-module.
It's primarily for use by the development team as it details actions they need to take. However, it should be of use to everyone on the team.