Develop a runbook for CLI/API/dandischema release procedures

dandi / dandi-archive

DANDI API server and Web app

https://dandiarchive.org

13 stars 10 forks source link

Develop a runbook for CLI/API/dandischema release procedures #826

Open waxlamp opened 2 years ago

yarikoptic commented 2 years ago

good idea. FWIW, for dandi-cli and dandischema it is largely

Merge a PR which has release label assigned (that would release to github and pypi)
Wait for conda-forge bot to pick up new release from pypi and prepare a PR against corresponding feedstock. Review/adjust (if needed) and merge

waxlamp commented 2 years ago

This is aimed toward a more holistic understanding of release procedures. I want to avoid the production breakage that occurred this time around due to mismatched dandi schema versions in the different components.

satra commented 2 years ago

i think the simplest solution is that a schema release should always trigger a co-occurring release of all components (api, ui, cli) with support for that schema, since technically the CLI and API don't impose an exact version or a max version, just a min version of the library. this would mean that anyone installing the CLI or upgrading dandischema could in essence move to a newer version of the schema.