Quesnelia CSP #4

Spring Boot

Spring Framework 6.1

1. Upgrade various shared libraries and modules to the release candidate once it's available, then during Bugfest, upgrade them again to the GA version.  The idea being that the delta between the 3.4 (RC) and 3.4 (GA) is smaller than the delta between 3.3 and 3.4 (GA).  This approach adds a bit of complexity to Bugfest.
2. Stay on 3.3 for Ramsons GA and upgrade to 3.4 in a Ramsons CSP release.  Exactly what would be tested after deploying the CSP to Bugfest is TBD, maybe the smoke tests are sufficient?  This option would reduce the amount of moving parts during Bugfest.  The downside here is that the CSP is going to be large in terms of the number of modules. 
3. Upgrade to 3.4 (RC) for Ramsons GA and upgrade to 3.4 (GA) in a Ramsons CSP release.  It feels awkward for Ramsons to go GA on a release candidate versions of spring boot/framework.  There's also the risk that the devs on the spring project change their minds and some things in the 3.4 RC don't make it into 3.4 GA, which could lead to some thrashing/extra work.
4. Stay on 3.3 for Ramsons.  Upgrade to 3.4 in Sunflower.  This means we'd be unsupported for some period of time.  If we're lucky and there aren't any Critical/High security vulnerabilities in these frameworks, all is good.  However, if there are, we would be in the position where now we need to get teams to drop what their doing and upgrade unexpectedly, backporting the changes to Ramsons.

Decision:

Option 4

TC - review possibility to get enterprise support from Spring Framework

Reserve time in Trillium to upgrade to version 3.5