Re: changes.xml in 3.0

2019-06-03 Thread Carter Kozak
ke this is to track changes from when > > the branches diverged. > > > > Gary > > > > On Sun, Jun 2, 2019 at 5:45 PM Ralph Goers > > wrote: > > > >> Gary, > >> > >> In looking at the changes.xml in 3.0 it looks like you are addin

Re: changes.xml in 3.0

2019-06-03 Thread Ralph Goers
> On Jun 3, 2019, at 4:14 AM, Gary Gregory wrote: > > Are you sure? The reason I did it like this is to track changes from when > the branches diverged. > > Gary > > On Sun, Jun 2, 2019 at 5:45 PM Ralph Goers > wrote: > >> Gary, >> >> In looking

Re: changes.xml in 3.0

2019-06-03 Thread Gary Gregory
Are you sure? The reason I did it like this is to track changes from when the branches diverged. Gary On Sun, Jun 2, 2019 at 5:45 PM Ralph Goers wrote: > Gary, > > In looking at the changes.xml in 3.0 it looks like you are adding > notations to both the 2.x and 3.x releases. That

changes.xml in 3.0

2019-06-02 Thread Ralph Goers
Gary, In looking at the changes.xml in 3.0 it looks like you are adding notations to both the 2.x and 3.x releases. That doesn’t make any sense. A change should be noted ONLY in the release in which it was first published. Can you please go through all the actions you added to the 3.0 release