[Flow] Commit the composer.lock file or not?

[Mario Rimann]

Hi

The guys that brought us composer suggest to commit the composer.lock
file, so that the exact same set of packages/revisions is installed
wherever the installation happens.

Basically this seems to be a great idea. But it would bring us back to
something very similar like updating Git submodule pointers on each
change - I don't want this to come back.

My scenario is:
I have a distribution which requires one of my packages to be installed.
Whenever I push changes to this package, the whole distribution is taken
and deployed to a test server via Surf.

But now it just installs the versions in the lock file - which is in
theory ok - but it doesn't contain my latest changes to my own package.

So what is the Flow way of doing it, given the above scenario?

Cheers,
Mario