[ ] Resolve other issues/PRs associated with the milestone (most importantly: can we get the class optimizations into this release?)
[ ] Decide whether to remove Ristretto/VC/PoKCR in first public release (probably want to move these to a vc branch)
[ ] Write/stabilize docs for release. Similar to the bulletproofs library, we might want to have an explanatory notes module (see their lib.rs and docs)
[ ] Pick an open-source license and verify that all code we're relying on is compatible (Alan brought up VDF competition code as a potential ambiguity)
[ ] Decide if we want this repo to be IDE-agnostic (I think having a .vscode folder and VS Code setup suggestions is fine, particularly for newbies trying to contribute; still, something to think about)
[ ] Add a CONTRIBUTING.md for external folks (see here for an example)
[ ] Add CI/pre-commit hooks to verify that rustfmt and compilation succeed. Since master is protected and since our contributor guide will discuss standards for code hygiene, this is mostly a sanity check mechanism
[ ] Bump version in Cargo.toml
Launch Tasks:
[ ] Squash commit history
[ ] Make repo non-private
[ ] Decide on publicity strategy (also what our position on ongoing maintenance of the library is)
(Tasks are roughly ordered.)
Code Tasks:
vcbranch)bulletproofslibrary, we might want to have an explanatorynotesmodule (see their lib.rs and docs).vscodefolder and VS Code setup suggestions is fine, particularly for newbies trying to contribute; still, something to think about)CONTRIBUTING.mdfor external folks (see here for an example)rustfmtand compilation succeed. Sincemasteris protected and since our contributor guide will discuss standards for code hygiene, this is mostly a sanity check mechanismCargo.tomlLaunch Tasks: