From owner-freebsd-hackers@freebsd.org Mon Jun 24 17:52:18 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 3859215D4092 for ; Mon, 24 Jun 2019 17:52:18 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-io1-xd41.google.com (mail-io1-xd41.google.com [IPv6:2607:f8b0:4864:20::d41]) (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 95CF580369; Mon, 24 Jun 2019 17:52:17 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-io1-xd41.google.com with SMTP id m24so242248ioo.2; Mon, 24 Jun 2019 10:52:17 -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=jOpNEIlseak6XfSB9qecVyIg6z320iK6tufnV9KpUD0=; b=k5nWuIR1F7hy5wL6c3VyWGjB7lX+D9u9ST7e44MBqE49MYii1RBCq4NJkD8aMySNd+ vym26JSysQWIWgWS6dAMmVCyIy0C2RWQljG9XPdZ9UqLCJc7VncPRKmIboyrdAjjY/Mw wXXyH4mDY3e28WIbxlIRUWfBVo2aCn3r4PdB0YF/krvT2HRBg6EMu4+RetzssnayzUP/ aGGmd27hVOTxgUtyM1zpyZkDfObmBRchAOWKXkDEryO/DgPbv8/kF4qmQYKPK8ABLo/R Zs5ivK1swTejQJrtuVWdcQUXxexDYDk+geDi3fgrr658R3u3FBdNE9ZJUzlwEAzxvXRY 6okA== 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=jOpNEIlseak6XfSB9qecVyIg6z320iK6tufnV9KpUD0=; b=eDM+EaJSKn04ua1k6UHD47Hv1hAYgW8S74M1XiWDWcKjGLFxfmiM3B3V3y+7lOYxc7 R3CO7YjHX0xLl2R4DZrPId3AI168YePbxDyG9fChhvm4XBjuEchWYFeVd9D/KJxHV4lb I3JXAFGudRzh7z98DrKYzoXeYZsW7cn7O27hna50K9qPUTWDlrV4LSDRP18SnCCvqvQV ShdwVU0jb6UBGFvUHxyJkrLg02U1wLxbVdNlZuZ7B+cttwLC7QXhyh3jP9fsQ+gP08Tz kAeS6H2OLQp6nUBYLlYzZmtFkV2NaKIyYq5QPd7MaMAIOeY5zbPrK8waUUtoEPbf3q2t 0wpQ== X-Gm-Message-State: APjAAAWqbiwTZJQn/IEx1YrydQ+/9TQ2QkKlPe3US7xWj5PNY3+aWpZc c65XeNQDPeOvVvM32IkVuv/Ml/3x X-Google-Smtp-Source: APXvYqx63+LQIamqHMa1Zh4QZTPKuxRa7AKuZDjk3i5uWOfjlmv4qCM8qo/xdRHOeCZsua/MTj0l5A== X-Received: by 2002:a6b:7f0b:: with SMTP id l11mr113762531ioq.282.1561398736589; Mon, 24 Jun 2019 10:52:16 -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 p9sm10679666ioj.49.2019.06.24.10.52.15 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Mon, 24 Jun 2019 10:52:15 -0700 (PDT) Sender: Mark Johnston Date: Mon, 24 Jun 2019 13:52:11 -0400 From: Mark Johnston To: Baptiste Daroussin Cc: freebsd-hackers@freebsd.org, re@freebsd.org Subject: Re: release notes file Message-ID: <20190624175211.GA66843@raichu> References: <20190623191818.GA84365@raichu> <20190624135737.42mf3fi7q75xipsx@ivaldir.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190624135737.42mf3fi7q75xipsx@ivaldir.net> User-Agent: Mutt/1.12.0 (2019-05-25) X-Rspamd-Queue-Id: 95CF580369 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=k5nWuIR1; spf=pass (mx1.freebsd.org: domain of markjdb@gmail.com designates 2607:f8b0:4864:20::d41 as permitted sender) smtp.mailfrom=markjdb@gmail.com X-Spamd-Result: default: False [-3.57 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[freebsd.org]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-0.88)[ip: (1.15), ipnet: 2607:f8b0::/32(-3.15), asn: 15169(-2.33), country: US(-0.06)]; DKIM_TRACE(0.00)[gmail.com:+]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCVD_IN_DNSWL_NONE(0.00)[1.4.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]; NEURAL_HAM_SHORT(-0.98)[-0.981,0]; FORGED_SENDER(0.30)[markj@freebsd.org,markjdb@gmail.com]; MIME_TRACE(0.00)[0:+]; MID_RHS_NOT_FQDN(0.50)[]; 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] 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: Mon, 24 Jun 2019 17:52:18 -0000 On Mon, Jun 24, 2019 at 03:57:37PM +0200, Baptiste Daroussin wrote: > On Sun, Jun 23, 2019 at 03:18:18PM -0400, Mark Johnston wrote: > > Hi, > > > > Today we add a Relnotes tag to commits that warrant a release note. > > My impression is that it doesn't work so well: if a committer forgets > > or doesn't know to add one there's no way to amend the commit message > > (same for MFCs), and a commit message isn't a convenient place to write > > the text of a release note. I would like to propose adding a top-level > > RELNOTES file instead, which like UPDATING would document notes for > > specific commits. It would be truncated every time the head branch is > > forked, and changes to it would be MFCed. This fixes the > > above-mentioned problems and would hopefully reduce the amount of time > > needed by re@ to compile release notes. > > > > For example: > > > > Index: RELNOTES > > =================================================================== > > --- RELNOTES (nonexistent) > > +++ RELNOTES (working copy) > > @@ -0,0 +1,8 @@ > > +Release notes for FreeBSD 13.0. > > + > > +r349286: > > + swapon(8) can now erase a swap device immediately before > > + enabling it, similar to newfs(8)'s -E option. This behaviour > > + can be specified by adding -E to swapon(8)'s command-line > > + parameters, or by adding the "trimonce" option to a swap > > + device's /etc/fstab entry. > > > > What do folks think? > > I do like this idea, and maybe it should be made in a parseable format, so that > it can serve to create some messages to display while running pkg upgrade (for > pkgbase). > > pkg knows to only print message when going from a given revision of a package to > another (and only in this case) to avoid having too many noise to the output. Can you explain a bit further? I'm only familiar with pkg-message, which is unstructured and always printed AFAIK. > I think it would be a nice feature for pkgbase :)