I've tried doing a little triage regarding all open issues and PRs, to see whether and how urgently they should become part of 1.1.0. Here's the result:

Should definitively be included (in some way or other):

Clarify Unicode and UTF-8 references #929: this is really just a small wording change.
Permit more control characters in comments #924: this incorporates the changes from Clarify Unicode and UTF-8 references #929 and so should be handled afterwards; it too is a fairly minor change, but it changes the substance of the spec, so @pradyunsg might conceivably reject it. But in any case it should be decided upon.

To be decided whether we include them:

Clarify sub-millisecond precision is allowed #805: it is just a tiny change to two examples; it makes sense to decide whether it goes in or is rejected before the next release.
clarify string descriptions #875: this too is a relatively small wording change, which might be accepted or rejected.
Define appropriate implementation behaviors for extreme values #538: it's unclear whether this will result in any changes, but it probably makes sense to give it some thought before the release.
Add syntax for hexadecimal floating point values #562: this would add new syntax, so we may accept it, postpone it for possible inclusion in a future version, or reject it altogether.
Feature request: Add a duration/timedelta type #514 – related PR: Proposal to add a duration type #717: this would add a new datatype, which might be accepted (in some way), postponed, and rejected.
Added Schema validator specification #116: this is pretty old, I don't know if it's still wanted or relevant. But it might make sense to decide on it some way or the other instead of just letting it rot.

Not essential, but would be nice to have:

Newlogo #909 – related issue: New logo design concepts #828: this has been hanging for quite a while and for no good reason I can see; it's not really relevant for a new version, but would be good to act upon to improve TOML's corporate identity.
Maintainance and onboarding new maintainers #895: clearly we can do a new release with the existing maintainer team, but the maintainer bottleneck is still noticeable, so it would certainly be helpful if there was some substantial progress on this ticket.
Make toml-test the standard test suite for checking compliance of implementations #585: not really a part of the spec, but progress on this would be good as well.

To be started afterwards:

TOML as an RFC? #870: there was already some talk that the 1.1.0 release might be a good starting point for an RFC (if and when we decide we want one), so the release must be done first before this can be tackled.

New syntax or features that are probably beyond the scope of TOML 1.1 (if they ever come):

Add nicer syntax for file sizes #912: frankly I think we could just reject this; but if it comes, I don't think it'll come soon.
Proposal: TOML Schema #792: this is a big topic that's probably best treated separately.
Optionally supported implementation-defined values #707: if this comes, it would be a big topic that'll require a lot of work, so I don't see it as a possible part of 1.1. Frankly I also see it as a violation of TOML's "minimalism" principle and would therefore be in favor of closing it altogether.
Will custom type syntax be good for TOML health? #603: similar to Optionally supported implementation-defined values #707 in scope and consequences.

Definitively beyond the scope of any TOML 1.x release, since it would be a breaking change:

Possible positional restrictions on table definitions #446: @pradyunsg: maybe one could add a "post-1.x" label for this, since it's incompatible with TOML 1.0 and so couldn't ever come before 2.0. Though frankly I think one could just close it, since "You can put tables in any order (except where arrays of tables are involved)" has always been a core element of TOML's philosophy and I don't really see it going away.

TOML 1.1.0 #928

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions