From nobody Thu Nov 16 03:19:39 2023 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SW4ys0jCwz514Jj; Thu, 16 Nov 2023 03:19:49 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [66.165.241.226]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SW4yr2ZSGz4QRx; Thu, 16 Nov 2023 03:19:48 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1700104780; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wBPCnY43OxQjHdlKWYkNJqBjcGi+0dLfVovlYlYnuCI=; b=4kh5jj4kkthq84iFtXiXpwoJtqaLAiqpav8VCFwMbXEbThaXhy7kbv9jaz2U8mDOFSUw3v /hO6xgvpOF0EJgtfnT/atbMCxiantHwGevqMF2Dmz18S+ClzGoJVepYhpEKY/eH5f7zfa/ GC5DYr4wfvOnnqlgPo4Fl2aKqq8V3NE= Received: from [192.168.1.223] (cpe-24-24-168-214.socal.res.rr.com [24.24.168.214]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 3d9d9019 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Thu, 16 Nov 2023 03:19:39 +0000 (UTC) Content-Type: multipart/alternative; boundary="------------koVe1rSEAnHTQ7IVSnZIv0gx" Message-ID: <23a4bd83-dca4-4e76-a513-9df6671d930d@nomadlogic.org> Date: Wed, 15 Nov 2023 19:19:39 -0800 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [HEADS-UP] Quick update to 14.0-RELEASE schedule To: Glen Barber , John Baldwin Cc: The Doctor , FreeBSD Release Engineering Team , freebsd-current@freebsd.org, freebsd-stable@freebsd.org References: <20231114203654.GB52320@FreeBSD.org> <20231115022701.GM1307@FreeBSD.org> <20231115045231.GN1307@FreeBSD.org> <20231116003030.GO1307@FreeBSD.org> Content-Language: en-US From: Pete Wright In-Reply-To: <20231116003030.GO1307@FreeBSD.org> X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US] X-Rspamd-Queue-Id: 4SW4yr2ZSGz4QRx This is a multi-part message in MIME format. --------------koVe1rSEAnHTQ7IVSnZIv0gx Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 11/15/23 16:30, Glen Barber wrote: > The alternative would be to say nothing at all. > > Either way, it is a productivity, communication drain. It is > a lose-lose situation no matter how one looks at it given the above > context. We either get chastised for being "too open" into insights > delaying an official announcement, or for being "not open enough" when > there is silence from RE when a release does not meet its scheduled > announcement date. Glen I appreciate your transparency and the efforts you have done to keep everyone in the loop.  I think people get excited about new releases, which is probably a good thing.  IMHO i feel you've been striking a good balance. As an operator these updates are really helpful for me as it allows me to adjust timelines on my end for updating my fleet of servers. You and the RE team do an incredible job - and personally I am thankful for the caution and common sense you all bring to this complex process. Cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA --------------koVe1rSEAnHTQ7IVSnZIv0gx Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

On 11/15/23 16:30, Glen Barber wrote:
The alternative would be to say nothing at all.

Either way, it is a productivity, communication drain.  It is
a lose-lose situation no matter how one looks at it given the above
context.  We either get chastised for being "too open" into insights
delaying an official announcement, or for being "not open enough" when
there is silence from RE when a release does not meet its scheduled
announcement date.
Glen I appreciate your transparency and the efforts you have done to keep everyone in the loop.  I think people get excited about new releases, which is probably a good thing.  IMHO i feel you've been striking a good balance.

As an operator these updates are really helpful for me as it allows me to adjust timelines on my end for updating my fleet of servers.  You and the RE team do an incredible job - and personally I am thankful for the caution and common sense you all bring to this complex process.

Cheers,
-pete 

-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA
--------------koVe1rSEAnHTQ7IVSnZIv0gx--