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

[chris Wolff]

Hi Composer Recommends,
commiting it with composer.json into the version controll system:

"This means that anyone who sets up the project will download the
exact same version of the dependencies. Your CI server, production
machines, other developers in your team, everything and everyone runs
on the same dependencies, which mitigates the potential for bugs
affecting only some parts of the deployments."
 - http://getcomposer.org/doc/01-basic-usage.md#composer-lock-the-lock-file

regards chris

2013/8/30 Mario Rimann <mario.rimann at typo3.org>:
> Hi Jigal
>
> Am 27.07.13 11:30, schrieb Jigal van Hemert:
>> Thanks for brining this up. There are some things about composer that
>> bring more questions:
>
> I agree, there are other things that can be needed to discuss related to
> compoer.
>
> But for now, I'm happy with composer - and still unsure whether to
> commit the composer.lock file or not.
>
> What's the experience of the Surf-Deployment experts? What would you
> recommend?
>
> Cheers,
> Mario
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow



-- 
christian wolff - webdeveloper, tech-loving geek and typo3 enthusiast
telefon: +49 30 347 244 88
mobil:  +49 179 49 44 758
email: chris at connye.com
adresse: friedelstraße 31 - 12047 berlin

xing-profil: http://www.xing.com/profile/Christian_Wolff43
google+: https://plus.google.com/u/0/115669673917212236875/posts?hl=de
facebook: https://www.facebook.com/1stMachine
flattr: https://flattr.com/profile/1stmachine