On 02/19/15 06:38, Alexis Ballier wrote: > On Thu, 19 Feb 2015 19:34:28 +0800 > Patrick Lauer <patr...@gentoo.org> wrote: > >> On Thursday 19 February 2015 12:31:27 Alexis Ballier wrote: >>> On Wed, 18 Feb 2015 22:48:27 +0100 >>> >>> Michał Górny <mgo...@gentoo.org> wrote: >>>> Dnia 2015-02-18, o godz. 16:11:53 >>>> >>>> "Mike Frysinger (vapier)" <vap...@gentoo.org> napisał(a): >>>>> vapier 15/02/18 16:11:53 >>>>> >>>>> Modified: fcaps.eclass >>>>> Log: >>>>> clarify USE=filecaps intention #540430 >>>>> >>>>> Revision Changes Path >>>>> 1.11 eclass/fcaps.eclass >>>> >>>> Please commit the missing ChangeLog update and remember to update >>>> the ChangeLog after changing any eclass in any way. This is an >>>> official policy for any commits to the Gentoo repository [1] and a >>>> lack of consistency in entries to the ChangeLog is confusing to >>>> our developers and users. >>>> >>>> [1]:http://devmanual.gentoo.org/ebuild-writing/misc-files/changelog/index. >>>> html >>> this policy is about packages; cvs log is *muuuuch* better than any >>> global changelog for eclasses: who will dig into a thousand >>> changelog entries to find what changed in fcaps.eclass ?
Noting in that policy limits it to packages. >>> >>> if you want changelogs in eclass/, make it per-eclass, like it is >>> already per-package. Our current policy is to enforce updating existing Changelogs at the lowest possible level. That means if you really feel strongly about a per-eclass Changelog that would be permissible per the policy. >>> >> >> We've had this discussion before ... so ... > > > what i remember of it is someone adding a ChangeLog file to eclass/ and > sending an email to ask people to fill it. Mind sharing a link ? > > I think I'll add ChangeLog to every category and ask people to fill it > whenever they make changes to a package in that category. This would > have the same level of usefulness as a ChangeLog in eclass/. This kind of comment isn't productive, let's stick to being productive. If you feel that the commit log is "good enough" then open a bug assigned to QA to remove the existing Changelog. If the existing Changelog is removed then our policy would be that it doesn't need to be updated anymore. Not sure how many people would need to sign off on that idea, but that would be the process. Thanks, Zero_Chaos
signature.asc
Description: OpenPGP digital signature
