... great idea James and definitely in favor of deprecating things after a certain time instead of artificially bloating the next release with stuff that never gets done. We have a similar concept in place for PRs (I want to say PRs get closed automatically if they get stale after 2 weeks or so). For Jira tickets that timeframe should be longer of course... if we continue with the current pace of new developments/features then I'd say everything that is older than 1 year is ancient history (just to put a number out there).
A Zoom session on that topic would be great... pretty sure that everyone has a slightly different view/concern here. Cheers On Thu, Sep 1, 2022 at 11:50 PM James Dailey <[email protected]> wrote: > Devs - There remains a sizable backlog of issues on the Fineract JIRA, > which clogs up the process a bit. > > @[email protected] <[email protected]>. I noticed that during release 1.8 > that you pushed a few to 1.9. I know that this isn't the first time that > we've kicked those items down the road. > > Would it be ok if we go through now and mark those issues as "Will Not > Fix" if they are older than 3 years? > > And then try to move to group the issues into high, medium, low priority > for the rest? > > I'd be willing to organize a zoom session to review. > > Thanks, > James > > >
