New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Define an API change process #243

Open

CharlesNepote opened this issue Mar 5, 2025 · 0 comments

Member

CharlesNepote commented Mar 5, 2025

What's the process in case of API changes?

Document API changes
API versionning? (Or not)
Push information to API users
Delay to launch new version
Test impacts, at least in Product Opener and mobile app
Ask feedbacks from Product Opener and mobile app devs.

What needs to be done?

Create something to push information
Create at least a detailed API changelog; distinguish small and biger changes; distinguish features improvements without any impact
Publish the process on this repo
...

FYI: 4 API users are already identified:

Product Opener (Open Food Facts backend and web frontend)
Open Food Facts mobile app
@aleene app
@VaiTon app

teolemon added this to 🏷️ Folksonomy Engine

github-project-automation bot moved this to Todo in 🏷️ Folksonomy Engine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment