cshannon commented on PR #964: URL: https://github.com/apache/activemq/pull/964#issuecomment-1413534039
> > I agree for the PR, but the Jira should be atomic as it's better for release notes IMHO. We can group several dep updates in one PR/commit as soon as we have one Jira per update. > > That sounds good, I'll go ahead and update JIRA for individual JIRAs for the release notes. Thx Right, for minor stuff there's no reason to have like 10 commits when they can be combined into one commit like this but the major stuff like Spring for sure should be by itself. For Jira I think we should be able to create one top level Jira issue for the minor dependency updates and then have subtasks for each individual update. Then the PR that does the multiple changes at once could just reference the main Jira but the release notes would still list all the individual dependencies because of the sub tasks (I think but need to test) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
