Brainstorm ways to help customers confirm their solution operates on a given release of Zowe for an extended period of time

[RASakach]

Help solve the challenge of interoperating with various releases of Zowe for a given time period -
Customers are not keeping up with the cadence of the Zowe release schedule, i.e. the (most) current release of Zowe (server side components) may not work with the latest release of a solution built-on-Zowe. The result, product teams are not able to test with the current Zowe release and consumers are frustrated that solutions are not working.

[RASakach]

Proposals:

1. Dramatically change the Zowe release cadence from 12 weeks >>>>> to every 6 months
2. Continue on the same cadence, and also provide a yearly "patch" release that offers a cumulative maintenance option - which would also require rethinking how we deliver patch releases (to not have to reinstall everything)
3. Continue the same cadence and change the way we deliver them, i.e. go to patch options for the minor versions (PTF style)
4. Something else?

How do we arrive at a solution?

1. Interview product teams, come back with their voice
2. Discuss at TSC
3. and...

[RASakach]

@balhar-jakub is this being managed at TSC or should we keep it open in Onboarding?