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.

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

Should we specify fixed versions in tagged releases? #76

Closed
zerebubuth opened this issue Mar 7, 2017 · 2 comments
Closed

Should we specify fixed versions in tagged releases? #76

zerebubuth opened this issue Mar 7, 2017 · 2 comments

Comments

@zerebubuth
Copy link
Member

zerebubuth commented Mar 7, 2017 •
edited
Loading

We currently specify the master branch for tilezen software dependencies in requirements.txt, although we specify fixed, non-master versions in the vector-datasource release notes. This is confusing, since the installation instructions say to install requirements from requirements.txt. We should fix versions in requirements.txt or provide different installation instructions which install fixed versions.

See #75 for context.
@zerebubuth zerebubuth mentioned this issue Mar 7, 2017
Closed
@pnorman
Copy link
Contributor

pnorman commented Mar 7, 2017

👍 to changing requirements.txt

@nvkelso
Copy link
Member

nvkelso commented Mar 7, 2017 via email

@pnorman pnorman mentioned this issue Jun 10, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@zerebubuth @nvkelso @pnorman