-
Notifications
You must be signed in to change notification settings - Fork 851
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
How to find the roadmap about toml #942
Comments
You're looking at it; the issues and discussions on this repository serve essentially the same purpose. |
The TOML project doesn't have design documents that we end up having extensive discussion on -- instead, the design discussions happen in this issue tracker, and pull requests for language changes in the spec serve the same purpose as rfcs in some sense. There is also no "traditional" roadmap, since there's no established need for hte project to have such a roadmap at this time. I'll close this out since the question has been answered. :) |
Even though this question's been answered officially by @pradyunsg, I'd like to suggest this list of open issues and PRs by @ChristianSi from a few weeks back. His opinions may be his own, but I've used his list to address unresolved issues whose solutions would move us closer to a release candidate for TOML v1.1.0. It isn't a final list by any means, but it's as near a roadmap to the next release as we have for this iteration. We can always use additional points of view by enthusiasts who want to provide their use cases and suggestions. If any of these issues, discussions, or PRs catch your eye, please feel free to drop a comment in any of these items. |
How to find the roadmap about toml?
Roadmap or Rfc exist? Like rust rfc : https://github.com/rust-lang/rfcs
The text was updated successfully, but these errors were encountered: