In zonemaster/zonemaster-backend#1054 and zonemaster/zonemaster-backend#1083 a completely new RPC API was introduced, deprecating the old methods. These changes are scheduled for inclusion in 2023.1.
There is also a set of followup changes in zonemaster/zonemaster-backend#1084 and zonemaster/zonemaster-backend#1090 that make breaking changes to the new API methods. These changes are scheduled for inclusion at a later time in 2023.2.
This means that we're unnecessarily forcing breaking changes upon ourselves in 2023.2. Before stabilizing the methods we should probably also take the opportunity to review the design of the interfaces of the new methods for other changes we'd like to make. It's not often you get clean-up opportunities like this.
We should introduce these new methods in a responsible way that:
- minimizes the amount of breaking changes we have to make in the future, and
- makes sure the new methods have as good interfaces as possible.
Suggestion: Before releasing 2023.1 we should mark the new methods as experimental and remove the deprecation of the old ones.
In zonemaster/zonemaster-backend#1054 and zonemaster/zonemaster-backend#1083 a completely new RPC API was introduced, deprecating the old methods. These changes are scheduled for inclusion in 2023.1.
There is also a set of followup changes in zonemaster/zonemaster-backend#1084 and zonemaster/zonemaster-backend#1090 that make breaking changes to the new API methods. These changes are scheduled for inclusion at a later time in 2023.2.
This means that we're unnecessarily forcing breaking changes upon ourselves in 2023.2. Before stabilizing the methods we should probably also take the opportunity to review the design of the interfaces of the new methods for other changes we'd like to make. It's not often you get clean-up opportunities like this.
We should introduce these new methods in a responsible way that:
Suggestion: Before releasing 2023.1 we should mark the new methods as experimental and remove the deprecation of the old ones.