Re: [commons-codec] branch master updated: Track changes

2020-11-26 Thread Gary Gregory
Then do it because that's the "style" we've been using, just like we use the changes.xml "issue" attribute to refer to the associated Jira issue, but in this case it's not a Jira #, it's a PR#. Note that the Maven changes plugin does not know about PRs in that field, so we use the PR# in the

Re: [commons-codec] branch master updated: Track changes

2020-11-26 Thread Gilles Sadowski
Hello. Le jeu. 26 nov. 2020 à 15:22, Gary Gregory a écrit : > > May you please show the PR number in the description? See the first action > in the list. This will give us better provenance for changes. At first thought, I don't see that this info belongs in the "changes" file. [Rationale:

Re: [commons-codec] branch master updated: Track changes

2020-11-26 Thread Gary Gregory
May you please show the PR number in the description? See the first action in the list. This will give us better provenance for changes. TY! Gary On Thu, Nov 26, 2020 at 9:13 AM wrote: > This is an automated email from the ASF dual-hosted git repository. > > aherbert pushed a commit to branch