Rocketeer 2.0 roadmap

# Features
- [x] Refactor the parts that needed it
- [x] Parallel deployments
- [x] Multiservers connections
- [x] Recognize contextual configuration files/folders without the need for includes
- [x] More informations on which task/event is running
- [x] Create DependenciesStrategy and make Composer a concrete of it
- [x] Add a PolyglotStrategy that installs dependencies through common PM (Bundler, NPM, Bower, etc)
- [x] Timer class that stores how long each task takes and display an average time to completion on average
- [x] Track down performances holes and work on connections caching
- [ ] FTP DeploymentStrategy

# Support
- [x] HHVM Support
- [ ] Official HipChat plugin (#158)

# Documentation
- [x] Add an automatically generated API
- [x] Split documentation sections in different pages
- [ ] Document all breaking changes, namespace changes, etc.
- [ ] Document the new Binaries system, how to use it, how to create Binaries
- [ ] Document the new Strategy system, how to use it, how to create Strategies, example with testing/migrating a Rails application
Well granted you track your Composer lockfile that one should be pretty fast, and migrations are disabled by default and enabled with a flat. As for symlinks there's isn't really any way to skip them, they're necessary to the process. That being said the process itself isn't slow, I deploy projects in under 20s on a Digital Ocean box, I think it's just a bug somewhere on your end between Rocketeer and the machine which makes the back and forth slow. It might be better on 2.0 as connections are cached but I can't garantuee it.