WP-CLI's last five major releases have been roughly three months apart:

• v0.24.0 - July 26th, 2016
• v0.23.0 - March 23rd, 2016
• v0.22.0 - January 7th, 2016
• v0.21.0 - November 4th, 2015
• v0.20.0 - August 26th, 2015

My goal for WP-CLI is for users to never have to think about which version they're running — they should always be on the latest and greatest.

In the past, we've been fortunate that users are forced to update for compatibility with the latest WordPress version. Now that wp-settings.php is no longer forked (#2278), we don't have that excuse to depend on. Updating is easy for individual users — wp cli update. For organizational users, updating can include scheduling engineering time, a more rigorous QA process, and so on.

For the completion of this issue, I'd like to have documented:

• How often new major versions are released, and when minor releases are produced.
• Which versions of WP-CLI are officially supported.
• How we handle breaking changes.
• How we handle dependency updates (because WP-CLI is built into a Phar file that includes Symphony components, etc.)

Consider this to be an open thread; I'm curious to hear different perspectives on this issue.