Skip to content
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

Document how we do releases, how we build docker images, etc #263

Open
orangejulius opened this issue Nov 26, 2019 · 0 comments
Open

Document how we do releases, how we build docker images, etc #263

orangejulius opened this issue Nov 26, 2019 · 0 comments
Assignees

Comments

@orangejulius
Copy link
Member

We don't have much documentation to tell people how we manage releases for Pelias.

Some things that would be useful to mention:

  • In general, we run a rolling release process where people are generally best off using the latest master branch.
  • We publish releases using semantic-release and using semantic versioning
  • Releases for each component of pelias are well described in the GitHub releases page for each repo
  • Each release of the "primary" Pelias repositories (Pelias services, importers, schema) have Docker images built for each branch, and for each commit
  • In the case where we have to make a breaking change, we will call this out in the release notes for the affected projects, and generally follow the rule that we will try to make breaking changes that are backwards/forwards compatible with at least 1 or 2 months leeway
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

No branches or pull requests

1 participant