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

Release new version #101

Closed
citizen-stig opened this issue May 10, 2016 · 3 comments · Fixed by #110
Closed

Release new version #101

citizen-stig opened this issue May 10, 2016 · 3 comments · Fixed by #110

Comments

@citizen-stig
Copy link

Please release new version of the package, because #73 has been fixed in december and I would like to apply this fix without installing a package from git

@dappiu
Copy link

dappiu commented Jun 8, 2016

You can always fork, put a tag on a commit that works for you and do pip install git+git://github.com/my_username/flask-assets.git@my_tag (works in requirements.txt too), or refer a commit/branch/tag from the master branch of the original repository, using the same format.

@jirikuncar
Copy link
Contributor

@dappiu forking and tagging a commit works if you are building an app. I'm working on framework for digital repositories where we would like people to run just pip install for installing everything.

Hence, I'm in favor of Release early, release often strategy to create a tight feedback loop between developers and testers or users of Flask-Assets.

@dappiu
Copy link

dappiu commented Jul 7, 2016

@jirikuncar I perfectly agree with you, I was just suggesting a temporary solution until the author takes some step here because I don't feel like we can do much more otherwise. That, and maybe leaving a +1 on this thread's first comment, which I just did :)

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 a pull request may close this issue.

3 participants