New Snowdrop productization and support plan

This plan describes what the impact will be for the team(s) to:

• Stop to productize the snowdrop BOM and to use directly the upstream Spring Boot community BOM,
• Continue to support Spring Boot when the Community support ended and before we reach the EOL of the commercial support

Action plan

• Engineering
  • Disable on our internal jenkins server the jobs responsible to productize Snowdrop BOM
  • Inform CPAAS that our project should removed from their platform
  • Archive the existing github snowdrop BOM project (optional)
  • Review and update the jobs publishing the examples on launch.openshift.com as we will not publish anymore the prod version
  • Create new jobs to verify according to x use cases that SB works on kubernetes (upstream) using dekorate, buildpack builds, ...
  • Close and maybe re-assign the opened CVEs as they will not be fixed
• Management
  • Define a release calendar as will certainly not test / support all the upstream SB releases
  • Inform the QE team about the new releasing cadence to get their go/no go
  • Inform the BU, GSS, Program management and doc team about the new plan
  • Review the process creating automatically the Jira tickets when a new upstream release is out and should be verified
  • Continue to collect for each release what should be the "proposed or supported" version of the 3rd party red hat products consumed y the different starters as such information should be communicated to QE team at least
• QE
  • Review and adapt the test cases to perform the tests using the upstream SpringBoot BOM but where we use as dependencies the the Red Hat products (Apache Tomcat, ....) against ocp4
  • Adapt the process to report the approval post QE tests (= signoff)
• Support and release
  • Review and update the existing RuntimeSKU support page
  • Adapt the releasing process to publish the new information when a new SB upstream release has been tested and verified
  • Create a doc detailing how we will handle a customer ticket if an issue is raised against a SB starter > OSS ended and < EOL of our commercial support.