some good practice rules to organize branches/merges (scampi has
currently just a "default" branch and a "dev" branch that we merge
frequently with default). It probably makes sense to avoid merging on
default something which is not tested nor documented.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Agreed, especially considering that the software will involve several researchers, with experimental extentions, so that each researcher should have its own branch for experiment.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Agreed, especially considering that the software will involve several researchers, with experimental extentions, so that each researcher should have its own branch for experiment.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
some good practice rules to organize branches/merges (scampi has
currently just a "default" branch and a "dev" branch that we merge
frequently with default). It probably makes sense to avoid merging on
default something which is not tested nor documented.
Agreed, especially considering that the software will involve several researchers, with experimental extentions, so that each researcher should have its own branch for experiment.
Agreed, especially considering that the software will involve several researchers, with experimental extentions, so that each researcher should have its own branch for experiment.