+1 for B. I think some other projects use this policy, and it works well for them.
Keep in mind that release notes automation is driven from the release note field in JIRA, so make sure to use JIRA if you want it in the release notes. I guess though by definition anything worthy of a release note is non-trivial. Chris Nauroth On Tue, Apr 21, 2026 at 1:55 AM Cheng Pan <[email protected]> wrote: > +1 to B > > MINOR. This is title of the pull request > > I suggest adopting such a standard prefix for small changes. > > Thanks, > Cheng Pan > > > > > On Apr 21, 2026, at 08:32, Aaron Fabbri <[email protected]> wrote: > > > > Mea culpa: I recently merged a trivial, one-commit PR without an > > accompanying Jira. > > > > Cheng Pan mentioned this is probably not accepted practice: > > > > https://github.com/apache/hadoop/pull/8439#issuecomment-4276717996 > > > > Looks like he was right according to our How To Contribute guide[1]. > > > > Filing Jiras for trivial changes like this (fixing spelling in comments) > > creates clutter and wastes time, but there may be some reasons we want > this. > > > > Some options: > > A. Require a JIRA. > > B. Allow a standard prefix like "trivial:" or "MINOR:" in place of the > Jira > > ID. > > C. Send Fabbri straight to jail and never speak of this again. > > > > A compromise for A could be to file a permanent "Trivial Changes" JIRA > > explaining it applies to non-code changes of limited scope. I could add > > that to the contribution guide if people liked that idea. > > > > Apologies if I missed previous discussions about this. Thanks, > > Aaron > > > > 1. > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=70255755#HowToContribute-Provideapatch > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
