From owner-freebsd-hackers@freebsd.org Sun Jun 23 22:09:36 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25DAF15B3085 for ; Sun, 23 Jun 2019 22:09:36 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FA017235E; Sun, 23 Jun 2019 22:09:35 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-io1-xd2d.google.com with SMTP id r185so412588iod.6; Sun, 23 Jun 2019 15:09:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=rXRzJNTrCwZIGd6+vNSwYead9v9iPxABDxb/K+0ZOC4=; b=mJq5UKdDO2dCatqcjGQX810m9UzAGjqBGHASeZlVRasUNq/rrj5OIR1J6FvuG3dTX9 abICRtnr6asJcdwLxc4eYQzw0uPZ/ZbWCS2CVFNRvL6qKLzwDWlxZMh51fOODJ4EQZ3Q 1JOgVBLxYM92uXVI5qY0Wa2heNT3oSoZbOm8YUl+3iv5+mROoJACS1/EWIrYr/s/Ofhz VPuw8RplKvNeYLQFzRtBaBThtW5h9EG5jiH/SnQN+jZTP9nUY31aXKNarK9yMEai2HXd uT0ixcDmDrDFrfM68fJG05AvJtZPq91TV9ptYHv7X+Tp2t04CLC+KDjypFZkfgAYA50d YOSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=rXRzJNTrCwZIGd6+vNSwYead9v9iPxABDxb/K+0ZOC4=; b=pbpLyjM4X+7tiPMz7AP7q8GQBJq/+hAdszdJ/uJHMRY2RcRed0I/1a+ELJpoqqjM4z 2x5gBsxx5qI/Z/R8wCw8XdmNFyvzYkMXgn4TZ7VqvRQXhBJkhb/B2XSd/eMYy3ewqKm9 Jf3OCiAcI+hySBu0fRwRgiWs8Qr4JRZXfNvrzlEgzn8npPxlZb8oXaZirSE2wOgMtLWQ ZVPD/i5usspIUt56HTGXh2766g25dYumgsF8Jww8sSqRRbAVzYQVvHw6B4mzEIGfyY6T /Vq7F4u+eqnYbGsgUEKij7I5QiI+wgop6PuPi41BrX04mDhY8PiE2ZUyoJxFnnMxk0Y7 cQyQ== X-Gm-Message-State: APjAAAX2LKeKj1db4F9MWphi0pIo3jtNLrRTmnoORmlMbAqn3Ica+jIR xj+sfiwJV/4m7kLHjo2Z5RrqP2wZ X-Google-Smtp-Source: APXvYqz2+sDug1f6Hpb/tvjEW+wr+OMoyJTW9JMBMH9hXs7XQHwrx2BAI8n5Kp+87QBEeoerd+W3yA== X-Received: by 2002:a6b:b804:: with SMTP id i4mr9836870iof.119.1561327774169; Sun, 23 Jun 2019 15:09:34 -0700 (PDT) Received: from raichu (toroon0560w-lp140-05-70-29-85-38.dsl.bell.ca. [70.29.85.38]) by smtp.gmail.com with ESMTPSA id a2sm9046165iod.57.2019.06.23.15.09.33 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Sun, 23 Jun 2019 15:09:33 -0700 (PDT) Sender: Mark Johnston Date: Sun, 23 Jun 2019 18:09:31 -0400 From: Mark Johnston To: Glen Barber Cc: Warner Losh , "freebsd-hackers@freebsd.org" , FreeBSD Release Engineering Team Subject: Re: release notes file Message-ID: <20190623220931.GC50070@raichu> References: <20190623191818.GA84365@raichu> <6B485E5C-9C8A-43C8-BD5A-528A74A61A23@FreeBSD.org> <79B7AEEE-7617-44D8-A16A-C8EC5F95455A@FreeBSD.org> <20190623201943.GB41944@FreeBSD.org> <20190623210959.GB50070@raichu> <20190623215729.GD41944@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190623215729.GD41944@FreeBSD.org> User-Agent: Mutt/1.12.0 (2019-05-25) X-Rspamd-Queue-Id: 2FA017235E X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=mJq5UKdD; spf=pass (mx1.freebsd.org: domain of markjdb@gmail.com designates 2607:f8b0:4864:20::d2d as permitted sender) smtp.mailfrom=markjdb@gmail.com X-Spamd-Result: default: False [-5.63 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.97)[-0.967,0]; FORGED_SENDER(0.30)[markj@freebsd.org,markjdb@gmail.com]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[markj@freebsd.org,markjdb@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[d.2.d.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.95)[ip: (-9.24), ipnet: 2607:f8b0::/32(-3.14), asn: 15169(-2.33), country: US(-0.06)]; MID_RHS_NOT_FQDN(0.50)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jun 2019 22:09:36 -0000 On Sun, Jun 23, 2019 at 09:57:29PM +0000, Glen Barber wrote: > On Sun, Jun 23, 2019 at 05:09:59PM -0400, Mark Johnston wrote: > > Regarding whether RELNOTES entries should be removed, I would prefer to > > keep them at least until head is branched. They would serve as useful > > documentation to users, and if there are multiple people compiling > > release notes they can synchronize in other ways. At least, I would > > wait for it to become a problem before trying to solve it by removing > > entries from RELNOTES. > > > > To your latter point, removing the RELNOTES entries, this is what I sort > of had in mind: > > head -> stable/X -> releng/X.Y: > head/RELNOTES gets truncated after stable/X is created; > stable/X gets truncated after releng/X.Y is created > > For point releases, the workflow is similar as it just excludes head: > stable/X -> releng/X.Y: > stable/X gets truncated after releng/X.Y is created > > In other words, there would be no arbitrarily-long file, but there > would potentially be some overlap for a major release where a dot-zero > release has last-minute new stuff that should be in release notes; it > would grow and shrink as development happens. > > Or, this is how I see it being most beneficial to RE when it comes to > writing release notes, at least. This is what I had pictured as well.