Le dim. 8 déc. 2024 à 23:03, Elliotte Rusty Harold <elh...@ibiblio.org> a écrit :
> On Sun, Dec 8, 2024 at 9:47 PM Slawomir Jaranowski > <s.jaranow...@gmail.com> wrote: > > > > Hi, > > > > I see that more and more PR are not connected to Jira issues ... > > So we simply take a decision and formally accept what we do > > > > I think that might be simply related to what the PRs do. Accrual bug > fix and new feature PRs are usually connected to Jira. issues. > Refactoring and cleanups generally aren't, and that's as it should be > IMHO. As long as Jira issues are used to create release notes, we > shouldn't file a Jira issue for anything that doesn't deserve a > release note, and changes that don't directly impact users of the > plugin don't deserve release notes. > > There's some disagreement about whether dependency upgrades should > have Jira issues. Personally I think not, both because this doesn't > directly impact how a user interacts with the plugin, and also because > dependabot isn't smart enough to do that automatically. If folks > really, really want Jira issues for every .0.0.1 update, then we might > as well turn off dependabot. > Not sure how that's related, apart from the fact that it takes some time. Though that's not true anymore. I came up with the following script which I'm using everytime I start from code with no prior JIRA issue: https://gist.github.com/gnodet/78c30360a56c02a5cd777a624b5549c3 A simple command from the terminal will create the issue given the PR number and link those. This works for dependabot PRs too. > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- ------------------------ Guillaume Nodet
