Closed sapetnioc closed 3 years ago
Summary of today's visio call:
Use casa-distro 3 to release BrainVISA 5.0
brainvisa.info/vbox
/ brainvisa.info/singularity
Release = image that includes all projects
casa_distro_admin create_release
-> runs make install-runtime
in an environment, copies the install directory into a casa-run
imagerelease_candidate
branches of individual projects. That branch evolves independently from master
, only the release team has the right to commit to it. Thus, special build-workflows on the release_candidate
branches are used when a release is being prepared.Tests : get tests to run nightly and get them to succeed in all supported environments
brainvisa
(public) and cea
distros using the Singularity workflowmaster
branchVersioning / branch switches
Web site: built with bv_maker
in a web
build-workflow (all of the public brainvisa
build-workflow + the web
project) (who does it, on which machine, at what frequency?)
I think this issue is obsolete now
This issue is related to #20 We must define how the BrainVISA team will work to make daily compilation, daily tests, virtual images updates, new releases, etc.