Date: Fri, 13 Apr 2018 10:07:36 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Matthias Fechner <idefix@fechner.net> Cc: Sunpoet Po-Chuan Hsieh <sunpoet@freebsd.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r467193 - in head/www/gitlab: . files Message-ID: <20180413100736.GA32041@FreeBSD.org> In-Reply-To: <431aaec9-51c2-c0c9-7a1f-2f29f79edb5d@fechner.net> References: <201804121833.w3CIXtgW077267@repo.freebsd.org> <e1a55c7b-1ad1-36c8-ec3d-f806702feed5@fechner.net> <CAMHz58RD9rtyqBLV6nsZ2naOvGRiO7PDPAGWZ8Vemnz-g1J6cw@mail.gmail.com> <431aaec9-51c2-c0c9-7a1f-2f29f79edb5d@fechner.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180413100736.GA32041>