* Nicolas Mailhot via devel: > Le vendredi 10 janvier 2020 à 17:36 +0100, Pierre-Yves Chibon a écrit : >> Good Morning Everyone, >> >> This is not a new idea, it has been presented at flock last year and >> spoken >> about on this very list this fall, so I'd like to push it a little >> further. >> >> Do we want to drop release and changelog from our spec file? >> If we do, how would this work? > > Dropping changelog is easy. Since we have a clean separation of spec > repo (src.fedoraproject.org) and project repo (pagure, gitlab or > elsewhere) the spec should just be assembled from all the > src.fedoraproject.org commit messages not present in the previous > generated changelog That way, you cannot fix typos, add missing CVE IDs, and the like. It's a significant functionality change. It may be possible to auto-generate a %changelog section listing new commits since the last %changelog update. Combined with a tool that people can run before editing the %changelog section manually, to make its contents explicit, I expect that to work. > (that won't work for thinks ike rehat-rpm-config because it does not > separate the project files in a separate repository but it’s high time > it behaved likea normal project, the non separation is a major PITA to > deal with) I have trouble matching this claim to my experience working on redhat-rpm-config. Why is it painful to use Git as it was designed? I don't think it's an improvement if contributors have to figure out how to generate a new upstream tarball for each change. Thanks, Florian _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
