Skip to content

Document the release policy #405

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.

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

Merged
merged 1 commit into from
Feb 24, 2018
Merged

Document the release policy #405

merged 1 commit into from
Feb 24, 2018

Conversation

dunglas
Copy link
Member

@dunglas dunglas commented Feb 23, 2018

The important part:

  • stable (currently the 2.2 branch): regular bug fixes are integrated in this version
  • old-stable (currently 2.1 branch): security fixes are integrated in this version, regular bug fixes are not backported in it
  • development (master branch): new features target this branch

Older versions (1.x, 2.0...) are not maintained. If you still use them, you must upgrade as soon as possible.

ping @api-platform/core-team

@joelwurtz
Copy link
Contributor

What about the timing of releases ? Can we expect consistent time between each releases or will this mainly depend on contribution activity ?

@dunglas
Copy link
Member Author

dunglas commented Feb 23, 2018

@joelwurtz I've written this in the docs: New versions of API Platform are released **when they are ready**, on the behalf of the API Platform Core Team.

So it will mainly depend of the contribution activity for now. We may change this later. My current idea is to release a new minor version of API Platform ~1 month after the release of every minor Symfony version (so every 6 months). But I don't want to enforce this hardly for now, we may release versions more frequently if the activity level is high.

@dunglas dunglas merged commit ad4be2f into 2.2 Feb 24, 2018
@dunglas dunglas deleted the releases branch February 24, 2018 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants