From owner-freebsd-pkg@FreeBSD.ORG Fri Apr 3 15:07:21 2015 Return-Path: Delivered-To: pkg@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 651AFA9A; Fri, 3 Apr 2015 15:07:21 +0000 (UTC) Received: from mail.egr.msu.edu (boomhauer.egr.msu.edu [35.9.37.167]) by mx1.freebsd.org (Postfix) with ESMTP id B5A3C622; Fri, 3 Apr 2015 15:07:20 +0000 (UTC) Received: from boomhauer (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id B28773DD39; Fri, 3 Apr 2015 11:07:19 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by boomhauer (boomhauer.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cWoydLr3Dor5; Fri, 3 Apr 2015 11:07:19 -0400 (EDT) Received: from EGR authenticated sender mcdouga9 Message-ID: <551EACA7.8060008@egr.msu.edu> Date: Fri, 03 Apr 2015 11:07:19 -0400 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Baptiste Daroussin , pkg@FreeBSD.org Subject: Re: [CFT] Call for testing pkg 1.5.0 References: <20150331190323.GF30115@ivaldir.etoilebsd.net> In-Reply-To: <20150331190323.GF30115@ivaldir.etoilebsd.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2015 15:07:21 -0000 On 03/31/2015 15:03, Baptiste Daroussin wrote: > Hi all, > > We just released pkg 1.5.0 beta1 (in ports-mgmt/pkg-devel), > > Please test and report as much bugs as you can! > We could be very grateful if regressions tests could be provided along with the > bug reports :) > > Plan is to release 1.5.0 as soon as possible > > Best regards, > Bapt > When the rapid cycle of bugreport-> fix slows down in the RC stage, could you give a heads up and ETA before final release (2-3 weeks?) I will probably be out of town for this release but my inclinations to test are rising. In the past, the final release came very quickly after a number of reported bugs were fixed. Fortunately 1.4.0 was good. I feel the late RC stage needs a short announced period of a week or more to let risk-averse testers know that it is worthwhile to start testing without concern of almost daily fixes. Thanks.