Updating the changes.xml files

Should contributors update the changes.xml file(s), or is that left to the developers?

If so, how should I handle the versioning? Should I increment the patch version to indicate that the tag should be bumped?

E.g., for the FastMath updates, I have the following:

    <release version="4.0.2" date="2025-05-29" description="This is a patch release.">
      <action dev="ryan" type="update" issue="issues/391">
        Replaced custom FastMath implementations of
          sin, cos, tan, sinCos, log1p, log10, log, exp, hypot, cbrt, pow, floor, ceil, and abs
        with delegates to Math
      </action>
    </release>

Contributors can update any file (except changing the license or removing other contributors, of course).
What we usually do is we put TBD in the date and description fields until release is really done.
As Hipparchus is multi-module, we all try to put the entry in the changes.xml files of both the module it pertains to (hipparchus-core in this case) and in the aggregator module.

1 Like