Time-based releases concept - trains leave on schedule

Situation

Consider moving to time-based releases where engineering ships whats ready on a fixed cadence (e.g., monthly or bi-weekly). Product must scope features to fit the timeline rather than engineering stretching to fit scope. The train leaves whether youre ready or not.

Reasoning

Time-based releases invert the power dynamic - product cant keep adding scope because the train leaves on schedule. This forces prioritization decisions onto product where they belong. Agile shops ship every two weeks with whatever is ready.

Additional Context

Currently product keeps adding requirements (AMD, CLK 618, Ola) making existing dates impossible. Bjorn throws down arbitrary dates to see response. Time-based releases would flip this - engineering commits to cadence, product commits to scope.

Observed Evidence

Justin: "All Linux products now are a time-based release... we will ship what we have in June, no matter what" and "There will be a train every two weeks. Its up to you what we put on the train" and Peter: "Im fine with that world... Were not that far off"

Confidence Breakdown