...
- move out loosely coupled reusable code into it's own GitHub repository (repository per-piece), e.g. ImageHelper goes to one repository and CurlHelper goes to other
- each moved out piece will have it's own release cycle (can get released even before In-Portal does)
- all component bug fixes are automatically applied to all projects using it (through usage of Composer "
1.*" dependency) - as any code, hosted on GitHub we'll also be granted with usage of TravisCI (https://travis-ci.org/), which is Continuous Integration server, that would automatically run our tests (or whatever we need to run) on every commit.
After completing this step we'll get (at lease these):
...