Rafiki does not currently have any formal release cadence, structure or mechanism. This will make supporting deployments difficult. Having a formal release process for the codebase, docker images and helm charts will give greater ability to support deployments. This should allow major, minor and security based releases
Intended Outcomes
By the end of this piece of work, a full release process should be
designed
documented
implemented
It should allow us to version the codebase, docker images and helm charts seperately. We should also have the ability to backpatch security issues in previous releases.
How will it work?
Initially a team/individual will be tasked with designing and proposing a release plan. Once a process has been agreed upon, it should be documented and upon it form the basis for the documenting
Summary
Rafiki does not currently have any formal release cadence, structure or mechanism. This will make supporting deployments difficult. Having a formal release process for the codebase, docker images and helm charts will give greater ability to support deployments. This should allow major, minor and security based releases
Intended Outcomes
By the end of this piece of work, a full release process should be
It should allow us to version the codebase, docker images and helm charts seperately. We should also have the ability to backpatch security issues in previous releases.
How will it work?
Initially a team/individual will be tasked with designing and proposing a release plan. Once a process has been agreed upon, it should be documented and upon it form the basis for the documenting
Links