svn commit: r467193 - in head/www/gitlab: . files

[Alexey Dokuchaev]

On Fri, Apr 13, 2018 at 11:55:13AM +0200, Matthias Fechner wrote:
> ...
> To make tests for all features in Gitlab you will require many hours and
> I'm not willing to do the work the gitlab team is doing already for us.
> They provide us with clear instructions what version are tested and
> should work.
> To be 100% save we should use what is in the Gemfile.lock, but this
> would really a major effort and I think to use what is in Gemfile
> defined is relatively safe.
> I remember only 2 cases where even the definition in the Gemfiles cause
> gitlab to break. One was the upgrade of default_value_for from 3.0.3 to
> 3.0.4.

I don't quite understand how/why would anyone in their right mind write
software than breaks when one of its dependencies have *minor* version
bump?  Is this specific to Gitlab, or the nature of Gemfiles is really
that broken?

./danfe