Something I noticed today is that several new contributors have attempted to follow our PR template by referencing GitHub Issue numbers in the PR title rather than Jira ticket numbers.
Some examples (there are more than just these): - https://github.com/apache/spark/pull/55660 - https://github.com/apache/spark/pull/57809 - https://github.com/apache/spark/pull/57356 - https://github.com/apache/spark/pull/57566 > On May 20, 2026, at 5:43 PM, Tian Gao via dev <[email protected]> wrote: > > Now back to our next step. According to my proposal, we had to choose from > one of the following options: > > 1. Explicitly declaring that we need more time for this experiment. 3 or 6 > extra months. > 2. Close the github issues because the maintenance effort is larger than the > benefit. > 3. Decide that using github issues as discussion only is the best way for > spark and keep doing it. > 4. Support github issues as an equivalent to JIRA tickets so PRs can link to > them too. > 5. Fully migrate from JIRA to github issues. I think by default / inertia, we’ve effectively chosen 1, and this causes the point of confusion about ticket numbers I documented above. I am personally in favor of 5—a full migration, at least for new issues going forward. Having two systems that do similar things will always be confusing to some extent. I don’t know if we are ready to re-open this discussion and move things forward. Just wanted to share this observation. Nick --------------------------------------------------------------------- To unsubscribe e-mail: [email protected]
