On 2024-08-27 19:41:54 +0200 (+0200), tho...@goirand.fr wrote: [...] > All you wrote is precisely why I am not using these tarballs. I > know we don't agree... :) > > Also, the FTP master do NOT want the changeLog as they are too big > and provide no value when one can check the git repo to find the > same info.
Sure, but the assembled release notes are not nearly as large as the changelog while still relying on having Git history available to build, and the generated authorship list is referred to in the license information for at least one OpenStack project as a stand-in for referencing Git committer metadata. To put it another way, upstream in OpenStack when the project was started in 2010, we were aware that package maintainers preferred signed and clearly versioned tarballs for every release, so that's what we structured our workflows and tooling around providing. In the meantime, package maintainers decided to take advantage of the fact that we use Git repositories in our development workflow but the release process we settled on isn't designed with that in mind, and changing workflows and processes in a developer community that size is sometimes like trying to steer a train. -- Jeremy Stanley
signature.asc
Description: PGP signature
