From owner-freebsd-stable@FreeBSD.ORG Mon Sep 29 03:44:19 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 16801403; Mon, 29 Sep 2014 03:44:19 +0000 (UTC) Received: from ruggedinbox.com (ruggedinbox.com [94.156.77.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C8344F7; Mon, 29 Sep 2014 03:44:18 +0000 (UTC) Message-ID: In-Reply-To: <20140929031120.GI75063@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <20140929025102.GH75063@hub.FreeBSD.org> <20140929031120.GI75063@hub.FreeBSD.org> Date: Mon, 29 Sep 2014 05:42:30 +0200 Subject: Re: FreeBSD 10.1-BETA3 Now Available From: beeessdee@ruggedinbox.com To: "Glen Barber" Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: FreeBSD Release Engineering Team , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 03:44:19 -0000 On Mon, September 29, 2014 5:11 am, "Glen Barber" wrote: > On Sun, Sep 28, 2014 at 10:51:02PM -0400, Glen Barber wrote: >> On Mon, Sep 29, 2014 at 04:45:21AM +0200, beeessdee@ruggedinbox.com >> wrote: >> > Why 10.1-BETA3 announcement signed with not usual PGP key? >> > >> >> Because it is a BETA build, and not a release. >> > > After re-reading your reply, I realize I haven't sent my last set of PGP > subkeys. Thanks gjb@! I will watch for those, so I can verify BETA3 and later before testing/using. (But sad nobody before noticed and asked you. I thought I am very slow.) > Anyway, this is not RE-related. Jah, 'RE-related' would be public verify method for whole svn repo tied to audit trail of release process. :-( Anyway... thanks again for clarify the mysterious keyid 0x478FE293. (fyi I checked keyservers too before I mail the list.)