Maestro moving to v10.x with breaking changes

[caiordjesus]

Summary

Hey everyone!
We're deprecating the current version of maestro (v9) in favor of a new major change (v10).
The v10 is a revamp of Maestro, having a totally different codebase and architecture. Although some endpoints have correlations, the structure is different and this new version is incompatible with the current one at almost all levels.

Related libs

• Maestro client is not affected by this release;
• Maestro cli is affected, having a new version too.

v10 adoption

After being released, the v10 will still miss some already planned features, like autoscaling. That said, depending on your need, it's better to wait for these features to come on new minor versions through Q2 and Q3, although we still recommend using v10 if it's possible.

v9 end of life

The v9 code will still be hosted in the "v9" branch in the repository.

We will keep the v9 support after the v10 is released (more details below). However, after that period, the version will no longer receive any updates.

Here is the complete timeline of the v9 next steps:

Date	Status	Comments
2022-02-14	Deprecated	Only security and performance fixes will be accepted. The package will be marked as “deprecated”, and V10 will be recommended.
2022-12-14	Inactive	Only critical security fixes will be accepted.
2023-06-14	Read-only	No more code changes will be accepted, and the “v9” branch will become read-only.

Issues and pull requests

All issues regarding v9 will need to be labeled. Then, a contributor member will review them to see if they will be accepted following the v9 status (Deprecated, Inactive, and Read-only).