elharo commented on pull request #32: URL: https://github.com/apache/maven-site-plugin/pull/32#issuecomment-647508322
Latest communication from @rfscholte was that dependency upgrades should just happen without JIRA issues. I'm inclined to agree, but if the community decides we must have JIRA issues for each dependency upgrade they can be added to dependabot PRs at the cost of some extra manual effort. There's a meta-issue here that every developer on the project has their own workflow, none of which fully match our outdated documentation on dev practices, and many of which contradict each other. As a general principle I prefer automation over convention. E.g. if we shouldn't use squash commits, then the squash commit button should be disabled on the repo rather than expecting devs not to press it. There are many other examples of this. If there are accepted conventions for code commits, it would be worth investing some time to enforce in our systems. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
