From owner-cvs-ports@FreeBSD.ORG Sun Feb 13 16:37:01 2011 Return-Path: Delivered-To: cvs-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28D06106566B; Sun, 13 Feb 2011 16:37:01 +0000 (UTC) (envelope-from andrej.zverev@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8E3098FC13; Sun, 13 Feb 2011 16:37:00 +0000 (UTC) Received: by vxa40 with SMTP id 40so2181540vxa.13 for ; Sun, 13 Feb 2011 08:36:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=6Pol2cnhiTRvhfTPma6yAAoo6xOGMX7aRuKMPMmwP1E=; b=LI1T1V6Ltdynv7PM3TR7Xu/F2Yj6t8xVmQLNPMo99B4u1WlgUGtWz8YXni86lMM1hk taw6Klah6F/yGbebYsGDluK4aRdd0avhKsR3p8Z85/kM6eKwTuvzw/fgD2wR8eyyu575 C4oTiAwbswg/9BKe5yJcjf9zM+wsCXaYHawnE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=XHd6ENvSk6AiVECKA+Gf2r+sIN/h4v9KbNviH1JVNHvkpr9YUhKEp5MFbz1zJKd1fB e6CwaifC+n1Oqmyog6MLc9P89IWX2XY9eCMo4lO4Zhr2JbhgNPoX8D9T9EaVT/ihF5r3 Vi3IyItPVh0z3vwG2LXoP3rSHIWy9N7dI3sNo= MIME-Version: 1.0 Received: by 10.220.192.133 with SMTP id dq5mr3632067vcb.202.1297615019545; Sun, 13 Feb 2011 08:36:59 -0800 (PST) Sender: andrej.zverev@gmail.com Received: by 10.220.202.5 with HTTP; Sun, 13 Feb 2011 08:36:59 -0800 (PST) In-Reply-To: <20110213160735.GO18095@droso.net> References: <20110213160735.GO18095@droso.net> Date: Sun, 13 Feb 2011 19:36:59 +0300 X-Google-Sender-Auth: gE0VVORD3NFZWIjxsYaSTQAT7mg Message-ID: From: Andrej Zverev To: Erwin Lansing Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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 X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Feb 2011 16:37:01 -0000 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 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 >