-
Notifications
You must be signed in to change notification settings - Fork 780
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
hyperapp version #1079
Comments
New projects should use the latest 2.0 branch as the 1 branch has been deprecated for a few years now. The 2.0.x has been stable for a while so I’d be very surprised if any breaking changes happen. But you’re right there hasn’t been an official announcement that it is “production ready” (although it is used in production in several places). As for documentation, there is no official website yet either but the docs folder in this repo is pretty well complete with all you need to know and more. |
Thank you, I think it will be good to have all versions after 2.0.0 included on "releases" and perhaps considering marking 2.0.0 or after as "stable" |
@kofifus I agree. Last I heard there were some plans to implement tests and then call it ready. (As docs and types are done). Not exactly sure where we are with the tests but if it’s any comfort it’s been tested pretty extensively in the real world. Should be safe to call it stable and mark a release in my opinion. |
Newbie here, two questions regarding versions:
Basically what version should a new project go for and where is that documented
Thanks!
The text was updated successfully, but these errors were encountered: