git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Brian Lyles" <brianmlyles@gmail.com>
Cc: git@vger.kernel.org, phillip.wood123@gmail.com,
	"Jean-Noël AVILA" <jn.avila@free.fr>
Subject: Re: What's cooking in git.git (Mar 2024, #05; Tue, 19)
Date: Thu, 21 Mar 2024 06:02:03 -0700	[thread overview]
Message-ID: <xmqq34sjd9h0.fsf@gitster.g> (raw)
In-Reply-To: <17bea28cf691d3eb.70b1dd9aae081c6e.203dcd72f6563036@zivdesk> (Brian Lyles's message of "Thu, 21 Mar 2024 01:13:54 +0000")

"Brian Lyles" <brianmlyles@gmail.com> writes:

> A strategy that I have seen work well is for any commit making a notable
> change (one that should appear in the release notes) to include an entry
> in a CHANGELOG.NEXT.md file.

While I very much like the idea of distributing the burden of coming
up with an initial draft for an entry in the final release notes, I
am not convinced that the approach to use a single in-tree file
would work well in our distributed development style where the
history is merge-heavy with many topics in flight in parallel.

I can imagine how well the approach for each contributor to give
such a draft entry in the cover letter of their topic would work;
it would be with much less friction compared to a single in-tree
file that will be the source of merge conflicts.




  parent reply	other threads:[~2024-03-21 13:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 16:53 What's cooking in git.git (Mar 2024, #05; Tue, 19) Junio C Hamano
2024-03-20 15:15 ` Brian Lyles
2024-03-20 16:11   ` Junio C Hamano
2024-03-21  1:13     ` Brian Lyles
2024-03-21  1:36       ` Junio C Hamano
2024-03-21  2:04         ` Brian Lyles
2024-03-21 13:02       ` Junio C Hamano [this message]
2024-03-22  1:22         ` Brian Lyles
2024-03-22  1:59           ` Junio C Hamano
2024-03-22  2:47             ` Brian Lyles
2024-03-22  5:14               ` Dragan Simic
2024-03-22 12:39                 ` Max Gautier
2024-03-22 13:25                   ` Dragan Simic
2024-03-22 14:46               ` Junio C Hamano
2024-03-22  5:05             ` Dragan Simic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq34sjd9h0.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=brianmlyles@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jn.avila@free.fr \
    --cc=phillip.wood123@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).