Beta release is major refactor of the Sputnik example code to make the project modular, API driven, increase code coverage, and generally make it easy to consume and integrate into actual solutions.
Attention: All versions of Sputnik are to be considered "example" code and are provided "AS IS" under the Amazon Software License.
The Beta Release is being tracking by the Sputnik Beta Release Project and will mark the first official release of the project.
Key Features/Requirements:
[x] Refactor project to be modular
Enable using specific parts of the project rather than "all or nothing"
[ ] Refactor API (Schema First) (WIP)
[x] Separate API schema and operations
[ ] Refactor API schema (WIP) #19
[ ] Consistent naming of types, querier, mutation, etc (WIP)
[ ] Consistent operation inputs and pagination (WIP)
Once all the above have been completed, depending on the level of code coverage and the stability of the project overall, the core contributor team will decide on either release v0 or v1. Anything prior to v1 will not follow Semver and may have breaking changes between minor/patch releases. However from v1 onward, the project will follow strict Semver releases and be considered "stable". Obviously, without comprehensive test coverage this is not possible to maintain, as such will stay in <= v0 until team is confident in ongoing maintainability.
Beta release is major refactor of the Sputnik example code to make the project modular, API driven, increase code coverage, and generally make it easy to consume and integrate into actual solutions.
The Beta Release is being tracking by the Sputnik Beta Release Project and will mark the first official release of the project.
Key Features/Requirements:
Once all the above have been completed, depending on the level of code coverage and the stability of the project overall, the core contributor team will decide on either release
v0orv1. Anything prior tov1will not follow Semver and may have breaking changes between minor/patch releases. However fromv1onward, the project will follow strict Semver releases and be considered "stable". Obviously, without comprehensive test coverage this is not possible to maintain, as such will stay in <= v0 until team is confident in ongoing maintainability.