Roadmap

| Code Name | RFC | Champion | Possible Release | Description |
|---|---|---|---|---|
| Ports (edgedb/edgedb#1910) | Tomorrow | @1st1 | `v1.0` | Connection pooling, configuration of extra ports, share binary protocol port with HTTP |
| CLI Design (#14) | by `v1-beta1` / 2020-11-19 | @1st1 | `v1.0` | Organizes commands into groups. Other CLI improvements |
| Versioning | by `v1.0` | ??? | | Describes version scheme EdgeDB, CLI tools, language bindings. And also release cadence of various parts. |
| Ping/Pongs (edgedb/edgedb#1914) | by `v1-beta` / 2020-11-19 | @tailhook | `v1.0` | Adds protocol messages for ping/pongs and announcement of client capability of responding. Also specifies how server is going to use these |
| New Protocol | possibly by `v1.0` | @tailhook | `v1.0` | Use more uniform way to specify various protocol details (i.e. structure field vs header string) |
| |
| Tracing Metadata | by `v1.0` | @tailhook | `v2.0` | Add metadata for each request that shows up in slow log, statistics, and opentelemetry |
| HTTP Auth (#5) | by `v1.0` | @tailhook | `v2.0` | Authentication for the HTTP/WebSocket endpoints of the EdgeDB |
| ACLs | by `v1.0` | @elprans | `v2.0` [flag] -> `v3.0` | Allows fine-grained data access. |
| |
| Forms | by `v2.0` | @elprans | `v3.0` [flag] -> `v4.0` | Allows defining properly validated and secure HTTP(s) API endpoints for data input and access inside EdgeDB itself (no application code needed) |

Notes:
* `[flag]` -- feature-flagged release, where you have to opt-in for the feature and it has some "experimental" marker
* Dates are tied to releases we yet did not set a date for 1.0.
* This assumes 12 weeks/3 months release cadence

No source file, test, or concrete change is identified; start by checking whether this roadmap and its linked RFCs are still authoritative. Done would require an agreed update to the table and release assumptions, but the issue provides no acceptance criteria.

Written by the indexing model from the issue text.