+1 to always a jira. there's another option to consider, a big one, which is; move to github issues.
+direct IDE integration +direct AI integration +good cross reference between issue and PR Parquet and iceberg use them, and I am coming to appreciate them. github issues aren't as powerful as jira, but how much of that tooling do asf projects use? On Wed, 22 Apr 2026 at 07:11, Ayush Saxena <[email protected]> wrote: > I will go with A as well. I am old school. > * Creating JIRA isn't tough > * We have been doing that since ages > * Trivial/Minor maybe from code point of view, but every contribution > and the contributor is equally valuable, so, I don't want that > situation your ticket is trivial, you don't need credits over Jira, or > your names misses the release note, do some thing ambitious. > > -Ayush > > On Wed, 22 Apr 2026 at 09:40, Xiaoqiao He <[email protected]> wrote: > > > > Prefer A from my side. My points: > > a. How to define trivial or minor changes. We need an explicit > > rule first, then follow it when committing. > > b. It will be difficult for end users to trace these changes without > > JIRA-ID. > > c. Creating JIRA is not hard for contributors, at least for me. > > Thanks. > > > > Best Regards, > > - He Xiaoqiao > > > > On Wed, Apr 22, 2026 at 1:04 AM Chris Nauroth <[email protected]> > wrote: > > > > > +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] > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
