I have been doing the same thing as Gary, I will prune out my duplicates shortly.
-ck On Mon, Jun 3, 2019, at 10:55, Ralph Goers wrote: > Am I sure about what? Who cares when the branches diverged? If a fix or > feature was introduced prior to 3.0 then it shouldn’t be listed as something > introduced in 3.0. Changes.xml should reflect the version the fix or feature > was first added. > > Please remove the duplicates from 3.0. > > Ralph > > > On Jun 3, 2019, at 4:14 AM, Gary Gregory <[email protected]> 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 <[email protected]> > > 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 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 and > >> remove the duplicates? > >> > >> Ralph > >> > > >
