OK - I prefer the second option, because I can see the prefix getting dropped somewhere down the line, and the format isn't really part of the proposal.
Most of the existing github issues record the process of creating 1.7 from the backlog of concluded tickets in Trac. The github issues seem like the natural place for these things and, for example, the recent ticket on an asciidoc issue (#135). Perhaps we need a new, seperate repository for change proposal e.g. `cf-convention/change-proposals` (or some such name). Then we can keep issues in each of the separate repos (`cf-conventions`, `Conformance`, `cf-convention.github.io` for all the other practical (rather than scientific or logical) thing that crop up. Do pull requests work across repos in the same project? Thanks, David -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/130#issuecomment-400721818
