-
-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap to stable v1.0.0 #101
Comments
Updated as |
What's the status of 0.5.0? |
@kelunik We're focussing on |
@WyriHaximus : The provided link does not contain any issue at the moment. |
@rrajkomar All currently open issues for |
Updated now that the v0.5.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! 🎉 |
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.4.3 ✅
v0.5.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.
The text was updated successfully, but these errors were encountered: