Drupal's innovation cycles revisited

SLIDES: see above RECORDING: https://drive.google.com/file/d/118XVRhEwEIXxX6KsXa8WihiGlRuxrTQ4/view?usp=sharing (audio only)

At DrupalCon Baltimore we discussed the experimental modules process in Drupal core. Since that conversation we added a new experimental install profile in core, made one module hidden, matured some and even removed an experimental module from core. A lot has happened and we have a lot more experience with how our innovation cycles work. We made changes to how experimental modules are released with core.

There has also been recurring discussion about adjusting the six month release cycle for a few reasons:

1. When an issue just slightly misses the feature deadline for a release, it is almost eight months total to the next release, which can be disappointing and make the work harder to fund.
2. High bursts of work around two deadlines a year add strain for core contributors.
3. The lack of overlapping security support for old minors is difficult for many users and not well understood.

Let's discuss these at this core conversation!