Closed MarkLodato closed 3 years ago
Mark, should we add backwards-compatibility as a design requirement? As it is right now, I do not see how the spec helps older clients and repositories who cannot immediately upgrade their code.
No. I just responded on #14. Instead of adding backwards compatibility here, I plan to remove it entirely from the spec.
Friendly ping. Ready to merge?
@MarkLodato Whoops, sorry! I meant to ask you about:
MUST support multiple signed messages in a single file, possibly as a separate file format
Could you elaborate on the motivating use cases there? Thanks!
Apart from that, it looks good to me, and I'm happy to merge.
Removed. I'll create a separate GitHub issue for this, and we can add the requirement back once we agree and start work on that piece.
This helps readers understand what problems we are trying to solve and why we chose these particular decisions. It also helps us assess potential future changes.
NOTE: The "multi-message file format" is not yet in the spec. I am adding it here because we do need to eventually define that.