- One language for all code (which is Ruby for now)
- Avoiding repetitive and boilerplate code.
- Use convention over configuration where possible.
- Class definitions that are internally consistent, and stable over time.
- Class definitions that act like existing well known structures.
- As friction free as possible configuration and development tool chain.
- Good documentation, and a helpful community, both for users, and contributors.
- A professional, well structured code base, complete test coverage, and automatic continuous integration.
- Implementation should be as efficient both in speed and space as practical given the above.
- First Hyperstack release based on last Hyperloop
- Change class names from Hyperloop to Hyperstack convention
- All gems building from one repo with an automated test, build, deploy process
- 10x speed improvement in hyper-spec
- Opal-webpack-loader based build process
- New webesite and updated docs and tutorials
- Use rails templates for installation and setup
- Depreciation of changes and documented upgrade path
- move current gem set to one repo under hyperstack (done - tx Barry)
- get specs to pass with current names
- release under old hyperloop gem names version 0.99
- publish to hyperloop-legacy branch (not master) with tag 0.99
- rename modules and classes per new naming conventions
- include a deprecation module
- document upgrade path
- release under new gem names with version 0.1
- tag as master version 0.1
- document install and usage instructions for OWL, and lazy loading
- release and tag as master version 0.2
- details TBD, may include restructure of gems as client and server adapters
- document upgrade instructions
- release and tag as master version 0.3