Agreed, +1 Any old tickets that have been resolved but not closed can probably be assumed to have been correctly fixed. Otherwise someone would have likely ran into the issue and reopened the ticket.
And if we do discover an issue wasn't fixed, we can also reopen a ticket or create a new one. Also, pruning these old tickets will make it easier to stay on top of resolved ticket verification and maybe make getting involved with verification for new contributors less intimidating. On 5/19/21 7:51 AM, Sood, Harinder wrote: > Agreed > > > Sincerely, > Harinder Sood |Director (Senior Project Manager) > > [email protected] > M 240 805 4219 > Work: 410 290-1411 x122 > Connect with us! > > > > The information contained in this transmission is for the personal and > confidential use of the individual or entity to which it is addressed. If the > reader is not the intended recipient, you are hereby notified that any > review, dissemination, or copying of this communication is strictly > prohibited. If you have received this transmission in error, please notify > the sender immediately > > > -----Original Message----- > From: Interrante, John A (GE Research, US) <[email protected]> > Sent: Wednesday, May 19, 2021 7:46 AM > To: [email protected] > Subject: RE: 224 legacy Resolved Daffodil JIRA tickets > > No one seems to have expressed an opinion, so I think it would be acceptable > to close all those resolved tickets over two years old. :) > > John > > From: Thompson, Dave <[email protected]> > Sent: Tuesday, May 18, 2021 1:12 PM > To: [email protected] > Subject: EXT: 224 legacy Resolved Daffodil JIRA tickets > > All, > > There are currently 224 Daffodil JIRA tickets resolved in previous releases, > all but 2 from v2.5.0 (1/2/2020) and earlier. > > I want to check with the group to see if it would be acceptable to close > these tickets with "Closed due to no activity." > > Any other suggestions would be appreciated. > > Thanks > > Dave > > > Dave Thompson | Senior Engineer, Services > [cid:[email protected]][cid:[email protected]] > [email protected]<mailto:[email protected]> > (410) 290-1411 x162 > Connect with us! > [cid:[email protected]][cid:[email protected]]<https://www.linkedin.com/company/owlcyberdefense/>[cid:[email protected]][cid:[email protected]]<https://twitter.com/owlcyberdefense> > [cid:[email protected]][cid:[email protected]]<https://owlcyberdefense.com/resources/events/> > > The information contained in this transmission is for the personal and > confidential use of the individual or entity to which it is addressed. If the > reader is not the intended recipient, you are hereby notified that any > review, dissemination, or copying of this communication is strictly > prohibited. If you have received this transmission in error, please notify > the sender immediately > > >
