sbp commented on issue #286: URL: https://github.com/apache/tooling-trusted-releases/issues/286#issuecomment-3779109283
Our current options, annotated by when they're used, are as follows. **Compose**: Source artifact paths (_revision_) Source artifact license checker (_revision_) Lightweight source excludes (_revision_) RAT source excludes (_revision_) Binary artifact paths (_revision_) GitHub repository name (_upload, distribution_) GitHub compose workflow paths (_upload, distribution_) Strict checking (_transition to vote_) **Vote**: GitHub vote workflow paths (_unused?_) Email (_form to start voting_) Manual voting process (_unsure_) Minimum voting period (_form to start voting_) Pause for RM (_vote resolution_) Release checklist (_form to start voting_) Vote comment template (_form to register a vote_) Start vote subject (_form to start voting_) Start vote template (_form to start voting_) **Finish**: GitHub finish workflow paths (_distribution_) Announce release subject (_form to announce_) Announce release template (_form to announce_) Preserve download files (_transition to released_) Since 81a5678539e41fdb002de278de4ba9a9f1e1dfa7 we have a method to store attestable data: it's written to a `state/attestable/PROJECT/VERSION/REVISION.json` file. Since this data only corresponds to revisions, it would only be useful for recording the fields above that are associated with revisions. Any other data could, perhaps, be stored in `state/attestable/PROJECT/VERSION.json`. Alternatives to JSON that we're considering are JSON Lines and SQLite3. If we used JSON Lines then we could have a single `state/attestable/PROJECT/VERSION.jsonl` log file and store everything in there. We could perhaps add a log line every so often which seals the log internally, using whatever mechanism we decide on for #214. The main drawback of this approach is that it's difficult to use strong typing if we're storing lots of tiny different log formats, but maybe we could throw it all into a giant discriminated union. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
