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

Let's internalize notification #501

Open
bhaugen opened this issue May 17, 2016 · 1 comment
Open

Let's internalize notification #501

bhaugen opened this issue May 17, 2016 · 1 comment
Labels
priority

Comments

@bhaugen
Copy link

bhaugen commented May 17, 2016

It is now auto-installing a newer version of account than the one we internalized awhile ago. We don't want any updates to notification, either, and I think we will want some mods. Pinning versions of these external apps doesn't seem to be reliable.
@bhaugen
Copy link
Author

bhaugen commented May 17, 2016

P.S. this came to the forefront when Valentina ran into interference between the version of account that notification installed and the one we internalized. The notification version wants django 1.5+.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bhaugen