Hi David,
thanks for the clean-up!
Regarding your questions:
(1) I am +1 with limiting the scope of the issue type "dependency
upgrade" to user-facing dependencies.
Sadly, we cannot add new issue types like "build/test dependency
upgrade" without involving infra but if we agree on tagging
Hello David,
I agree that on (my) customer side, dependency upgrade of the
build/test tools aren't as important as dependency upgrades of code
actually part of TomEE runtime, so if it is possible to split the list
in release notes between runtime dependencies upgrade versus
build/test-time ones,
Side note, I used a command-line tool I wrote called 'jamira' to file most of
these and have them appear as the person who originally filed the issue and did
the work.
A couple examples:
jamira create issue --fix-version=9.0.0-M9 --reporter=ruelland
--assignee=ruelland --type="Dependency
Hey All,
I did some cleanup of the dependency upgrade JIRAs for 9.0.0-M8. Here's what
they look like:
• [TOMEE-3800] - Apache DBCP 2.9.0
• [TOMEE-3999] - Apache MyFaces 3.0.2
• [TOMEE-4006] - slf4j 1.7.36
• [TOMEE-4009] - WSS4J 2.4.1
• [TOMEE-4010] -
