Date: Sun, 13 Feb 2011 19:36:59 +0300 From: Andrej Zverev <az@freebsd.org> To: Erwin Lansing <erwin@freebsd.org> Cc: cvs-ports@freebsd.org, cvs-all@freebsd.org, ports-committers@freebsd.org Subject: Re: cvs commit: ports/converters/p5-Text-Bidi pkg-descr ports/databases/p5-DBIx-Class-EncodeColumns pkg-descr ports/databases/p5-Dancer-Session-Memcached pkg-descr ports/deskutils/p5-ZConf-BGSet pkg-descr ports/devel/p5-App-SVN-Bisect pkg-descr ports Message-ID: <AANLkTinYWd0_pKOnPd%2Bpxfb96b7TwO9nVS=gbjc5azr0@mail.gmail.com> In-Reply-To: <20110213160735.GO18095@droso.net> References: <AANLkTinZ-GHCx6E%2BvD9cmtFWXgDjJf%2BB7gkuy38Kxg%2BO@mail.gmail.com> <20110213160735.GO18095@droso.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Jesus Christ! it changes everything. Thanks for pointing and explaining. I was almost already do touch 226 ports. Since guidelines is outdated maybe put your explanation somewhere on WIKI under portmrg@ section? On Sun, Feb 13, 2011 at 7:07 PM, Erwin Lansing <erwin@freebsd.org> wrote: > On Sun, Feb 13, 2011 at 05:29:32PM +0300, Andrej Zverev wrote: > > Pardon me but I thought what sweeping commit = affect huge number of > ports > > which cluster required to rebuild. > > Since my commit don't touch PORTVERSION or PORTREVISION(PORTEPOCH). I > really > > thought it's okay. > > So, what actually sweeping commit? Don't touch more then 10,20 ports per > > commit? > > How my changes affect on package building? If I broke something I'm ready > to > > fix. > > > I guess we'll need to update the guidelines to be more specific, > especially after the change towards the soft-freeze we have used the > last few releases. During the soft-freeze, it has everything to do with > package building, so here we are most careful about functional changes > that may break functionality requiring either large rebuilds or other > time consuming fixes that may delay the release. During the slush, as > we have now, it's all about potential rebuilds and retagging. As the > tree has been tagged, commits will no longer affect what goes into the > release, but if a security vulnerability turns up requiring a refresh of > a given package, if that ports has changed all those changes, including > things like shared library bumps etc, will have to be brought in as well > as we can only move the tag forwards. It's a tag, not a branch. > I hope that explains it a bit more in detail, but you're right that the > current guidelines are outdated and should be clarified. > > -erwin >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinYWd0_pKOnPd%2Bpxfb96b7TwO9nVS=gbjc5azr0>