Open toloudis opened 2 years ago
toloudis
commented
2 years ago with tagged versions we can release to pypi. not sure if this lib already publishes to pypi. On the other hand if we are relying on main branch to always be the production release, then we have to have a dev branch to hold intermediate completed tasks prior to release.
blairlyons
commented
2 years ago We are already releasing tagged versions on pypi, so merging to main once implementation is finished should be ok
jsavieo
commented
2 years ago Releases: viewer - merge PR (Done), increment version (release), update viewer version on website (autodeploy to staging), manually push to prod (public release) website - merge PR (Done), increment version (autodeploy to staging), manually push to prod (public release) simulariumio - merge PR (Done), increment version (public release) after any required changes (either viewer or website) have been pushed to prod simularium-models-util - run models again -> Done, upload files to AWS s3
blairlyons
commented
5 months ago write summary document
What needs to happen?
Either used tagged version releases or have a dev branch where completed PRs can be merged.
Why should we do this?
We want to be able to merge PRs into main branch without worrying that it's going to break anyone's code. Some changes need this codebase to be in sync with app front and back ends.
When does this need to get done?
Next milestone?