View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009441 | Taler | documentation | public | 2025-01-07 13:24 | 2025-01-07 22:35 |
| Reporter | oec | Assigned To | |||
| Priority | normal | Severity | text | Reproducibility | always |
| Status | confirmed | Resolution | open | ||
| Product Version | git (master) | ||||
| Target Version | 1.0 | ||||
| Summary | 0009441: Protocol version missing in public documentation | ||||
| Description | The public documentation at docs.taler.net, and there under "Core Protocol Specification", none of the protocol API's (exchange, merchant, auditor etc.) mention their current version of their protocol. I suggest that for each API, the protocol version should be - part of the "Overview" section - prominently and consistently presented in the introduction of each API - (if possible) automatically synchronized with the versions set in the main branches of the respective API repos | ||||
| Tags | No tags attached. | ||||
|
|
Eh, they all do mention this under /config. I'm not against moving this up or making it more prominent, but it is not *missing*. |
|
|
As far as automatic sync goes, that should *not* be done, as we _do_ sometimes write specs before implementation, and/or may have an implementation in a branch but the spec already in master, etc. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-01-07 13:24 | oec | New Issue | |
| 2025-01-07 13:24 | oec | Status | new => assigned |
| 2025-01-07 13:24 | oec | Assigned To | => Christian Grothoff |
| 2025-01-07 22:34 | Christian Grothoff | Note Added: 0023945 | |
| 2025-01-07 22:35 | Christian Grothoff | Note Added: 0023946 | |
| 2025-01-07 22:35 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2025-01-07 22:35 | Christian Grothoff | Severity | feature => text |
| 2025-01-07 22:35 | Christian Grothoff | Status | assigned => confirmed |
