Hi Larry, Thank you so much for your thoughts on maintaining historical records. I agree this may not be helpful immediately. I'll explore if there is a way to streamline things with Livy JIRA.
Thanks for the suggestions! Warm Regards, Arnav On Thu, Feb 26, 2026 at 6:13 PM larry mccay <[email protected]> wrote: > Thanks for the valid question, Arnav! > > I agree with Marco and I believe that the Jira link to email is required > for Apache history and records. > > Maybe there have been some changes in the thinking from the foundation that > I am not aware of wrt github issues. > @Jean-Baptiste Onofré <[email protected]> - anything you are aware of > here? > > Unless there is an official stance from ASF on this, I think we should stay > with Jira for the time being. > > On Thu, Feb 26, 2026 at 5:03 AM Marco Gaido <[email protected]> > wrote: > > > Hi, > > > > JIRA has some features that are not present in Github issues to the best > of > > my knowledge. E.g. marking blockers for a release, tracking in which > > release something has been solved, ... So as an history for users JIRA is > > probably a better option and for this reason I would stick with JIRA, > even > > though Github would streamline dev operations. > > > > Thanks, > > Marco > > > > Il giorno gio 26 feb 2026 alle ore 08:52 Arnav Balyan < > > [email protected]> ha scritto: > > > > > Hi team, > > > > > > We currently use JIRA for tracking issues and linking them to PRs. > > > > > > GitHub provides built in issue tracking with native integration to PRs. > > > Would it help to use GitHub issues for tracking items? > > > > > > It may help remove the prerequisite of creating a new JIRA account for > > new > > > contributors and avoid switching between systems to open issues and > > create > > > PRs. > > > > > > Would love to hear what you think. > > > > > > Thanks! > > > Arnav > > > > > >
