Am 31.07.2026 um 14:33 schrieb Gary Gregory:
On Fri, Jul 31, 2026 at 8:28 AM Julian Reschke <[email protected]> wrote:
Hi there,
what's the best way to link (as in JIRA) to changes in Commons
components, such as IO?
AFAICT, only *bugs* have a Jira ticket.
The Release Notes (as in
<https://commons.apache.org/proper/commons-io/changes.html#a2.22.0>)
list the changes, but the individual changes do not have a unique
identifier.
It all depends on what your definition of "individual changes" is. For
commits, you can ask git with "git log" or you can ask GitHub, for
example:
https://github.com/apache/commons-io/compare/rel/commons-io-2.21.0...rel/commons-io-2.22.0
...
Yes, I'm aware of that :-)
That said, the granularity of Git commits is not ideal.
So, what about giving in each line a stable identifier (could be
auto-generated), so one could link *into* the change log file? Such as
"https://commons.apache.org/proper/commons-io/changes.html#a2.22.0-change-1";?
...and - while I'm writing this - I realize that *something* like that
only (sort of) works:
<https://commons.apache.org/proper/commons-io/changes.html##:~:text=BoundedReader%20now%20extends%20ProxyReader>
Best regards, Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
