+1 (non-binding) For the next steps 4 and 5, if we go there, we can use different patterns to distinguish the JIRA and GitHub tickets.
[SPARK-12345][CORE] A patch that links to a JIRA ticket [SPARK #12345][CORE] A patch that links to a GitHub issue Note: a space is required between "SPARK" and "#12345". GitHub can recognize the #12345 and hyperlink it to the issue automatically. Thanks, Cheng Pan > On Feb 13, 2026, at 09:32, Tian Gao via dev <[email protected]> wrote: > > We had a very involved discussion in the [DISCUSS] thread > (https://lists.apache.org/thread/tnhhys28btqmwfbccx7582095jotyh7c) I sent a > few weeks ago. > > After considering opinions from the community, I have a more conservative > proposal and I want to move this to a procedural vote, as there will be no > mandatory code change in spark. > > For a procedural vote, we need a majority approval (at least 3 binding +1 and > more +1 than -1) > https://www.apache.org/foundation/glossary.html#MajorityApproval > > Here's my proposal: > > 1. Open github issues > 2. Create an issue template with > a. option of "Bug", "New Feature", "Improvement" (we can add more if we > need it in the future) > b. description > c. spark version > 3. Create labels for the options in 2.a, spark versions, and for common > components. > 4. The PR process keeps the same (requiring a JIRA ticket). > * 5 (Optional). Build a bot that can create a JIRA from an issue with a > simple label > > This experimental phase will last for 3 months. Then we must choose the next > step from: > > 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. > > Tian Gao
