Hints for major release management?

[SevenOutman]

Hi, Laravel team! It's amazing that you guys managed to make major upgrades so smooth.

I'm eager to learn how to properly plan major releases, focusing on following topics:

• After a new major release, when to decide to start developing the next major release? And when to decide to release it?
• How to keep the in-development next major release up to date with changes applied to the current major release? And how to decide whether a change should only go into the next major release and not be back-ported into the current major release?

I'd really appreciate it if you would like to share with us.