Page History

...

1. Roll to next snapshot version of parent poms, and update properties containing current version to use next snapshot version.
2. Roll ccsdk/sli repos (sli/core, sli/adaptors, sli/northbound, sli/plugins, distribution) to next snapshot and update to use new snapshot version of parent pomCrpom.
    Note: be sure to do the repos in the order listed.  core must be done first; then adaptors,northbound and plugins ; and lastly distribution.
3. Create new CCSDK docker containers
4. Rerun CSIT to make sure it still passes
5. Update parent poms to update properties containing version to the next version
   Note: at this point, builds of sli/adaptors, sli/northbound, sli/plugins and distribution will break, because we have not yet released sli/core. 
6. Create staging version of ccsdk/parent by posting comment "please release" to commit for previous step.
7. Mail helpdesk@onap.org to create a ticket requesting to release new CCSDK parent poms. In ticket, be sure to include link to the Jenkins release build triggered by previous step.
   NOTE: do NOT continue to next step until Linux Foundation has released parent poms.
8. Update ccsdk/sli repos to use released version of parent pom.
9. Create new staging versions of ccsdk sli repos (core, adaptors, northbound, plugins)
10. Create new CCSDK docker containers
11. Rerun CSIT to make sure it still passes
12. Mail helpdesk@onap.org to create a ticket requesting to release CCSDK sli repos (core, adaptors, northbound, plugins).  In ticket, be sure to reference Jenkins release builds trigger by step 10