Re: Linking to changes in Commons components

Gary Gregory <[email protected]> Fri, 31 Jul 2026 08:33:02 -0400
Newsgroups gmane.comp.jakarta.commons.devel
Message-ID <CACZkXPww7nNRw5RbOK8Y1g-SJkOM9QvXrW1cen4FNnXLKV8G3w@mail.gmail.com>
On Fri, Jul 31, 2026 at 8:28=E2=80=AFAM 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/co=
mmons-io-2.22.0

Gary

>
> I'm currently using a link into Github - such as
> <https://github.com/apache/commons-io/blob/274cd956de35dc664a2caca200c2d7=
3b2b37efdc/RELEASE-NOTES.txt#L48>
> - is there a better way to do this?
>
> (Context: <https://issues.apache.org/jira/browse/SLING-13268>).
>
> Best regards, Julian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>