> On Jun 28, 2022, at 3:24 AM, Gary Gregory wrote:
>
> The way I've been using changes.xml is slightly different: I record my
> commit ID in dev and in due-to I usually list whomever participated by
> looking at the Jira and/or PR.
>
Yes, I know. Except what shows up in the changes report is
"commit ID" -> "Apache ID"
Gary
On Tue, Jun 28, 2022, 06:24 Gary Gregory wrote:
> The way I've been using changes.xml is slightly different: I record my
> commit ID in dev and in due-to I usually list whomever participated by
> looking at the Jira and/or PR.
>
> Gary
>
> On Tue, Jun 28, 2022, 0
The way I've been using changes.xml is slightly different: I record my
commit ID in dev and in due-to I usually list whomever participated by
looking at the Jira and/or PR.
Gary
On Tue, Jun 28, 2022, 02:13 Ralph Goers wrote:
> I don’t always check the changes.xml and during the frenzy of the CV
I don’t always check the changes.xml and during the frenzy of the CVE releases
I probably
didn’t look at all.
But I don’t think it is wise to go back and change it. For one, we won’t be
updating the sites
of those past releases so modifying them would make the history in the new
release not
Hi Ralph,
On Tue, 28 Jun 2022 at 01:40, Ralph Goers wrote:
> In preparation for the release I am going through changes.xml and am finding
> some issues.
> 1. The dev attribute should always include the uid of the committer who
> performed the commit.
> 2. The due-to attribute should be used to
In preparation for the release I am going through changes.xml and am finding
some issues.
1. The dev attribute should always include the uid of the committer who
performed the commit.
2. The due-to attribute should be used to acknowledge the individual who either
submitted a PR
or provided
