Rely on JIRA for release notes ?

[Tom Zeller]

I guess my question is : should we rely on JIRA for generation of
RELEASE-NOTES.txt ?

For example, there are no issues in JIRA for Spring Extensions for
whatever version comes after the current release 1.2.0, but we
actually added to the API according to Subversion :

 svn log https://svn.shibboleth.net/utilities/spring-extensions -rHEAD:608

 Support both string and boolean to Predicate conversions.
 JSPT-46 Move services down from the IdP...

So, I think we need to bump the minor version from 1.2.0 to 1.3.0
because we added to the API, but the release notes generated by JIRA
for Spring Extensions will not include JSPT-46 since that is in the
Java Support project obviously. Of course, I can just manually copy
the one-line JSP-46 issue to the release notes for Spring Extensions
from Java Support, but I was wondering if we should generate
RELEASE-NOTES.txt from Subversion, since that can be automated.

Also, I think it probably is a good idea to choose a "standard" format
for RELEASE-NOTES.txt across the various projects which depend on
parent-v3 which should include the date and Subversion revision number
of each released version.

I ask because I was figuring out what version to use next for our
IdPv3 dependencies, and JIRA was not sufficient.

Thoughts ?

Thanks.