Clarify instructions for updating multibuild about multibuild HOT 10 CLOSED

Yeah, it does require a bit of submodule knowledge, but I usually go the long way round:

cd multibuild
git checkout master  # only needs doing once
git pull
cd ..
git add multibuild

from multibuild.

I don't know if I am suggesting always updating the multibuild submodule. I am sure that will, occasionally, break people's build, so I'd rather they do the update explicitly, with the promise from us that we'll try and keep master working, and so an update should be relatively safe.

from multibuild.

How would you suggest doing the update explicitly?

(This is the first time I've dealt directly with git submodules, which is perhaps why this part of the README.rst seems unclear to me)

from multibuild.

I would like to see any clarifications on when (if?) new commits are merged into master.

Normally, projects have releases/milestones (typically implemented as git tags) and a few release lines (implemented as branches), and only implement certain API changes into the next major or minor release line (in semantic versioning, backward-compatible changes between minor releases, breaking changes between major ones, no changes beside bugfixes between micro ones).

Not so here. I don't see any releases, so it's unclear which revisions I'm supposed to use in production to get new features.

from multibuild.

We use the 'live at head' philosophy.

from multibuild.

from multibuild.

So the theory is that we only merge to master when we are sure that the particular commit does not have any significant problems. I personally just update multibuild to devel though; I don't really look at master at all.

from multibuild.

Guess what? I found a downside of never using branches or tags.

If one uses submodule update --depth to save on clone time, eventually, the command will stop working because one cannot check out a commit more than <depth>-1 away from a ref.

from multibuild.

I believe this can be closed thanks to https://github.com/matthew-brett/multibuild/pull/122.

from multibuild.

Thanks - yes I agree.

from multibuild.