Feel free to edit as you see fit ;-) Gary
On Fri, Oct 29, 2021, 20:26 sebb <seb...@gmail.com> wrote: > I'm inclined to agree with Gilles that updates to plugins should only > be noted where they affect users of the code, i.e. direct > dependencies. > > The useful changes are being shouted down by the various plugin changes. > > In particular, updates to actions are completely irrelevant as they > only affect our GitHub installation. > > On Sat, 30 Oct 2021 at 01:13, Gary Gregory <garydgreg...@gmail.com> wrote: > > > > IMO, each component can do as it best sees fit. I like the idea of the > file > > being a summary of all changes. RE updates to dependencies and plugins, > > these will matter to some but not others, it depends on how you use the > > component. I see it as making visible and transparent the kind of > attention > > to detail we have (or not). > > > > Gary > > > > On Fri, Oct 29, 2021, 18:36 Gilles Sadowski <gillese...@gmail.com> > wrote: > > > > > Hello. > > > > > > Referring to e.g. the recent > > > https://commons.apache.org/proper/commons-cli/changes-report.html > > > I notice that almost half the reported changes concern build's plugins > > > updates. > > > Shouldn't "changes.xml" only report modifications of the code source, > i.e. > > > things that are of direct interest to users of the component? > > > > > > Regards, > > > Gilles > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
