Repository navigation
Roadmap to stable v1.0.0 #75
Description
Activity
Updated now that the v0.5.1 release is out
This also makes the previously planned v0.7.0 release obsolete, as the updated streams do not affect BC.Updated to plan the intermediary v0.6.0 and the major v0.7.0 for this week and deferred Unix socket server support to future v0.8.0 with a simpler facade API.
- added a commit that references this issue
on Mar 29, 2017 Updated now that the v0.7.0 release is out
Reacted by Ivan Kalita, Maxime Veber and Chris BodenUpdated to reduce focus of the upcoming v0.8.0 release so that all non-breaking changes will land after the v1.0.0 release is out.
Updated now that the v0.8.0 release is out
Unless we find any major blockers, there's hope that this is the last noteworthy release before we get to tag this as v1.0.0 🎉
The very first stable v1.0.0 release with LTS has just been tagged and released! 🎉
Reacted by Cees-Jan Kiewiet
Let's face it, this project is stable and has been used in production for years
However, we're currently following a v0.X.Y release scheme (http://sentimentalversioning.org/).
We should finally make this explicit and fully adhere to SemVer and release a stable v1.0.0.
To a large extend, a stable v1.0.0 helps making BC breaks more explicit and thus the whole project more reliable from a consumer perspective. This project is actively maintained and has received some major updates in the last weeks and has some major updates planned in the next weeks. Given our current versioning scheme, we'd like to ensure all anticipated BC breaks will be merged before the planned v1.0.0 release.
As such, I've set up a roadmap that enlists only the major changes for each version among with planned release dates towards a stable v1.0.0 release:
v0.5.0 ✅
v0.5.1 ✅
v0.6.0 ✅
v0.7.0 ✅
v0.8.0 ✅
v1.0.0
This ticket aims to serve as a basic overview and does not contain every single change. Please also see the milestone links and the CHANGELOG for more details.
Obviously, this roadmap is subject to change and I'll try to keep it updated as we progress. In order to avoid cluttering this, please keep discussion in this ticket to a minimum and consider reaching out to us through new tickets or Twitter etc.