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

Readme version comment #868

Closed
bitwiseman opened this issue Feb 2, 2016 · 2 comments
Closed

Readme version comment #868

bitwiseman opened this issue Feb 2, 2016 · 2 comments
Labels
type: task
Milestone
v1.6.4

Comments

@bitwiseman
Copy link
Member

Many projects depend on this one. Having the version in the readme track the release version would reduce confusion. Either that or removing the version from the readme.
@bitwiseman bitwiseman mentioned this issue Feb 2, 2016
Closed
@bitwiseman bitwiseman added this to the v1.6.3 milestone Feb 3, 2016
@jayceekay
Copy link

why open this without merging my PR which actually updated it? to get opinions on whether it should be done or not? are you trying to automate this for all future releases?

@bitwiseman
Copy link
Member Author

Automate (in the release-all.sh script) or consider removing - the package.json has the version number in it.

@bitwiseman bitwiseman modified the milestones: v1.6.3, v1.6.4 Jun 3, 2016
@pyup-bot pyup-bot mentioned this issue Mar 5, 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
type: task
Projects
None yet
Milestone
v1.6.4
Development

No branches or pull requests
2 participants
@jayceekay @bitwiseman