Split API Versioning #45

Open
opened 2020-06-13 01:31:05 +01:00 by SethFalco · 0 comments
SethFalco commented 2020-06-13 01:31:05 +01:00 (Migrated from gitlab.com)

With the common code removed from this repository, it makes less sense to version all APIs together.
We should consider splitting the versioning numbers out.

The interface is defined by Retropia, so when this receives a major update, that may warrant a bulk version change to all projects, but other than this each module is being updated one by one and the version number should reflect this.

We don't want to have updates available for people consuming the osu! API, when the past 10 releases where updates of other APIs or new wraps.

With the common code removed from this repository, it makes less sense to version all APIs together. We should consider splitting the versioning numbers out. The interface is defined by Retropia, so when this receives a major update, that may warrant a bulk version change to all projects, but other than this each module is being updated one by one and the version number should reflect this. We don't want to have updates available for people consuming the osu! API, when the past 10 releases where updates of other APIs or new wraps.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
SethFalco/elypiai#45
No description provided.