If a component has not been released yet, then, yes, it makes sense to not track these changes. Thank you for clarifying.
Gary On Tue, Nov 24, 2020, 14:55 Bruno P. Kinoshita <ki...@apache.org> wrote: > I left a comment when merging in Git (thought it would appear in here, > but it didn't, sorry). [functor] has not been released yet. So I thought it > wouldn't be necessary to have an entry in changes.xml as we are not > updating from version X to Y. > > On Tuesday, 24 November 2020, 1:53:36 pm UTC, Gary Gregory < > garydgreg...@gmail.com> wrote: > > Please don't forget to update changes.xml when you merge a PR. It's > simpler, more transparent, and provides info for attribution. > > TY, > Gary > > ---------- Forwarded message --------- > From: <ki...@apache.org> > Date: Tue, Nov 24, 2020, 02:25 > Subject: [commons-functor] branch master updated (1e3145b -> 9b217ed) > To: comm...@commons.apache.org <comm...@commons.apache.org> > > > This is an automated email from the ASF dual-hosted git repository. > > kinow pushed a change to branch master > in repository https://gitbox.apache.org/repos/asf/commons-functor.git. > > > from 1e3145b Merge pull request #10 from > > apache/dependabot/maven/org.apache.maven.plugins-maven-changes-plugin-2.12.1 > add 0c94e8d Bump maven-pmd-plugin from 3.13.0 to 3.14.0 > new 9b217ed Merge pull request #13 from > apache/dependabot/maven/org.apache.maven.plugins-maven-pmd-plugin-3.14.0 > > The 1 revisions listed above as "new" are entirely new to this > repository and will be described in separate emails. The revisions > listed as "add" were already present in the repository and have only > been added to this reference. > > > Summary of changes: > pom.xml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) >
