Cleaning up the JIRA

[James Dailey <ja...@gmail.com>]

Devs - There remains a sizable backlog of issues on the Fineract JIRA,
which clogs up the process a bit.

@aleks@apache.org <al...@apache.org>. 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

Re: Cleaning up the JIRA

[Bharath Gowda <bg...@mifos.org>]

Hi James,

+1 from my side for the Idea, I would like to help in the clean-up and
attend the zoom meeting as well.

Regards,
Bharath
Lead Implementation Analyst | Mifos Initiative
Skype: live:cbharath4| Mobile: +91.7019635592
http://mifos.org  <http://facebook.com/mifos>
<http://www.twitter.com/mifos>


On Sat, Sep 3, 2022 at 11:49 AM Bruce <br...@gmail.com> wrote:

>
> Good ideas James and Aleks. When can we have the Zoom meeting on this?
>
> On Fri, Sep 2, 2022 at 4:11 AM Aleksandar Vidakovic <al...@apache.org>
> wrote:
>
>> ... 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 <ja...@gmail.com>
>> wrote:
>>
>>> Devs - There remains a sizable backlog of issues on the Fineract JIRA,
>>> which clogs up the process a bit.
>>>
>>> @aleks@apache.org <al...@apache.org>. 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
>>>
>>>
>>>

Re: Cleaning up the JIRA

[Bruce <br...@gmail.com>]

Good ideas James and Aleks. When can we have the Zoom meeting on this?

On Fri, Sep 2, 2022 at 4:11 AM Aleksandar Vidakovic <al...@apache.org>
wrote:

> ... 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 <ja...@gmail.com>
> wrote:
>
>> Devs - There remains a sizable backlog of issues on the Fineract JIRA,
>> which clogs up the process a bit.
>>
>> @aleks@apache.org <al...@apache.org>. 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
>>
>>
>>

Re: Cleaning up the JIRA

[James Dailey <ja...@gmail.com>]

*Zoom Meeting on JIRA Ticket Clean Up*
Tuesday, 13th September 2022
1400 GMT
0700 Seattle

Posting the zoom info in the wiki.
https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up




On Sat, Sep 3, 2022 at 8:17 AM James Dailey <ja...@gmail.com> wrote:

> Thanks Alex
>
> How about Tuesday following, September 13th.
> 0700PDT
>
> Simply accept the calendar invite.
>
> I’ll then invite everyone else
>
>
>
> On Thu, Sep 1, 2022 at 6:11 PM Aleksandar Vidakovic <al...@apache.org>
> wrote:
>
>> ... 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 <ja...@gmail.com>
>> wrote:
>>
>>> Devs - There remains a sizable backlog of issues on the Fineract JIRA,
>>> which clogs up the process a bit.
>>>
>>> @aleks@apache.org <al...@apache.org>. 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
>>>
>>>
>>> --
> Sent from Gmail Mobile
>

Re: Cleaning up the JIRA

[Aleksandar Vidakovic <al...@apache.org>]

... 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 <ja...@gmail.com> wrote:

> Devs - There remains a sizable backlog of issues on the Fineract JIRA,
> which clogs up the process a bit.
>
> @aleks@apache.org <al...@apache.org>. 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
>
>
>