Upgrade to new versions / Optimizations / Bug fixes #70
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Vladkryvoruchko
modified the milestones:
smoke-tests,
performance/optimization,
upgrade blockers,
post-upgrade fixes,
enhancements
This was referenced Sep 25, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Alright, I haven't maintained anything here for a while, so its time to put some effort to solve as many issues as I can and upgrade repo to the:
I plan to deliver updates in several phases:
Write some simple smoke tests, to be sure system functioning
Resolve any issues that are related to the bugfix/performance/optimization using Python3.5 interpreter
Remove blockers to be able to upgrade to the latest stable Python/TF/Keras versions
I may open a Poll vote to see a statistic about versions ppl use, and take it into account as well
I expect to have a bunch of new issues after upgrading to the new versions, so then will be the phase of solving new issues.
After all Blocking/Critical/High severity bugs will be resolved, Add add/enhance features such as better deploy/analyze if code refactoring needed/API layer(analyze if needed)
Answer the most common questions in the READme, so fewer issues with common questions will be created
(Different repository) Create Flask API wrapper around this project to ease up deploy/integration/whatever, so ppl without related experience can run it as easy as count to 3
e.g: git pull, make build; make deploy;
then do simple http(s) request
(docker-compose/Flask/nginx/uwsgi(or gunicorn)/celery worker/redis[or whatever configurable queue])