On Sun, Jun 22, 2025, 10:58 Oleg Kalnichevski <ol...@apache.org> wrote:
> On Sun, 2025-06-22 at 10:52 -0400, Gary Gregory wrote: > > On Sun, Jun 22, 2025 at 10:43 AM Oleg Kalnichevski <ol...@apache.org> > > wrote: > > > > > > On Sun, 2025-06-22 at 14:28 +0000, ggreg...@apache.org wrote: > > > > This is an automated email from the ASF dual-hosted git > > > > repository. > > > > > > > > ggregory pushed a commit to branch master > > > > in repository > > > > https://gitbox.apache.org/repos/asf/httpcomponents-client.git > > > > > > > > > > > > The following commit(s) were added to refs/heads/master by this > > > > push: > > > > new cdd8e934d Add missing release notes for 4.3.5 and 4.3.6 > > > > cdd8e934d is described below > > > > > > > > commit cdd8e934d08d6802b874f8f287fa33c83a041ab4 > > > > Author: Gary Gregory <garydgreg...@users.noreply.github.com> > > > > AuthorDate: Sun Jun 22 10:28:31 2025 -0400 > > > > > > > > Add missing release notes for 4.3.5 and 4.3.6 > > > > > > Why? There are not missing. > > > > > > > https://dist.apache.org/repos/dist/release/httpcomponents/httpclient/RELEASE_NOTES-4.3.x.txt > > > > Hi Oleg, > > > > The above is a link to a dist file; the text was missing in the git > > file containing the release notes. > > > > No, it is not. Those releases were released from a stable branch and > not master, like a dozen of other releases, but the release notes are > in the repository. It is unclear to me what makes those two so special. > It is important IMO to have a release history that's continuous without holes somewhere, and master seems like the best place for that. I shouldn't have to hop between branches or various files in git or dist to get this history. This is a good thing for example when one is trying to understand what security fixes ended up in which release. Gary > Oleg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org > For additional commands, e-mail: dev-h...@hc.apache.org > >
