Suggestion: READ.me should be updated to not suggest release branch as the default.

[BJackal]

Currently the READ.me for Chaste docker suggests pulling in the release branch as the default branch.

docker run --init -it --rm -v chaste_data:/home/chaste chaste/release

The current release branch is 3 years old an causes a lot of issues in regards to vertex based models. Often leading to unclear CellVecData errors. I would suggest instead that the default for the docker image should be set to develop. Likely also containing many other issues that a new branch no longer has.

docker run --init -it --rm -v chaste_data:/home/chaste chaste/develop

This will require a bit of updating throughout some of the documentation and perhaps Docker file but I have opened a new branch to do this on. Happy to go through and do this but thought it best to discuss first.

[mirams]

Hmmm, I think the idea might have been making the release branch defunct. But I do like the idea of a 'pull in latest stable release' as a tagged branch and then you can get any 'hotfix' type things, although this will tend to happen in develop anyway.

I guess @fcooper8472 we should either update release branch to point at latest release (within release instructions/procedure), or remove it altogether.

[bdevans]

Perhaps slightly confusingly, the command:

docker run --init -it --rm -v chaste_data:/home/chaste chaste/release

does not actually use the release branch - it pulls a docker image built using the latest tagged release (2024.1 at the time of writing).

I don't mind change the instructions to use the other command though if that's the consensus as the chaste/develop image is indeed built from the develop branch.