With the CKF 1.9 release coming soon, the rocks repositories are being updated to match the newer component versions. This is problematic because the code for CKF 1.8 components will be lost, making it impossible to maintain CKF 1.8 rocks.
What needs to get done
Create a track/<version>** Github branch in each rocks repository. The HEAD of the branch should be the last change made before upgrading the rock to its CKF 1.9 version.
** Format TBC
Definition of Done
The rock repository has a track/<version> Github branch
The main Github branch is not altered
The publish job from the branch is not altered and can continue to publish rocks
Context
With the CKF 1.9 release coming soon, the rocks repositories are being updated to match the newer component versions. This is problematic because the code for CKF 1.8 components will be lost, making it impossible to maintain CKF 1.8 rocks.
What needs to get done
Create a
track/<version>
** Github branch in each rocks repository. TheHEAD
of the branch should be the last change made before upgrading the rock to its CKF 1.9 version.** Format TBC
Definition of Done
track/<version>
Github branchmain
Github branch is not altered