You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by James Dailey <ja...@gmail.com> on 2022/10/10 17:27:32 UTC
Re: Cleaning up the JIRA
+1 (binding)
We have three binding votes (PMC members) and support from active community
members. Thank you.
We have left this open for community input for over two weeks.
So, to re-enforce our process: this is closed and we proceed to
implementation of this set of policies and actions.
I shall move this to a wiki page with the clarifications that Avik offered.
On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io> wrote:
> Hi James, Devs,
>
> +1
>
> There should be some bulk interfaces or JIRA APIs to drive via pipelines /
> actions to make it simpler to execute as many other communities do.
>
>>
>> 1. *At each release cycle*, a further list of tickets will be sorted
>> based on which versions are affected. Versions older than THREE ago will be
>> considered "non-active".
>>
>> To clarify for other readers, the bold part is applicable to minor/major
> release cycles and not for patch / hotfix releases.
>
> With best regards,
> Avik.
>
> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <lu...@gmail.com>
> wrote:
>
>> +1
>>
>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>> cheetah@monkeysintown.com> a écrit :
>>
>>> +1
>>>
>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com> wrote:
>>>
>>>> +1
>>>>
>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org> wrote:
>>>>
>>>>> +1 for the suggested approach.
>>>>>
>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Devs -
>>>>>>
>>>>>> We currently have a lot of open and stale tickets, with the average
>>>>>> days open being over 1000 days (over the past two years on any given
>>>>>> day
>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>> See details I shared on wiki
>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>> including recording. If there is no objection we will begin this
>>>>>> clean up in the next week or so.
>>>>>>
>>>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>>>> generated and published to the list. The message will be to please review.
>>>>>>
>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>> ticket indicating their interest in working on the ticket further
>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>> person self-assigning it to themselves.
>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>> of "Auto Closed"
>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>> further review and may be re-opened, with cause.
>>>>>> 3. *At each release cycle*, a further list of tickets will be
>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>> will be considered "non-active".
>>>>>> 1. NB: This is a formalization of a practice we have, which
>>>>>> is to deprecate older versions and encourage our users to upgrade to the
>>>>>> most recent stable release. As we are on version 1.8 now, any issue
>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>> version 1.5 becomes "unsupported".
>>>>>> 2. This led to a further discussion of release strategy -
>>>>>> which I will start as a different thread. The main point being, if a
>>>>>> release is no longer a supported release, then those tickets are to be
>>>>>> archived.
>>>>>> 4. *Issue Reporting and Cleanliness: *We will require the
>>>>>> tickets to include "Version affected" and "Component" to be filled
>>>>>> out. This allows the sorting above and provides for the ability
>>>>>> to trace the origin of the issue. We also seek to have better ticket
>>>>>> reporting, meaning a clear set of criteria for "Bug" vs
>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>> 5. We will hold a regular - monthly - issue triage meeting to
>>>>>> coordinate on tickets.
>>>>>> 6. We noted that many of the issues on the list and some of
>>>>>> the Jira tickets are related to configuration and setup and suggest better
>>>>>> knowledge base management. We are interested in people taking an active
>>>>>> role in that.
>>>>>> 7. *Release Cycles: *We noted that we have gotten a number of
>>>>>> major improvements such that version 1.8 is very different from 1.5 (less
>>>>>> than two years ago). A new topic is thus to move to a Major release cycle
>>>>>> Version 2.0, and to consider a Long-Term-Support version of the Fineract1.x
>>>>>> . I can kick that off on a new thread as well.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
> Disclaimer:
>
> Privileged & confidential information is contained in this message
> (including all attachments). If you are not an intended recipient of this
> message, please destroy this message immediately and kindly notify
> the sender by reply e-mail. Any unauthorised use or dissemination of this
> message in any manner whatsoever, in whole or in part, is strictly
> prohibited. This e-mail, including all attachments hereto, (i) is for
> discussion purposes only and shall not be deemed or construed to be a
> professional opinion unless expressly stated otherwise, and (ii) is not
> intended, written or sent to be used, and cannot and shall not be used, for
> any unlawful purpose. This communication, including any attachments, may
> not be free of viruses, interceptions or interference, and may not be
> compatible with your systems. You should carry out your own virus checks
> before opening any attachment to this e-mail. The sender of this e-mail and
> *Fynarfin Tech Private Limited* shall not be liable for any damage that
> you may sustain as a result of viruses, incompleteness of this message, a
> delay in receipt of this message or computer problems experienced.
>
Re: Cleaning up the JIRA
Posted by Bruce <br...@gmail.com>.
+1
On Mon, Oct 10, 2022, 8:27 PM James Dailey <ja...@gmail.com> wrote:
> +1 (binding)
>
> We have three binding votes (PMC members) and support from active
> community members. Thank you.
> We have left this open for community input for over two weeks.
> So, to re-enforce our process: this is closed and we proceed to
> implementation of this set of policies and actions.
>
> I shall move this to a wiki page with the clarifications that Avik
> offered.
>
>
>
>
>
>
>
> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io> wrote:
>
>> Hi James, Devs,
>>
>> +1
>>
>> There should be some bulk interfaces or JIRA APIs to drive via pipelines
>> / actions to make it simpler to execute as many other communities do.
>>
>>>
>>> 1. *At each release cycle*, a further list of tickets will be sorted
>>> based on which versions are affected. Versions older than THREE ago will be
>>> considered "non-active".
>>>
>>> To clarify for other readers, the bold part is applicable to minor/major
>> release cycles and not for patch / hotfix releases.
>>
>> With best regards,
>> Avik.
>>
>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <lu...@gmail.com>
>> wrote:
>>
>>> +1
>>>
>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>> cheetah@monkeysintown.com> a écrit :
>>>
>>>> +1
>>>>
>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org> wrote:
>>>>>
>>>>>> +1 for the suggested approach.
>>>>>>
>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Devs -
>>>>>>>
>>>>>>> We currently have a lot of open and stale tickets, with the average
>>>>>>> days open being over 1000 days (over the past two years on any
>>>>>>> given day
>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>> See details I shared on wiki
>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>> including recording. If there is no objection we will begin this
>>>>>>> clean up in the next week or so.
>>>>>>>
>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>>>>> generated and published to the list. The message will be to please review.
>>>>>>>
>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>> person self-assigning it to themselves.
>>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>>> of "Auto Closed"
>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>> further review and may be re-opened, with cause.
>>>>>>> 3. *At each release cycle*, a further list of tickets will be
>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>> will be considered "non-active".
>>>>>>> 1. NB: This is a formalization of a practice we have, which
>>>>>>> is to deprecate older versions and encourage our users to upgrade to the
>>>>>>> most recent stable release. As we are on version 1.8 now, any issue
>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>> version 1.5 becomes "unsupported".
>>>>>>> 2. This led to a further discussion of release strategy -
>>>>>>> which I will start as a different thread. The main point being, if a
>>>>>>> release is no longer a supported release, then those tickets are to be
>>>>>>> archived.
>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require the
>>>>>>> tickets to include "Version affected" and "Component" to be filled
>>>>>>> out. This allows the sorting above and provides for the ability
>>>>>>> to trace the origin of the issue. We also seek to have better ticket
>>>>>>> reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>> 5. We will hold a regular - monthly - issue triage meeting to
>>>>>>> coordinate on tickets.
>>>>>>> 6. We noted that many of the issues on the list and some of
>>>>>>> the Jira tickets are related to configuration and setup and suggest better
>>>>>>> knowledge base management. We are interested in people taking an active
>>>>>>> role in that.
>>>>>>> 7. *Release Cycles: *We noted that we have gotten a number of
>>>>>>> major improvements such that version 1.8 is very different from 1.5 (less
>>>>>>> than two years ago). A new topic is thus to move to a Major release cycle
>>>>>>> Version 2.0, and to consider a Long-Term-Support version of the Fineract1.x
>>>>>>> . I can kick that off on a new thread as well.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>> Disclaimer:
>>
>> Privileged & confidential information is contained in this message
>> (including all attachments). If you are not an intended recipient of this
>> message, please destroy this message immediately and kindly notify
>> the sender by reply e-mail. Any unauthorised use or dissemination of this
>> message in any manner whatsoever, in whole or in part, is strictly
>> prohibited. This e-mail, including all attachments hereto, (i) is for
>> discussion purposes only and shall not be deemed or construed to be a
>> professional opinion unless expressly stated otherwise, and (ii) is not
>> intended, written or sent to be used, and cannot and shall not be used, for
>> any unlawful purpose. This communication, including any attachments, may
>> not be free of viruses, interceptions or interference, and may not be
>> compatible with your systems. You should carry out your own virus checks
>> before opening any attachment to this e-mail. The sender of this e-mail and
>> *Fynarfin Tech Private Limited* shall not be liable for any damage that
>> you may sustain as a result of viruses, incompleteness of this message, a
>> delay in receipt of this message or computer problems experienced.
>>
>
Re: Cleaning up the JIRA
Posted by Aleksandar Vidakovic <al...@apache.org>.
@James Dailey <ja...@gmail.com> sounds good
On Fri, Oct 21, 2022 at 7:43 PM James Dailey <ja...@gmail.com> wrote:
> Robert - good idea. Let's proceed with PLEASE REVIEW.
>
> I think I have set up the JIRA filter properly:
> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
> status = Open ORDER BY createdDate DESC
>
> This finds 342 tickets.
> They do NOT need a full review.
> See this: https://issues.apache.org/jira/issues/?filter=12352370
> <https://issues.apache.org/jira/issues/?filter=12352370>
>
> Again our community agreement is:
>
> 1. *Archiving*: A list of tickets older than 26 months will be
> generated and published to the list. The message will be to *please
> review. * ** *DONE ***
> 1. IF any reviewer finds that the ticket should NOT be archived,
> then that person should indicate by putting a comment on the ticket
> indicating their interest in working on the ticket further (validating
> issue, specifying more, testing, fixing), ideally with the person
> self-assigning it to themselves.
> 2. Otherwise within a set period of time (five days), all those
> tickets will be "Closed" with a tag added "Cleanup22", and a status of
> "Auto Closed"
> 2. Those closed tickets will be archived, and available for further
> review and may be re-opened, with cause.
>
>
> Let's give ourselves just five days to do a cursory review, but starting
> on October 24th (72 hrs from now). IF we need more time, then for sure we
> can do that, but we said five days because this isn't about reviewing the
> tickets in detail.
>
> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
> different from your understanding.
>
> @Robert Jakech <ro...@fiter.io>
> To not collide, let's use the filter above and modify as follows:
>
> Given DESCENDING order:
>
> Robert open tickets within ticket number range of 1259 to 850 (75 open
> tickets)
> a third volunteer can pick up 849 to 525 (another 75
> tickets) *VOLUNTEER HERE*
> a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets)
> * VOLUNTEER HERE*
>
> James open tickets within ticket number range of 374 to 1 (142 open
> tickets)
>
> As we get into this, we may want to highlight certain tickets as a "USEFUL
> IDEA" for a roadmap discussion. Please use label "Roadmap2022" (tag) . I
> will then add that list to a confluence page.
>
> it is unlikely that we can validate any of the BUG tickets as being valid
> without the original person being involved and more context. Therefore,
> they are completely stale and should be closed (as discussed).
>
> At this time, *do not close the tickets*. We will use a Bulk action to
> close them and give them the same tag/label: Cleanup22
>
> This is just the first effort to try to prioritize.
>
> Thanks,
> @jdailey
>
>
> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io> wrote:
>
>> Thanks James,
>> So we don't create redundancies or duplications. Can we find a way to
>> coordinate this?
>> For example, Segregate the work among the ones who have raised their
>> hands. Something like:
>> Robert handles tickets with numbers from xxxy to xxzz and were created at
>> least 26 months.
>> Please let me know if that makes sense and suggest the range I can take
>> on.
>> [image: Logo] <https://www.fiter.io>
>> *Robert Jakech* *| CTO*
>> *e:* robert@fiter.io
>> *w:* fiter.io <http://www.fiter.io>
>> *m:* +61458166091
>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>
>>
>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Robert
>>>
>>> First step is to get a filter in Jira that shows all tickets that were
>>> created over 26 months ago & remain open today. That filter should be
>>> shared here.
>>>
>>> Step two, go through any of those and indicate it is an active issue
>>> that “should” be fixed. Ie if it doesn’t have any activity on it in
>>> recent months then it is stale. This step can be done by anyone but if you
>>> think a tix needs work then you’ll need to validate it.
>>>
>>> Step three - jira mass-action close all remaining in filter as
>>> described.
>>>
>>>
>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io> wrote:
>>>
>>>> Hi James,
>>>> Has this process started yet?
>>>> I am happy to help, including going forward ensuring that all the
>>>> tickets created have the compliance needed (description, version numbers
>>>> etc). Please let me know.
>>>> Cheers
>>>> [image: Logo] <https://www.fiter.io>
>>>> *Robert Jakech* *| CTO*
>>>> *e:* robert@fiter.io
>>>> *w:* fiter.io <http://www.fiter.io>
>>>> *m:* +61458166091
>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>
>>>>
>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> +1 (binding)
>>>>>
>>>>> We have three binding votes (PMC members) and support from active
>>>>> community members. Thank you.
>>>>> We have left this open for community input for over two weeks.
>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>> implementation of this set of policies and actions.
>>>>>
>>>>> I shall move this to a wiki page with the clarifications that Avik
>>>>> offered.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io> wrote:
>>>>>
>>>>>> Hi James, Devs,
>>>>>>
>>>>>> +1
>>>>>>
>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>> do.
>>>>>>
>>>>>>>
>>>>>>> 1. *At each release cycle*, a further list of tickets will be
>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>> will be considered "non-active".
>>>>>>>
>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>
>>>>>> With best regards,
>>>>>> Avik.
>>>>>>
>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>
>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Devs -
>>>>>>>>>>>
>>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>>> average days open being over 1000 days (over the past two years
>>>>>>>>>>> on any given day
>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>
>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will
>>>>>>>>>>> be generated and published to the list. The message will be to please
>>>>>>>>>>> review.
>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>>>>>>> of "Auto Closed"
>>>>>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>>>>>> further review and may be re-opened, with cause.
>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets will
>>>>>>>>>>> be sorted based on which versions are affected. Versions older than THREE
>>>>>>>>>>> ago will be considered "non-active".
>>>>>>>>>>> 1. NB: This is a formalization of a practice we have,
>>>>>>>>>>> which is to deprecate older versions and encourage our users to upgrade to
>>>>>>>>>>> the most recent stable release. As we are on version 1.8 now, any issue
>>>>>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>>>>>> version 1.5 becomes "unsupported".
>>>>>>>>>>> 2. This led to a further discussion of release strategy -
>>>>>>>>>>> which I will start as a different thread. The main point being, if a
>>>>>>>>>>> release is no longer a supported release, then those tickets are to be
>>>>>>>>>>> archived.
>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require the
>>>>>>>>>>> tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage meeting
>>>>>>>>>>> to coordinate on tickets.
>>>>>>>>>>> 6. We noted that many of the issues on the list and some of
>>>>>>>>>>> the Jira tickets are related to configuration and setup and suggest better
>>>>>>>>>>> knowledge base management. We are interested in people taking an active
>>>>>>>>>>> role in that.
>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a number
>>>>>>>>>>> of major improvements such that version 1.8 is very different from 1.5
>>>>>>>>>>> (less than two years ago). A new topic is thus to move to a Major release
>>>>>>>>>>> cycle Version 2.0, and to consider a Long-Term-Support version of the
>>>>>>>>>>> Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> Disclaimer:
>>>>>>
>>>>>> Privileged & confidential information is contained in this message
>>>>>> (including all attachments). If you are not an intended recipient of this
>>>>>> message, please destroy this message immediately and kindly notify
>>>>>> the sender by reply e-mail. Any unauthorised use or dissemination of
>>>>>> this message in any manner whatsoever, in whole or in part, is strictly
>>>>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>>>>> discussion purposes only and shall not be deemed or construed to be a
>>>>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>>>>> intended, written or sent to be used, and cannot and shall not be used, for
>>>>>> any unlawful purpose. This communication, including any attachments, may
>>>>>> not be free of viruses, interceptions or interference, and may not be
>>>>>> compatible with your systems. You should carry out your own virus checks
>>>>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any damage
>>>>>> that you may sustain as a result of viruses, incompleteness of this
>>>>>> message, a delay in receipt of this message or computer problems
>>>>>> experienced.
>>>>>>
>>>>> --
>>> Sent from Gmail Mobile
>>>
>>
Re: Cleaning up the JIRA
Posted by James Dailey <ja...@gmail.com>.
The tickets that we are selecting as possibly useful for Roadmap discussion
are now at bottom of this page ==>
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=231117062
ROADMAP 2022 is the label
I'm nearly done with my set.
On Sun, Oct 30, 2022 at 7:13 AM Bharath Gowda <bg...@mifos.org> wrote:
> Hi James,
>
> This is to let you that 4th group tickets review is also completed and
> have added the label ''Roadmap2022" for the relevant tickets.
>
>
>
> 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, Oct 29, 2022 at 7:30 PM James Dailey <ja...@gmail.com>
> wrote:
>
>> No one else has signed up
>>
>> Keep going!
>>
>> On Sat, Oct 29, 2022 at 6:36 AM Bharath Gowda <bg...@mifos.org> wrote:
>>
>>> Hi James,
>>>
>>> I have completed the reviews for the below tickets' group and have added
>>> the label ''Roadmap2022" for the relevant tickets.
>>> a third volunteer can pick up 849 to 525 (another 75 tickets) *VOLUNTEER
>>> HERE*
>>>
>>> I can review the 4th group as well if it is still available to review
>>> a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets) * VOLUNTEER
>>> HERE*
>>>
>>> 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, Oct 29, 2022 at 12:43 PM Bharath Gowda <bg...@mifos.org> wrote:
>>>
>>>> Noted, Thanks for the confirmation James, Will notify here once I am
>>>> done.
>>>>
>>>> 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, Oct 29, 2022 at 12:41 PM James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> Thanks Bharat
>>>>>
>>>>> Your assigned that group.
>>>>>
>>>>> Just add the ROADMAP 2022 to specific tix as desired.
>>>>>
>>>>> I or Aleks will label the rest Cleanup 2022 and close as per agreed
>>>>> upon process. Do NOT add that label.
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Oct 28, 2022 at 11:58 PM Bharath Gowda <bg...@mifos.org>
>>>>> wrote:
>>>>>
>>>>>> James,
>>>>>>
>>>>>> I can take these tickets for clean up if it still not picked up by
>>>>>> any other volunteer over this weekend.
>>>>>>
>>>>>> a third volunteer can pick up 849 to 525 (another 75 tickets) *VOLUNTEER
>>>>>> HERE*
>>>>>>
>>>>>> Just to confirm if my understanding is correct
>>>>>>
>>>>>> We'll have to review and add the label 'ROADMAP 2022' for
>>>>>> useful Ideas and label 'Cleanup 2022' for stale and invalid tickets
>>>>>>
>>>>>>
>>>>>> 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, Oct 29, 2022 at 11:20 AM Awasum Yannick <aw...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Just because a ticket is old does not mean it's not valid.
>>>>>>>
>>>>>>> What will should do is check old tickets and verify if they are
>>>>>>> still bugs and issues or new features.
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Oct 29, 2022, 05:40 Robert Jakech <ro...@fiter.io> wrote:
>>>>>>>
>>>>>>>> Scheduled to go over mine this weekend too.
>>>>>>>>
>>>>>>>> On Sat, 29 Oct 2022 at 2:26 pm, James Dailey <
>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> I’m still trying to look at my allotment of tix. Let’s give
>>>>>>>>> ourselves another 3 days.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, Oct 21, 2022 at 10:43 AM James Dailey <
>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>>>>>>>>>
>>>>>>>>>> I think I have set up the JIRA filter properly:
>>>>>>>>>> project = FINERACT AND createdDate <= -100w AND updated <=-100w
>>>>>>>>>> AND status = Open ORDER BY createdDate DESC
>>>>>>>>>>
>>>>>>>>>> This finds 342 tickets.
>>>>>>>>>> They do NOT need a full review.
>>>>>>>>>> See this:
>>>>>>>>>> https://issues.apache.org/jira/issues/?filter=12352370
>>>>>>>>>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>>>>>>>>>
>>>>>>>>>> Again our community agreement is:
>>>>>>>>>>
>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will
>>>>>>>>>> be generated and published to the list. The message will be to *please
>>>>>>>>>> review. * ** *DONE ***
>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>>>>>> of "Auto Closed"
>>>>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>>>>> further review and may be re-opened, with cause.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Let's give ourselves just five days to do a cursory review, but
>>>>>>>>>> starting on October 24th (72 hrs from now). IF we need more time, then for
>>>>>>>>>> sure we can do that, but we said five days because this isn't about
>>>>>>>>>> reviewing the tickets in detail.
>>>>>>>>>>
>>>>>>>>>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this
>>>>>>>>>> is different from your understanding.
>>>>>>>>>>
>>>>>>>>>> @Robert Jakech <ro...@fiter.io>
>>>>>>>>>> To not collide, let's use the filter above and modify as follows:
>>>>>>>>>>
>>>>>>>>>> Given DESCENDING order:
>>>>>>>>>>
>>>>>>>>>> Robert open tickets within ticket number range of 1259 to 850
>>>>>>>>>> (75 open tickets)
>>>>>>>>>> a third volunteer can pick up 849 to 525 (another
>>>>>>>>>> 75 tickets) *VOLUNTEER HERE*
>>>>>>>>>> a fourth volunteer can pick up 524 to 374 ( ~ 50
>>>>>>>>>> tickets) * VOLUNTEER HERE*
>>>>>>>>>>
>>>>>>>>>> James open tickets within ticket number range of 374 to 1
>>>>>>>>>> (142 open tickets)
>>>>>>>>>>
>>>>>>>>>> As we get into this, we may want to highlight certain tickets as
>>>>>>>>>> a "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>>>>>>>>>> (tag) . I will then add that list to a confluence page.
>>>>>>>>>>
>>>>>>>>>> it is unlikely that we can validate any of the BUG tickets as
>>>>>>>>>> being valid without the original person being involved and more context.
>>>>>>>>>> Therefore, they are completely stale and should be closed (as discussed).
>>>>>>>>>>
>>>>>>>>>> At this time, *do not close the tickets*. We will use a Bulk
>>>>>>>>>> action to close them and give them the same tag/label: Cleanup22
>>>>>>>>>>
>>>>>>>>>> This is just the first effort to try to prioritize.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> @jdailey
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Thanks James,
>>>>>>>>>>> So we don't create redundancies or duplications. Can we find a
>>>>>>>>>>> way to coordinate this?
>>>>>>>>>>> For example, Segregate the work among the ones who have raised
>>>>>>>>>>> their hands. Something like:
>>>>>>>>>>> Robert handles tickets with numbers from xxxy to xxzz and were
>>>>>>>>>>> created at least 26 months.
>>>>>>>>>>> Please let me know if that makes sense and suggest the range I
>>>>>>>>>>> can take on.
>>>>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>>>>> *e:* robert@fiter.io
>>>>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>>>>> *m:* +61458166091
>>>>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>>>>> youtube icon]
>>>>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <
>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Robert
>>>>>>>>>>>>
>>>>>>>>>>>> First step is to get a filter in Jira that shows all tickets
>>>>>>>>>>>> that were created over 26 months ago & remain open today. That filter
>>>>>>>>>>>> should be shared here.
>>>>>>>>>>>>
>>>>>>>>>>>> Step two, go through any of those and indicate it is an active
>>>>>>>>>>>> issue that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>>>>>>>>>> recent months then it is stale. This step can be done by anyone but if you
>>>>>>>>>>>> think a tix needs work then you’ll need to validate it.
>>>>>>>>>>>>
>>>>>>>>>>>> Step three - jira mass-action close all remaining in filter as
>>>>>>>>>>>> described.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi James,
>>>>>>>>>>>>> Has this process started yet?
>>>>>>>>>>>>> I am happy to help, including going forward ensuring that all
>>>>>>>>>>>>> the tickets created have the compliance needed (description, version
>>>>>>>>>>>>> numbers etc). Please let me know.
>>>>>>>>>>>>> Cheers
>>>>>>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>>>>>>> *e:* robert@fiter.io
>>>>>>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>>>>>>> *m:* +61458166091
>>>>>>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>>>>>>> youtube icon]
>>>>>>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <
>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> +1 (binding)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We have three binding votes (PMC members) and support from
>>>>>>>>>>>>>> active community members. Thank you.
>>>>>>>>>>>>>> We have left this open for community input for over two
>>>>>>>>>>>>>> weeks.
>>>>>>>>>>>>>> So, to re-enforce our process: this is closed and we proceed
>>>>>>>>>>>>>> to implementation of this set of policies and actions.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I shall move this to a wiki page with the clarifications that
>>>>>>>>>>>>>> Avik offered.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <
>>>>>>>>>>>>>> avik@fynarfin.io> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi James, Devs,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> There should be some bulk interfaces or JIRA APIs to drive
>>>>>>>>>>>>>>> via pipelines / actions to make it simpler to execute as many other
>>>>>>>>>>>>>>> communities do.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 1. *At each release cycle*, a further list of tickets
>>>>>>>>>>>>>>>> will be sorted based on which versions are affected. Versions older than
>>>>>>>>>>>>>>>> THREE ago will be considered "non-active".
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> To clarify for other readers, the bold part is applicable
>>>>>>>>>>>>>>> to minor/major release cycles and not for patch / hotfix releases.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> With best regards,
>>>>>>>>>>>>>>> Avik.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>>>>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>>>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <
>>>>>>>>>>>>>>>>> brucetushabe@gmail.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <
>>>>>>>>>>>>>>>>>> bgowda@mifos.org> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Devs -
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> We currently have a lot of open and stale tickets, with
>>>>>>>>>>>>>>>>>>>> the average days open being over 1000 days (over the
>>>>>>>>>>>>>>>>>>>> past two years on any given day
>>>>>>>>>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26
>>>>>>>>>>>>>>>>>>>> months will be generated and published to the list. The message will be to
>>>>>>>>>>>>>>>>>>>> please review.
>>>>>>>>>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should
>>>>>>>>>>>>>>>>>>>> NOT be archived, then that person should indicate by putting a comment on
>>>>>>>>>>>>>>>>>>>> the ticket indicating their interest in working on the ticket further
>>>>>>>>>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>>>>>>>>>> 2. Otherwise within a set period of time (five
>>>>>>>>>>>>>>>>>>>> days), all those tickets will be "Closed" with a tag added "Cleanup22", and
>>>>>>>>>>>>>>>>>>>> a status of "Auto Closed"
>>>>>>>>>>>>>>>>>>>> 2. Those closed tickets will be archived, and
>>>>>>>>>>>>>>>>>>>> available for further review and may be re-opened, with cause.
>>>>>>>>>>>>>>>>>>>> 3. *At each release cycle*, a further list of
>>>>>>>>>>>>>>>>>>>> tickets will be sorted based on which versions are affected. Versions older
>>>>>>>>>>>>>>>>>>>> than THREE ago will be considered "non-active".
>>>>>>>>>>>>>>>>>>>> 1. NB: This is a formalization of a practice we
>>>>>>>>>>>>>>>>>>>> have, which is to deprecate older versions and encourage our users to
>>>>>>>>>>>>>>>>>>>> upgrade to the most recent stable release. As we are on version 1.8 now,
>>>>>>>>>>>>>>>>>>>> any issue affecting 1.4 or older would be "unsupported". As soon as we
>>>>>>>>>>>>>>>>>>>> release 1.9, version 1.5 becomes "unsupported".
>>>>>>>>>>>>>>>>>>>> 2. This led to a further discussion of release
>>>>>>>>>>>>>>>>>>>> strategy - which I will start as a different thread. The main point being,
>>>>>>>>>>>>>>>>>>>> if a release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>>>>>>>>>> archived.
>>>>>>>>>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will
>>>>>>>>>>>>>>>>>>>> require the tickets to include "Version affected" and "Component" to be
>>>>>>>>>>>>>>>>>>>> filled out. This allows the sorting above and
>>>>>>>>>>>>>>>>>>>> provides for the ability to trace the origin of the issue. We also seek to
>>>>>>>>>>>>>>>>>>>> have better ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage
>>>>>>>>>>>>>>>>>>>> meeting to coordinate on tickets.
>>>>>>>>>>>>>>>>>>>> 6. We noted that many of the issues on the list and
>>>>>>>>>>>>>>>>>>>> some of the Jira tickets are related to configuration and setup and suggest
>>>>>>>>>>>>>>>>>>>> better knowledge base management. We are interested in people taking an
>>>>>>>>>>>>>>>>>>>> active role in that.
>>>>>>>>>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten
>>>>>>>>>>>>>>>>>>>> a number of major improvements such that version 1.8 is very different from
>>>>>>>>>>>>>>>>>>>> 1.5 (less than two years ago). A new topic is thus to move to a Major
>>>>>>>>>>>>>>>>>>>> release cycle Version 2.0, and to consider a Long-Term-Support version of
>>>>>>>>>>>>>>>>>>>> the Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Disclaimer:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Privileged & confidential information is contained in this
>>>>>>>>>>>>>>> message (including all attachments). If you are not an intended recipient
>>>>>>>>>>>>>>> of this message, please destroy this message immediately and kindly notify
>>>>>>>>>>>>>>> the sender by reply e-mail. Any unauthorised use or
>>>>>>>>>>>>>>> dissemination of this message in any manner whatsoever, in whole or in
>>>>>>>>>>>>>>> part, is strictly prohibited. This e-mail, including all attachments
>>>>>>>>>>>>>>> hereto, (i) is for discussion purposes only and shall not be deemed or
>>>>>>>>>>>>>>> construed to be a professional opinion unless expressly stated otherwise,
>>>>>>>>>>>>>>> and (ii) is not intended, written or sent to be used, and cannot and shall
>>>>>>>>>>>>>>> not be used, for any unlawful purpose. This communication, including any
>>>>>>>>>>>>>>> attachments, may not be free of viruses, interceptions or interference, and
>>>>>>>>>>>>>>> may not be compatible with your systems. You should carry out your own
>>>>>>>>>>>>>>> virus checks before opening any attachment to this e-mail. The sender of
>>>>>>>>>>>>>>> this e-mail and
>>>>>>>>>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any
>>>>>>>>>>>>>>> damage that you may sustain as a result of viruses, incompleteness of this
>>>>>>>>>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>>>>>>>>>> experienced.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>
>>>>>>>> --
>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>> *e:* robert@fiter.io
>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>> *m:* +61458166091
>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>> youtube icon]
>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>
>>>>>>> --
>>>>> Sent from Gmail Mobile
>>>>>
>>>> --
>> Sent from Gmail Mobile
>>
>
Re: Cleaning up the JIRA
Posted by Bharath Gowda <bg...@mifos.org>.
Hi James,
This is to let you that 4th group tickets review is also completed and have
added the label ''Roadmap2022" for the relevant tickets.
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, Oct 29, 2022 at 7:30 PM James Dailey <ja...@gmail.com> wrote:
> No one else has signed up
>
> Keep going!
>
> On Sat, Oct 29, 2022 at 6:36 AM Bharath Gowda <bg...@mifos.org> wrote:
>
>> Hi James,
>>
>> I have completed the reviews for the below tickets' group and have added
>> the label ''Roadmap2022" for the relevant tickets.
>> a third volunteer can pick up 849 to 525 (another 75 tickets) *VOLUNTEER
>> HERE*
>>
>> I can review the 4th group as well if it is still available to review
>> a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets) * VOLUNTEER
>> HERE*
>>
>> 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, Oct 29, 2022 at 12:43 PM Bharath Gowda <bg...@mifos.org> wrote:
>>
>>> Noted, Thanks for the confirmation James, Will notify here once I am
>>> done.
>>>
>>> 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, Oct 29, 2022 at 12:41 PM James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>>> Thanks Bharat
>>>>
>>>> Your assigned that group.
>>>>
>>>> Just add the ROADMAP 2022 to specific tix as desired.
>>>>
>>>> I or Aleks will label the rest Cleanup 2022 and close as per agreed
>>>> upon process. Do NOT add that label.
>>>>
>>>>
>>>>
>>>> On Fri, Oct 28, 2022 at 11:58 PM Bharath Gowda <bg...@mifos.org>
>>>> wrote:
>>>>
>>>>> James,
>>>>>
>>>>> I can take these tickets for clean up if it still not picked up by any
>>>>> other volunteer over this weekend.
>>>>>
>>>>> a third volunteer can pick up 849 to 525 (another 75 tickets) *VOLUNTEER
>>>>> HERE*
>>>>>
>>>>> Just to confirm if my understanding is correct
>>>>>
>>>>> We'll have to review and add the label 'ROADMAP 2022' for useful Ideas
>>>>> and label 'Cleanup 2022' for stale and invalid tickets
>>>>>
>>>>>
>>>>> 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, Oct 29, 2022 at 11:20 AM Awasum Yannick <aw...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Just because a ticket is old does not mean it's not valid.
>>>>>>
>>>>>> What will should do is check old tickets and verify if they are still
>>>>>> bugs and issues or new features.
>>>>>>
>>>>>>
>>>>>> On Sat, Oct 29, 2022, 05:40 Robert Jakech <ro...@fiter.io> wrote:
>>>>>>
>>>>>>> Scheduled to go over mine this weekend too.
>>>>>>>
>>>>>>> On Sat, 29 Oct 2022 at 2:26 pm, James Dailey <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I’m still trying to look at my allotment of tix. Let’s give
>>>>>>>> ourselves another 3 days.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Oct 21, 2022 at 10:43 AM James Dailey <
>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>>>>>>>>
>>>>>>>>> I think I have set up the JIRA filter properly:
>>>>>>>>> project = FINERACT AND createdDate <= -100w AND updated <=-100w
>>>>>>>>> AND status = Open ORDER BY createdDate DESC
>>>>>>>>>
>>>>>>>>> This finds 342 tickets.
>>>>>>>>> They do NOT need a full review.
>>>>>>>>> See this:
>>>>>>>>> https://issues.apache.org/jira/issues/?filter=12352370
>>>>>>>>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>>>>>>>>
>>>>>>>>> Again our community agreement is:
>>>>>>>>>
>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>>>>>>> generated and published to the list. The message will be to *please
>>>>>>>>> review. * ** *DONE ***
>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>>>>> of "Auto Closed"
>>>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>>>> further review and may be re-opened, with cause.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Let's give ourselves just five days to do a cursory review, but
>>>>>>>>> starting on October 24th (72 hrs from now). IF we need more time, then for
>>>>>>>>> sure we can do that, but we said five days because this isn't about
>>>>>>>>> reviewing the tickets in detail.
>>>>>>>>>
>>>>>>>>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this
>>>>>>>>> is different from your understanding.
>>>>>>>>>
>>>>>>>>> @Robert Jakech <ro...@fiter.io>
>>>>>>>>> To not collide, let's use the filter above and modify as follows:
>>>>>>>>>
>>>>>>>>> Given DESCENDING order:
>>>>>>>>>
>>>>>>>>> Robert open tickets within ticket number range of 1259 to 850
>>>>>>>>> (75 open tickets)
>>>>>>>>> a third volunteer can pick up 849 to 525 (another 75
>>>>>>>>> tickets) *VOLUNTEER HERE*
>>>>>>>>> a fourth volunteer can pick up 524 to 374 ( ~ 50
>>>>>>>>> tickets) * VOLUNTEER HERE*
>>>>>>>>>
>>>>>>>>> James open tickets within ticket number range of 374 to 1 (142
>>>>>>>>> open tickets)
>>>>>>>>>
>>>>>>>>> As we get into this, we may want to highlight certain tickets as a
>>>>>>>>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>>>>>>>>> (tag) . I will then add that list to a confluence page.
>>>>>>>>>
>>>>>>>>> it is unlikely that we can validate any of the BUG tickets as
>>>>>>>>> being valid without the original person being involved and more context.
>>>>>>>>> Therefore, they are completely stale and should be closed (as discussed).
>>>>>>>>>
>>>>>>>>> At this time, *do not close the tickets*. We will use a Bulk
>>>>>>>>> action to close them and give them the same tag/label: Cleanup22
>>>>>>>>>
>>>>>>>>> This is just the first effort to try to prioritize.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> @jdailey
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Thanks James,
>>>>>>>>>> So we don't create redundancies or duplications. Can we find a
>>>>>>>>>> way to coordinate this?
>>>>>>>>>> For example, Segregate the work among the ones who have raised
>>>>>>>>>> their hands. Something like:
>>>>>>>>>> Robert handles tickets with numbers from xxxy to xxzz and were
>>>>>>>>>> created at least 26 months.
>>>>>>>>>> Please let me know if that makes sense and suggest the range I
>>>>>>>>>> can take on.
>>>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>>>> *e:* robert@fiter.io
>>>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>>>> *m:* +61458166091
>>>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>>>> youtube icon]
>>>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <
>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Robert
>>>>>>>>>>>
>>>>>>>>>>> First step is to get a filter in Jira that shows all tickets
>>>>>>>>>>> that were created over 26 months ago & remain open today. That filter
>>>>>>>>>>> should be shared here.
>>>>>>>>>>>
>>>>>>>>>>> Step two, go through any of those and indicate it is an active
>>>>>>>>>>> issue that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>>>>>>>>> recent months then it is stale. This step can be done by anyone but if you
>>>>>>>>>>> think a tix needs work then you’ll need to validate it.
>>>>>>>>>>>
>>>>>>>>>>> Step three - jira mass-action close all remaining in filter as
>>>>>>>>>>> described.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi James,
>>>>>>>>>>>> Has this process started yet?
>>>>>>>>>>>> I am happy to help, including going forward ensuring that all
>>>>>>>>>>>> the tickets created have the compliance needed (description, version
>>>>>>>>>>>> numbers etc). Please let me know.
>>>>>>>>>>>> Cheers
>>>>>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>>>>>> *e:* robert@fiter.io
>>>>>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>>>>>> *m:* +61458166091
>>>>>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>>>>>> youtube icon]
>>>>>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <
>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> +1 (binding)
>>>>>>>>>>>>>
>>>>>>>>>>>>> We have three binding votes (PMC members) and support from
>>>>>>>>>>>>> active community members. Thank you.
>>>>>>>>>>>>> We have left this open for community input for over two weeks.
>>>>>>>>>>>>> So, to re-enforce our process: this is closed and we proceed
>>>>>>>>>>>>> to implementation of this set of policies and actions.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I shall move this to a wiki page with the clarifications that
>>>>>>>>>>>>> Avik offered.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi James, Devs,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> There should be some bulk interfaces or JIRA APIs to drive
>>>>>>>>>>>>>> via pipelines / actions to make it simpler to execute as many other
>>>>>>>>>>>>>> communities do.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 1. *At each release cycle*, a further list of tickets
>>>>>>>>>>>>>>> will be sorted based on which versions are affected. Versions older than
>>>>>>>>>>>>>>> THREE ago will be considered "non-active".
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>>>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> With best regards,
>>>>>>>>>>>>>> Avik.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>>>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <
>>>>>>>>>>>>>>>> brucetushabe@gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <
>>>>>>>>>>>>>>>>> bgowda@mifos.org> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Devs -
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> We currently have a lot of open and stale tickets, with
>>>>>>>>>>>>>>>>>>> the average days open being over 1000 days (over the
>>>>>>>>>>>>>>>>>>> past two years on any given day
>>>>>>>>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26
>>>>>>>>>>>>>>>>>>> months will be generated and published to the list. The message will be to
>>>>>>>>>>>>>>>>>>> please review.
>>>>>>>>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should
>>>>>>>>>>>>>>>>>>> NOT be archived, then that person should indicate by putting a comment on
>>>>>>>>>>>>>>>>>>> the ticket indicating their interest in working on the ticket further
>>>>>>>>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>>>>>>>>> 2. Otherwise within a set period of time (five
>>>>>>>>>>>>>>>>>>> days), all those tickets will be "Closed" with a tag added "Cleanup22", and
>>>>>>>>>>>>>>>>>>> a status of "Auto Closed"
>>>>>>>>>>>>>>>>>>> 2. Those closed tickets will be archived, and
>>>>>>>>>>>>>>>>>>> available for further review and may be re-opened, with cause.
>>>>>>>>>>>>>>>>>>> 3. *At each release cycle*, a further list of
>>>>>>>>>>>>>>>>>>> tickets will be sorted based on which versions are affected. Versions older
>>>>>>>>>>>>>>>>>>> than THREE ago will be considered "non-active".
>>>>>>>>>>>>>>>>>>> 1. NB: This is a formalization of a practice we
>>>>>>>>>>>>>>>>>>> have, which is to deprecate older versions and encourage our users to
>>>>>>>>>>>>>>>>>>> upgrade to the most recent stable release. As we are on version 1.8 now,
>>>>>>>>>>>>>>>>>>> any issue affecting 1.4 or older would be "unsupported". As soon as we
>>>>>>>>>>>>>>>>>>> release 1.9, version 1.5 becomes "unsupported".
>>>>>>>>>>>>>>>>>>> 2. This led to a further discussion of release
>>>>>>>>>>>>>>>>>>> strategy - which I will start as a different thread. The main point being,
>>>>>>>>>>>>>>>>>>> if a release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>>>>>>>>> archived.
>>>>>>>>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will
>>>>>>>>>>>>>>>>>>> require the tickets to include "Version affected" and "Component" to be
>>>>>>>>>>>>>>>>>>> filled out. This allows the sorting above and
>>>>>>>>>>>>>>>>>>> provides for the ability to trace the origin of the issue. We also seek to
>>>>>>>>>>>>>>>>>>> have better ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage
>>>>>>>>>>>>>>>>>>> meeting to coordinate on tickets.
>>>>>>>>>>>>>>>>>>> 6. We noted that many of the issues on the list and
>>>>>>>>>>>>>>>>>>> some of the Jira tickets are related to configuration and setup and suggest
>>>>>>>>>>>>>>>>>>> better knowledge base management. We are interested in people taking an
>>>>>>>>>>>>>>>>>>> active role in that.
>>>>>>>>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a
>>>>>>>>>>>>>>>>>>> number of major improvements such that version 1.8 is very different from
>>>>>>>>>>>>>>>>>>> 1.5 (less than two years ago). A new topic is thus to move to a Major
>>>>>>>>>>>>>>>>>>> release cycle Version 2.0, and to consider a Long-Term-Support version of
>>>>>>>>>>>>>>>>>>> the Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Disclaimer:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Privileged & confidential information is contained in this
>>>>>>>>>>>>>> message (including all attachments). If you are not an intended recipient
>>>>>>>>>>>>>> of this message, please destroy this message immediately and kindly notify
>>>>>>>>>>>>>> the sender by reply e-mail. Any unauthorised use or
>>>>>>>>>>>>>> dissemination of this message in any manner whatsoever, in whole or in
>>>>>>>>>>>>>> part, is strictly prohibited. This e-mail, including all attachments
>>>>>>>>>>>>>> hereto, (i) is for discussion purposes only and shall not be deemed or
>>>>>>>>>>>>>> construed to be a professional opinion unless expressly stated otherwise,
>>>>>>>>>>>>>> and (ii) is not intended, written or sent to be used, and cannot and shall
>>>>>>>>>>>>>> not be used, for any unlawful purpose. This communication, including any
>>>>>>>>>>>>>> attachments, may not be free of viruses, interceptions or interference, and
>>>>>>>>>>>>>> may not be compatible with your systems. You should carry out your own
>>>>>>>>>>>>>> virus checks before opening any attachment to this e-mail. The sender of
>>>>>>>>>>>>>> this e-mail and
>>>>>>>>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any
>>>>>>>>>>>>>> damage that you may sustain as a result of viruses, incompleteness of this
>>>>>>>>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>>>>>>>>> experienced.
>>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>> Sent from Gmail Mobile
>>>>>>>>
>>>>>>> --
>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>> *Robert Jakech* *| CTO*
>>>>>>> *e:* robert@fiter.io
>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>> *m:* +61458166091
>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>> youtube icon]
>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>
>>>>>> --
>>>> Sent from Gmail Mobile
>>>>
>>> --
> Sent from Gmail Mobile
>
Re: Cleaning up the JIRA
Posted by James Dailey <ja...@gmail.com>.
No one else has signed up
Keep going!
On Sat, Oct 29, 2022 at 6:36 AM Bharath Gowda <bg...@mifos.org> wrote:
> Hi James,
>
> I have completed the reviews for the below tickets' group and have added
> the label ''Roadmap2022" for the relevant tickets.
> a third volunteer can pick up 849 to 525 (another 75 tickets) *VOLUNTEER
> HERE*
>
> I can review the 4th group as well if it is still available to review
> a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets) * VOLUNTEER
> HERE*
>
> 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, Oct 29, 2022 at 12:43 PM Bharath Gowda <bg...@mifos.org> wrote:
>
>> Noted, Thanks for the confirmation James, Will notify here once I am done.
>>
>> 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, Oct 29, 2022 at 12:41 PM James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Thanks Bharat
>>>
>>> Your assigned that group.
>>>
>>> Just add the ROADMAP 2022 to specific tix as desired.
>>>
>>> I or Aleks will label the rest Cleanup 2022 and close as per agreed upon
>>> process. Do NOT add that label.
>>>
>>>
>>>
>>> On Fri, Oct 28, 2022 at 11:58 PM Bharath Gowda <bg...@mifos.org> wrote:
>>>
>>>> James,
>>>>
>>>> I can take these tickets for clean up if it still not picked up by any
>>>> other volunteer over this weekend.
>>>>
>>>> a third volunteer can pick up 849 to 525 (another 75 tickets) *VOLUNTEER
>>>> HERE*
>>>>
>>>> Just to confirm if my understanding is correct
>>>>
>>>> We'll have to review and add the label 'ROADMAP 2022' for useful Ideas
>>>> and label 'Cleanup 2022' for stale and invalid tickets
>>>>
>>>>
>>>> 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, Oct 29, 2022 at 11:20 AM Awasum Yannick <aw...@apache.org>
>>>> wrote:
>>>>
>>>>> Just because a ticket is old does not mean it's not valid.
>>>>>
>>>>> What will should do is check old tickets and verify if they are still
>>>>> bugs and issues or new features.
>>>>>
>>>>>
>>>>> On Sat, Oct 29, 2022, 05:40 Robert Jakech <ro...@fiter.io> wrote:
>>>>>
>>>>>> Scheduled to go over mine this weekend too.
>>>>>>
>>>>>> On Sat, 29 Oct 2022 at 2:26 pm, James Dailey <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I’m still trying to look at my allotment of tix. Let’s give
>>>>>>> ourselves another 3 days.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Oct 21, 2022 at 10:43 AM James Dailey <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>
>>>>>>>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>>>>>>>
>>>>>>>> I think I have set up the JIRA filter properly:
>>>>>>>> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
>>>>>>>> status = Open ORDER BY createdDate DESC
>>>>>>>>
>>>>>>>> This finds 342 tickets.
>>>>>>>> They do NOT need a full review.
>>>>>>>> See this: https://issues.apache.org/jira/issues/?filter=12352370
>>>>>>>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>>>>>>>
>>>>>>>> Again our community agreement is:
>>>>>>>>
>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>>>>>> generated and published to the list. The message will be to *please
>>>>>>>> review. * ** *DONE ***
>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>> person self-assigning it to themselves.
>>>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>>>> of "Auto Closed"
>>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>>> further review and may be re-opened, with cause.
>>>>>>>>
>>>>>>>>
>>>>>>>> Let's give ourselves just five days to do a cursory review, but
>>>>>>>> starting on October 24th (72 hrs from now). IF we need more time, then for
>>>>>>>> sure we can do that, but we said five days because this isn't about
>>>>>>>> reviewing the tickets in detail.
>>>>>>>>
>>>>>>>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
>>>>>>>> different from your understanding.
>>>>>>>>
>>>>>>>> @Robert Jakech <ro...@fiter.io>
>>>>>>>> To not collide, let's use the filter above and modify as follows:
>>>>>>>>
>>>>>>>> Given DESCENDING order:
>>>>>>>>
>>>>>>>> Robert open tickets within ticket number range of 1259 to 850
>>>>>>>> (75 open tickets)
>>>>>>>> a third volunteer can pick up 849 to 525 (another 75
>>>>>>>> tickets) *VOLUNTEER HERE*
>>>>>>>> a fourth volunteer can pick up 524 to 374 ( ~ 50
>>>>>>>> tickets) * VOLUNTEER HERE*
>>>>>>>>
>>>>>>>> James open tickets within ticket number range of 374 to 1 (142
>>>>>>>> open tickets)
>>>>>>>>
>>>>>>>> As we get into this, we may want to highlight certain tickets as a
>>>>>>>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>>>>>>>> (tag) . I will then add that list to a confluence page.
>>>>>>>>
>>>>>>>> it is unlikely that we can validate any of the BUG tickets as being
>>>>>>>> valid without the original person being involved and more context.
>>>>>>>> Therefore, they are completely stale and should be closed (as discussed).
>>>>>>>>
>>>>>>>> At this time, *do not close the tickets*. We will use a Bulk
>>>>>>>> action to close them and give them the same tag/label: Cleanup22
>>>>>>>>
>>>>>>>> This is just the first effort to try to prioritize.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> @jdailey
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thanks James,
>>>>>>>>> So we don't create redundancies or duplications. Can we find a way
>>>>>>>>> to coordinate this?
>>>>>>>>> For example, Segregate the work among the ones who have raised
>>>>>>>>> their hands. Something like:
>>>>>>>>> Robert handles tickets with numbers from xxxy to xxzz and were
>>>>>>>>> created at least 26 months.
>>>>>>>>> Please let me know if that makes sense and suggest the range I can
>>>>>>>>> take on.
>>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>>> *e:* robert@fiter.io
>>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>>> *m:* +61458166091
>>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>>> youtube icon]
>>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Robert
>>>>>>>>>>
>>>>>>>>>> First step is to get a filter in Jira that shows all tickets that
>>>>>>>>>> were created over 26 months ago & remain open today. That filter should be
>>>>>>>>>> shared here.
>>>>>>>>>>
>>>>>>>>>> Step two, go through any of those and indicate it is an active
>>>>>>>>>> issue that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>>>>>>>> recent months then it is stale. This step can be done by anyone but if you
>>>>>>>>>> think a tix needs work then you’ll need to validate it.
>>>>>>>>>>
>>>>>>>>>> Step three - jira mass-action close all remaining in filter as
>>>>>>>>>> described.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi James,
>>>>>>>>>>> Has this process started yet?
>>>>>>>>>>> I am happy to help, including going forward ensuring that all
>>>>>>>>>>> the tickets created have the compliance needed (description, version
>>>>>>>>>>> numbers etc). Please let me know.
>>>>>>>>>>> Cheers
>>>>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>>>>> *e:* robert@fiter.io
>>>>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>>>>> *m:* +61458166091
>>>>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>>>>> youtube icon]
>>>>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <
>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> +1 (binding)
>>>>>>>>>>>>
>>>>>>>>>>>> We have three binding votes (PMC members) and support from
>>>>>>>>>>>> active community members. Thank you.
>>>>>>>>>>>> We have left this open for community input for over two weeks.
>>>>>>>>>>>> So, to re-enforce our process: this is closed and we proceed
>>>>>>>>>>>> to implementation of this set of policies and actions.
>>>>>>>>>>>>
>>>>>>>>>>>> I shall move this to a wiki page with the clarifications that
>>>>>>>>>>>> Avik offered.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi James, Devs,
>>>>>>>>>>>>>
>>>>>>>>>>>>> +1
>>>>>>>>>>>>>
>>>>>>>>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>>>>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>>>>>>>>> do.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 1. *At each release cycle*, a further list of tickets
>>>>>>>>>>>>>> will be sorted based on which versions are affected. Versions older than
>>>>>>>>>>>>>> THREE ago will be considered "non-active".
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>>>>>>>
>>>>>>>>>>>>> With best regards,
>>>>>>>>>>>>> Avik.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <
>>>>>>>>>>>>>>> brucetushabe@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <
>>>>>>>>>>>>>>>> bgowda@mifos.org> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Devs -
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> We currently have a lot of open and stale tickets, with
>>>>>>>>>>>>>>>>>> the average days open being over 1000 days (over the
>>>>>>>>>>>>>>>>>> past two years on any given day
>>>>>>>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26
>>>>>>>>>>>>>>>>>> months will be generated and published to the list. The message will be to
>>>>>>>>>>>>>>>>>> please review.
>>>>>>>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should
>>>>>>>>>>>>>>>>>> NOT be archived, then that person should indicate by putting a comment on
>>>>>>>>>>>>>>>>>> the ticket indicating their interest in working on the ticket further
>>>>>>>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>>>>>>>> 2. Otherwise within a set period of time (five
>>>>>>>>>>>>>>>>>> days), all those tickets will be "Closed" with a tag added "Cleanup22", and
>>>>>>>>>>>>>>>>>> a status of "Auto Closed"
>>>>>>>>>>>>>>>>>> 2. Those closed tickets will be archived, and
>>>>>>>>>>>>>>>>>> available for further review and may be re-opened, with cause.
>>>>>>>>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets
>>>>>>>>>>>>>>>>>> will be sorted based on which versions are affected. Versions older than
>>>>>>>>>>>>>>>>>> THREE ago will be considered "non-active".
>>>>>>>>>>>>>>>>>> 1. NB: This is a formalization of a practice we
>>>>>>>>>>>>>>>>>> have, which is to deprecate older versions and encourage our users to
>>>>>>>>>>>>>>>>>> upgrade to the most recent stable release. As we are on version 1.8 now,
>>>>>>>>>>>>>>>>>> any issue affecting 1.4 or older would be "unsupported". As soon as we
>>>>>>>>>>>>>>>>>> release 1.9, version 1.5 becomes "unsupported".
>>>>>>>>>>>>>>>>>> 2. This led to a further discussion of release
>>>>>>>>>>>>>>>>>> strategy - which I will start as a different thread. The main point being,
>>>>>>>>>>>>>>>>>> if a release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>>>>>>>> archived.
>>>>>>>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will
>>>>>>>>>>>>>>>>>> require the tickets to include "Version affected" and "Component" to be
>>>>>>>>>>>>>>>>>> filled out. This allows the sorting above and
>>>>>>>>>>>>>>>>>> provides for the ability to trace the origin of the issue. We also seek to
>>>>>>>>>>>>>>>>>> have better ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage
>>>>>>>>>>>>>>>>>> meeting to coordinate on tickets.
>>>>>>>>>>>>>>>>>> 6. We noted that many of the issues on the list and
>>>>>>>>>>>>>>>>>> some of the Jira tickets are related to configuration and setup and suggest
>>>>>>>>>>>>>>>>>> better knowledge base management. We are interested in people taking an
>>>>>>>>>>>>>>>>>> active role in that.
>>>>>>>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a
>>>>>>>>>>>>>>>>>> number of major improvements such that version 1.8 is very different from
>>>>>>>>>>>>>>>>>> 1.5 (less than two years ago). A new topic is thus to move to a Major
>>>>>>>>>>>>>>>>>> release cycle Version 2.0, and to consider a Long-Term-Support version of
>>>>>>>>>>>>>>>>>> the Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>> Disclaimer:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Privileged & confidential information is contained in this
>>>>>>>>>>>>> message (including all attachments). If you are not an intended recipient
>>>>>>>>>>>>> of this message, please destroy this message immediately and kindly notify
>>>>>>>>>>>>> the sender by reply e-mail. Any unauthorised use or
>>>>>>>>>>>>> dissemination of this message in any manner whatsoever, in whole or in
>>>>>>>>>>>>> part, is strictly prohibited. This e-mail, including all attachments
>>>>>>>>>>>>> hereto, (i) is for discussion purposes only and shall not be deemed or
>>>>>>>>>>>>> construed to be a professional opinion unless expressly stated otherwise,
>>>>>>>>>>>>> and (ii) is not intended, written or sent to be used, and cannot and shall
>>>>>>>>>>>>> not be used, for any unlawful purpose. This communication, including any
>>>>>>>>>>>>> attachments, may not be free of viruses, interceptions or interference, and
>>>>>>>>>>>>> may not be compatible with your systems. You should carry out your own
>>>>>>>>>>>>> virus checks before opening any attachment to this e-mail. The sender of
>>>>>>>>>>>>> this e-mail and
>>>>>>>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any
>>>>>>>>>>>>> damage that you may sustain as a result of viruses, incompleteness of this
>>>>>>>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>>>>>>>> experienced.
>>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>>
>>>>>>>>> --
>>>>>>> Sent from Gmail Mobile
>>>>>>>
>>>>>> --
>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>> *Robert Jakech* *| CTO*
>>>>>> *e:* robert@fiter.io
>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>> *m:* +61458166091
>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>
>>>>> --
>>> Sent from Gmail Mobile
>>>
>> --
Sent from Gmail Mobile
Re: Cleaning up the JIRA
Posted by Bharath Gowda <bg...@mifos.org>.
Hi James,
I have completed the reviews for the below tickets' group and have added
the label ''Roadmap2022" for the relevant tickets.
a third volunteer can pick up 849 to 525 (another 75 tickets) *VOLUNTEER
HERE*
I can review the 4th group as well if it is still available to review
a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets) * VOLUNTEER
HERE*
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, Oct 29, 2022 at 12:43 PM Bharath Gowda <bg...@mifos.org> wrote:
> Noted, Thanks for the confirmation James, Will notify here once I am done.
>
> 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, Oct 29, 2022 at 12:41 PM James Dailey <ja...@gmail.com>
> wrote:
>
>> Thanks Bharat
>>
>> Your assigned that group.
>>
>> Just add the ROADMAP 2022 to specific tix as desired.
>>
>> I or Aleks will label the rest Cleanup 2022 and close as per agreed upon
>> process. Do NOT add that label.
>>
>>
>>
>> On Fri, Oct 28, 2022 at 11:58 PM Bharath Gowda <bg...@mifos.org> wrote:
>>
>>> James,
>>>
>>> I can take these tickets for clean up if it still not picked up by any
>>> other volunteer over this weekend.
>>>
>>> a third volunteer can pick up 849 to 525 (another 75 tickets) *VOLUNTEER
>>> HERE*
>>>
>>> Just to confirm if my understanding is correct
>>>
>>> We'll have to review and add the label 'ROADMAP 2022' for useful Ideas
>>> and label 'Cleanup 2022' for stale and invalid tickets
>>>
>>>
>>> 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, Oct 29, 2022 at 11:20 AM Awasum Yannick <aw...@apache.org>
>>> wrote:
>>>
>>>> Just because a ticket is old does not mean it's not valid.
>>>>
>>>> What will should do is check old tickets and verify if they are still
>>>> bugs and issues or new features.
>>>>
>>>>
>>>> On Sat, Oct 29, 2022, 05:40 Robert Jakech <ro...@fiter.io> wrote:
>>>>
>>>>> Scheduled to go over mine this weekend too.
>>>>>
>>>>> On Sat, 29 Oct 2022 at 2:26 pm, James Dailey <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> I’m still trying to look at my allotment of tix. Let’s give
>>>>>> ourselves another 3 days.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Oct 21, 2022 at 10:43 AM James Dailey <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>>>>>>
>>>>>>> I think I have set up the JIRA filter properly:
>>>>>>> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
>>>>>>> status = Open ORDER BY createdDate DESC
>>>>>>>
>>>>>>> This finds 342 tickets.
>>>>>>> They do NOT need a full review.
>>>>>>> See this: https://issues.apache.org/jira/issues/?filter=12352370
>>>>>>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>>>>>>
>>>>>>> Again our community agreement is:
>>>>>>>
>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>>>>> generated and published to the list. The message will be to *please
>>>>>>> review. * ** *DONE ***
>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>> person self-assigning it to themselves.
>>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>>> of "Auto Closed"
>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>> further review and may be re-opened, with cause.
>>>>>>>
>>>>>>>
>>>>>>> Let's give ourselves just five days to do a cursory review, but
>>>>>>> starting on October 24th (72 hrs from now). IF we need more time, then for
>>>>>>> sure we can do that, but we said five days because this isn't about
>>>>>>> reviewing the tickets in detail.
>>>>>>>
>>>>>>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
>>>>>>> different from your understanding.
>>>>>>>
>>>>>>> @Robert Jakech <ro...@fiter.io>
>>>>>>> To not collide, let's use the filter above and modify as follows:
>>>>>>>
>>>>>>> Given DESCENDING order:
>>>>>>>
>>>>>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>>>>>> open tickets)
>>>>>>> a third volunteer can pick up 849 to 525 (another 75
>>>>>>> tickets) *VOLUNTEER HERE*
>>>>>>> a fourth volunteer can pick up 524 to 374 ( ~ 50
>>>>>>> tickets) * VOLUNTEER HERE*
>>>>>>>
>>>>>>> James open tickets within ticket number range of 374 to 1 (142
>>>>>>> open tickets)
>>>>>>>
>>>>>>> As we get into this, we may want to highlight certain tickets as a
>>>>>>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>>>>>>> (tag) . I will then add that list to a confluence page.
>>>>>>>
>>>>>>> it is unlikely that we can validate any of the BUG tickets as being
>>>>>>> valid without the original person being involved and more context.
>>>>>>> Therefore, they are completely stale and should be closed (as discussed).
>>>>>>>
>>>>>>> At this time, *do not close the tickets*. We will use a Bulk
>>>>>>> action to close them and give them the same tag/label: Cleanup22
>>>>>>>
>>>>>>> This is just the first effort to try to prioritize.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> @jdailey
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thanks James,
>>>>>>>> So we don't create redundancies or duplications. Can we find a way
>>>>>>>> to coordinate this?
>>>>>>>> For example, Segregate the work among the ones who have raised
>>>>>>>> their hands. Something like:
>>>>>>>> Robert handles tickets with numbers from xxxy to xxzz and were
>>>>>>>> created at least 26 months.
>>>>>>>> Please let me know if that makes sense and suggest the range I can
>>>>>>>> take on.
>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>> *e:* robert@fiter.io
>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>> *m:* +61458166091
>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>> youtube icon]
>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Robert
>>>>>>>>>
>>>>>>>>> First step is to get a filter in Jira that shows all tickets that
>>>>>>>>> were created over 26 months ago & remain open today. That filter should be
>>>>>>>>> shared here.
>>>>>>>>>
>>>>>>>>> Step two, go through any of those and indicate it is an active
>>>>>>>>> issue that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>>>>>>> recent months then it is stale. This step can be done by anyone but if you
>>>>>>>>> think a tix needs work then you’ll need to validate it.
>>>>>>>>>
>>>>>>>>> Step three - jira mass-action close all remaining in filter as
>>>>>>>>> described.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi James,
>>>>>>>>>> Has this process started yet?
>>>>>>>>>> I am happy to help, including going forward ensuring that all the
>>>>>>>>>> tickets created have the compliance needed (description, version numbers
>>>>>>>>>> etc). Please let me know.
>>>>>>>>>> Cheers
>>>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>>>> *e:* robert@fiter.io
>>>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>>>> *m:* +61458166091
>>>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>>>> youtube icon]
>>>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <
>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1 (binding)
>>>>>>>>>>>
>>>>>>>>>>> We have three binding votes (PMC members) and support from
>>>>>>>>>>> active community members. Thank you.
>>>>>>>>>>> We have left this open for community input for over two weeks.
>>>>>>>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>>>>>>>> implementation of this set of policies and actions.
>>>>>>>>>>>
>>>>>>>>>>> I shall move this to a wiki page with the clarifications that
>>>>>>>>>>> Avik offered.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi James, Devs,
>>>>>>>>>>>>
>>>>>>>>>>>> +1
>>>>>>>>>>>>
>>>>>>>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>>>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>>>>>>>> do.
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 1. *At each release cycle*, a further list of tickets will
>>>>>>>>>>>>> be sorted based on which versions are affected. Versions older than THREE
>>>>>>>>>>>>> ago will be considered "non-active".
>>>>>>>>>>>>>
>>>>>>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>>>>>>
>>>>>>>>>>>> With best regards,
>>>>>>>>>>>> Avik.
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> +1
>>>>>>>>>>>>>
>>>>>>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>>>>>>
>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <
>>>>>>>>>>>>>>> bgowda@mifos.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Devs -
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> We currently have a lot of open and stale tickets, with
>>>>>>>>>>>>>>>>> the average days open being over 1000 days (over the past
>>>>>>>>>>>>>>>>> two years on any given day
>>>>>>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months
>>>>>>>>>>>>>>>>> will be generated and published to the list. The message will be to please
>>>>>>>>>>>>>>>>> review.
>>>>>>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT
>>>>>>>>>>>>>>>>> be archived, then that person should indicate by putting a comment on the
>>>>>>>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>>>>>>> 2. Otherwise within a set period of time (five
>>>>>>>>>>>>>>>>> days), all those tickets will be "Closed" with a tag added "Cleanup22", and
>>>>>>>>>>>>>>>>> a status of "Auto Closed"
>>>>>>>>>>>>>>>>> 2. Those closed tickets will be archived, and
>>>>>>>>>>>>>>>>> available for further review and may be re-opened, with cause.
>>>>>>>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets
>>>>>>>>>>>>>>>>> will be sorted based on which versions are affected. Versions older than
>>>>>>>>>>>>>>>>> THREE ago will be considered "non-active".
>>>>>>>>>>>>>>>>> 1. NB: This is a formalization of a practice we
>>>>>>>>>>>>>>>>> have, which is to deprecate older versions and encourage our users to
>>>>>>>>>>>>>>>>> upgrade to the most recent stable release. As we are on version 1.8 now,
>>>>>>>>>>>>>>>>> any issue affecting 1.4 or older would be "unsupported". As soon as we
>>>>>>>>>>>>>>>>> release 1.9, version 1.5 becomes "unsupported".
>>>>>>>>>>>>>>>>> 2. This led to a further discussion of release
>>>>>>>>>>>>>>>>> strategy - which I will start as a different thread. The main point being,
>>>>>>>>>>>>>>>>> if a release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>>>>>>> archived.
>>>>>>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require
>>>>>>>>>>>>>>>>> the tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>>>>>>>> out. This allows the sorting above and provides for
>>>>>>>>>>>>>>>>> the ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage
>>>>>>>>>>>>>>>>> meeting to coordinate on tickets.
>>>>>>>>>>>>>>>>> 6. We noted that many of the issues on the list and
>>>>>>>>>>>>>>>>> some of the Jira tickets are related to configuration and setup and suggest
>>>>>>>>>>>>>>>>> better knowledge base management. We are interested in people taking an
>>>>>>>>>>>>>>>>> active role in that.
>>>>>>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a
>>>>>>>>>>>>>>>>> number of major improvements such that version 1.8 is very different from
>>>>>>>>>>>>>>>>> 1.5 (less than two years ago). A new topic is thus to move to a Major
>>>>>>>>>>>>>>>>> release cycle Version 2.0, and to consider a Long-Term-Support version of
>>>>>>>>>>>>>>>>> the Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>> Disclaimer:
>>>>>>>>>>>>
>>>>>>>>>>>> Privileged & confidential information is contained in this
>>>>>>>>>>>> message (including all attachments). If you are not an intended recipient
>>>>>>>>>>>> of this message, please destroy this message immediately and kindly notify
>>>>>>>>>>>> the sender by reply e-mail. Any unauthorised use or
>>>>>>>>>>>> dissemination of this message in any manner whatsoever, in whole or in
>>>>>>>>>>>> part, is strictly prohibited. This e-mail, including all attachments
>>>>>>>>>>>> hereto, (i) is for discussion purposes only and shall not be deemed or
>>>>>>>>>>>> construed to be a professional opinion unless expressly stated otherwise,
>>>>>>>>>>>> and (ii) is not intended, written or sent to be used, and cannot and shall
>>>>>>>>>>>> not be used, for any unlawful purpose. This communication, including any
>>>>>>>>>>>> attachments, may not be free of viruses, interceptions or interference, and
>>>>>>>>>>>> may not be compatible with your systems. You should carry out your own
>>>>>>>>>>>> virus checks before opening any attachment to this e-mail. The sender of
>>>>>>>>>>>> this e-mail and
>>>>>>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any
>>>>>>>>>>>> damage that you may sustain as a result of viruses, incompleteness of this
>>>>>>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>>>>>>> experienced.
>>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>
>>>>>>>> --
>>>>>> Sent from Gmail Mobile
>>>>>>
>>>>> --
>>>>> [image: Logo] <https://www.fiter.io>
>>>>> *Robert Jakech* *| CTO*
>>>>> *e:* robert@fiter.io
>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>> *m:* +61458166091
>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>
>>>> --
>> Sent from Gmail Mobile
>>
>
Re: Cleaning up the JIRA
Posted by Bharath Gowda <bg...@mifos.org>.
Noted, Thanks for the confirmation James, Will notify here once I am done.
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, Oct 29, 2022 at 12:41 PM James Dailey <ja...@gmail.com>
wrote:
> Thanks Bharat
>
> Your assigned that group.
>
> Just add the ROADMAP 2022 to specific tix as desired.
>
> I or Aleks will label the rest Cleanup 2022 and close as per agreed upon
> process. Do NOT add that label.
>
>
>
> On Fri, Oct 28, 2022 at 11:58 PM Bharath Gowda <bg...@mifos.org> wrote:
>
>> James,
>>
>> I can take these tickets for clean up if it still not picked up by any
>> other volunteer over this weekend.
>>
>> a third volunteer can pick up 849 to 525 (another 75 tickets) *VOLUNTEER
>> HERE*
>>
>> Just to confirm if my understanding is correct
>>
>> We'll have to review and add the label 'ROADMAP 2022' for useful Ideas
>> and label 'Cleanup 2022' for stale and invalid tickets
>>
>>
>> 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, Oct 29, 2022 at 11:20 AM Awasum Yannick <aw...@apache.org>
>> wrote:
>>
>>> Just because a ticket is old does not mean it's not valid.
>>>
>>> What will should do is check old tickets and verify if they are still
>>> bugs and issues or new features.
>>>
>>>
>>> On Sat, Oct 29, 2022, 05:40 Robert Jakech <ro...@fiter.io> wrote:
>>>
>>>> Scheduled to go over mine this weekend too.
>>>>
>>>> On Sat, 29 Oct 2022 at 2:26 pm, James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> I’m still trying to look at my allotment of tix. Let’s give ourselves
>>>>> another 3 days.
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Oct 21, 2022 at 10:43 AM James Dailey <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>>>>>
>>>>>> I think I have set up the JIRA filter properly:
>>>>>> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
>>>>>> status = Open ORDER BY createdDate DESC
>>>>>>
>>>>>> This finds 342 tickets.
>>>>>> They do NOT need a full review.
>>>>>> See this: https://issues.apache.org/jira/issues/?filter=12352370
>>>>>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>>>>>
>>>>>> Again our community agreement is:
>>>>>>
>>>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>>>> generated and published to the list. The message will be to *please
>>>>>> review. * ** *DONE ***
>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>> ticket indicating their interest in working on the ticket further
>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>> person self-assigning it to themselves.
>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>> of "Auto Closed"
>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>> further review and may be re-opened, with cause.
>>>>>>
>>>>>>
>>>>>> Let's give ourselves just five days to do a cursory review, but
>>>>>> starting on October 24th (72 hrs from now). IF we need more time, then for
>>>>>> sure we can do that, but we said five days because this isn't about
>>>>>> reviewing the tickets in detail.
>>>>>>
>>>>>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
>>>>>> different from your understanding.
>>>>>>
>>>>>> @Robert Jakech <ro...@fiter.io>
>>>>>> To not collide, let's use the filter above and modify as follows:
>>>>>>
>>>>>> Given DESCENDING order:
>>>>>>
>>>>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>>>>> open tickets)
>>>>>> a third volunteer can pick up 849 to 525 (another 75
>>>>>> tickets) *VOLUNTEER HERE*
>>>>>> a fourth volunteer can pick up 524 to 374 ( ~ 50
>>>>>> tickets) * VOLUNTEER HERE*
>>>>>>
>>>>>> James open tickets within ticket number range of 374 to 1 (142
>>>>>> open tickets)
>>>>>>
>>>>>> As we get into this, we may want to highlight certain tickets as a
>>>>>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>>>>>> (tag) . I will then add that list to a confluence page.
>>>>>>
>>>>>> it is unlikely that we can validate any of the BUG tickets as being
>>>>>> valid without the original person being involved and more context.
>>>>>> Therefore, they are completely stale and should be closed (as discussed).
>>>>>>
>>>>>> At this time, *do not close the tickets*. We will use a Bulk action
>>>>>> to close them and give them the same tag/label: Cleanup22
>>>>>>
>>>>>> This is just the first effort to try to prioritize.
>>>>>>
>>>>>> Thanks,
>>>>>> @jdailey
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io>
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks James,
>>>>>>> So we don't create redundancies or duplications. Can we find a way
>>>>>>> to coordinate this?
>>>>>>> For example, Segregate the work among the ones who have raised their
>>>>>>> hands. Something like:
>>>>>>> Robert handles tickets with numbers from xxxy to xxzz and were
>>>>>>> created at least 26 months.
>>>>>>> Please let me know if that makes sense and suggest the range I can
>>>>>>> take on.
>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>> *Robert Jakech* *| CTO*
>>>>>>> *e:* robert@fiter.io
>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>> *m:* +61458166091
>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>> youtube icon]
>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Robert
>>>>>>>>
>>>>>>>> First step is to get a filter in Jira that shows all tickets that
>>>>>>>> were created over 26 months ago & remain open today. That filter should be
>>>>>>>> shared here.
>>>>>>>>
>>>>>>>> Step two, go through any of those and indicate it is an active
>>>>>>>> issue that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>>>>>> recent months then it is stale. This step can be done by anyone but if you
>>>>>>>> think a tix needs work then you’ll need to validate it.
>>>>>>>>
>>>>>>>> Step three - jira mass-action close all remaining in filter as
>>>>>>>> described.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi James,
>>>>>>>>> Has this process started yet?
>>>>>>>>> I am happy to help, including going forward ensuring that all the
>>>>>>>>> tickets created have the compliance needed (description, version numbers
>>>>>>>>> etc). Please let me know.
>>>>>>>>> Cheers
>>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>>> *e:* robert@fiter.io
>>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>>> *m:* +61458166091
>>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>>> youtube icon]
>>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1 (binding)
>>>>>>>>>>
>>>>>>>>>> We have three binding votes (PMC members) and support from active
>>>>>>>>>> community members. Thank you.
>>>>>>>>>> We have left this open for community input for over two weeks.
>>>>>>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>>>>>>> implementation of this set of policies and actions.
>>>>>>>>>>
>>>>>>>>>> I shall move this to a wiki page with the clarifications that
>>>>>>>>>> Avik offered.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi James, Devs,
>>>>>>>>>>>
>>>>>>>>>>> +1
>>>>>>>>>>>
>>>>>>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>>>>>>> do.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 1. *At each release cycle*, a further list of tickets will
>>>>>>>>>>>> be sorted based on which versions are affected. Versions older than THREE
>>>>>>>>>>>> ago will be considered "non-active".
>>>>>>>>>>>>
>>>>>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>>>>>
>>>>>>>>>>> With best regards,
>>>>>>>>>>> Avik.
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> +1
>>>>>>>>>>>>
>>>>>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>>>>>
>>>>>>>>>>>>> +1
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Devs -
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>>>>>>>> average days open being over 1000 days (over the past two
>>>>>>>>>>>>>>>> years on any given day
>>>>>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months
>>>>>>>>>>>>>>>> will be generated and published to the list. The message will be to please
>>>>>>>>>>>>>>>> review.
>>>>>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT
>>>>>>>>>>>>>>>> be archived, then that person should indicate by putting a comment on the
>>>>>>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>>>>>> 2. Otherwise within a set period of time (five
>>>>>>>>>>>>>>>> days), all those tickets will be "Closed" with a tag added "Cleanup22", and
>>>>>>>>>>>>>>>> a status of "Auto Closed"
>>>>>>>>>>>>>>>> 2. Those closed tickets will be archived, and available
>>>>>>>>>>>>>>>> for further review and may be re-opened, with cause.
>>>>>>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets
>>>>>>>>>>>>>>>> will be sorted based on which versions are affected. Versions older than
>>>>>>>>>>>>>>>> THREE ago will be considered "non-active".
>>>>>>>>>>>>>>>> 1. NB: This is a formalization of a practice we
>>>>>>>>>>>>>>>> have, which is to deprecate older versions and encourage our users to
>>>>>>>>>>>>>>>> upgrade to the most recent stable release. As we are on version 1.8 now,
>>>>>>>>>>>>>>>> any issue affecting 1.4 or older would be "unsupported". As soon as we
>>>>>>>>>>>>>>>> release 1.9, version 1.5 becomes "unsupported".
>>>>>>>>>>>>>>>> 2. This led to a further discussion of release
>>>>>>>>>>>>>>>> strategy - which I will start as a different thread. The main point being,
>>>>>>>>>>>>>>>> if a release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>>>>>> archived.
>>>>>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require
>>>>>>>>>>>>>>>> the tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>>>>>>> out. This allows the sorting above and provides for
>>>>>>>>>>>>>>>> the ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage
>>>>>>>>>>>>>>>> meeting to coordinate on tickets.
>>>>>>>>>>>>>>>> 6. We noted that many of the issues on the list and
>>>>>>>>>>>>>>>> some of the Jira tickets are related to configuration and setup and suggest
>>>>>>>>>>>>>>>> better knowledge base management. We are interested in people taking an
>>>>>>>>>>>>>>>> active role in that.
>>>>>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a
>>>>>>>>>>>>>>>> number of major improvements such that version 1.8 is very different from
>>>>>>>>>>>>>>>> 1.5 (less than two years ago). A new topic is thus to move to a Major
>>>>>>>>>>>>>>>> release cycle Version 2.0, and to consider a Long-Term-Support version of
>>>>>>>>>>>>>>>> the Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>> Disclaimer:
>>>>>>>>>>>
>>>>>>>>>>> Privileged & confidential information is contained in this
>>>>>>>>>>> message (including all attachments). If you are not an intended recipient
>>>>>>>>>>> of this message, please destroy this message immediately and kindly notify
>>>>>>>>>>> the sender by reply e-mail. Any unauthorised use or
>>>>>>>>>>> dissemination of this message in any manner whatsoever, in whole or in
>>>>>>>>>>> part, is strictly prohibited. This e-mail, including all attachments
>>>>>>>>>>> hereto, (i) is for discussion purposes only and shall not be deemed or
>>>>>>>>>>> construed to be a professional opinion unless expressly stated otherwise,
>>>>>>>>>>> and (ii) is not intended, written or sent to be used, and cannot and shall
>>>>>>>>>>> not be used, for any unlawful purpose. This communication, including any
>>>>>>>>>>> attachments, may not be free of viruses, interceptions or interference, and
>>>>>>>>>>> may not be compatible with your systems. You should carry out your own
>>>>>>>>>>> virus checks before opening any attachment to this e-mail. The sender of
>>>>>>>>>>> this e-mail and
>>>>>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any
>>>>>>>>>>> damage that you may sustain as a result of viruses, incompleteness of this
>>>>>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>>>>>> experienced.
>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>> Sent from Gmail Mobile
>>>>>>>>
>>>>>>> --
>>>>> Sent from Gmail Mobile
>>>>>
>>>> --
>>>> [image: Logo] <https://www.fiter.io>
>>>> *Robert Jakech* *| CTO*
>>>> *e:* robert@fiter.io
>>>> *w:* fiter.io <http://www.fiter.io>
>>>> *m:* +61458166091
>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>
>>> --
> Sent from Gmail Mobile
>
Re: Cleaning up the JIRA
Posted by James Dailey <ja...@gmail.com>.
Thanks Bharat
Your assigned that group.
Just add the ROADMAP 2022 to specific tix as desired.
I or Aleks will label the rest Cleanup 2022 and close as per agreed upon
process. Do NOT add that label.
On Fri, Oct 28, 2022 at 11:58 PM Bharath Gowda <bg...@mifos.org> wrote:
> James,
>
> I can take these tickets for clean up if it still not picked up by any
> other volunteer over this weekend.
>
> a third volunteer can pick up 849 to 525 (another 75 tickets) *VOLUNTEER
> HERE*
>
> Just to confirm if my understanding is correct
>
> We'll have to review and add the label 'ROADMAP 2022' for useful Ideas and
> label 'Cleanup 2022' for stale and invalid tickets
>
>
> 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, Oct 29, 2022 at 11:20 AM Awasum Yannick <aw...@apache.org> wrote:
>
>> Just because a ticket is old does not mean it's not valid.
>>
>> What will should do is check old tickets and verify if they are still
>> bugs and issues or new features.
>>
>>
>> On Sat, Oct 29, 2022, 05:40 Robert Jakech <ro...@fiter.io> wrote:
>>
>>> Scheduled to go over mine this weekend too.
>>>
>>> On Sat, 29 Oct 2022 at 2:26 pm, James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>>> I’m still trying to look at my allotment of tix. Let’s give ourselves
>>>> another 3 days.
>>>>
>>>>
>>>>
>>>> On Fri, Oct 21, 2022 at 10:43 AM James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>>>>
>>>>> I think I have set up the JIRA filter properly:
>>>>> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
>>>>> status = Open ORDER BY createdDate DESC
>>>>>
>>>>> This finds 342 tickets.
>>>>> They do NOT need a full review.
>>>>> See this: https://issues.apache.org/jira/issues/?filter=12352370
>>>>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>>>>
>>>>> Again our community agreement is:
>>>>>
>>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>>> generated and published to the list. The message will be to *please
>>>>> review. * ** *DONE ***
>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>> archived, then that person should indicate by putting a comment on the
>>>>> ticket indicating their interest in working on the ticket further
>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>> person self-assigning it to themselves.
>>>>> 2. Otherwise within a set period of time (five days), all those
>>>>> tickets will be "Closed" with a tag added "Cleanup22", and a status of
>>>>> "Auto Closed"
>>>>> 2. Those closed tickets will be archived, and available for
>>>>> further review and may be re-opened, with cause.
>>>>>
>>>>>
>>>>> Let's give ourselves just five days to do a cursory review, but
>>>>> starting on October 24th (72 hrs from now). IF we need more time, then for
>>>>> sure we can do that, but we said five days because this isn't about
>>>>> reviewing the tickets in detail.
>>>>>
>>>>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
>>>>> different from your understanding.
>>>>>
>>>>> @Robert Jakech <ro...@fiter.io>
>>>>> To not collide, let's use the filter above and modify as follows:
>>>>>
>>>>> Given DESCENDING order:
>>>>>
>>>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>>>> open tickets)
>>>>> a third volunteer can pick up 849 to 525 (another 75
>>>>> tickets) *VOLUNTEER HERE*
>>>>> a fourth volunteer can pick up 524 to 374 ( ~ 50
>>>>> tickets) * VOLUNTEER HERE*
>>>>>
>>>>> James open tickets within ticket number range of 374 to 1 (142
>>>>> open tickets)
>>>>>
>>>>> As we get into this, we may want to highlight certain tickets as a
>>>>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>>>>> (tag) . I will then add that list to a confluence page.
>>>>>
>>>>> it is unlikely that we can validate any of the BUG tickets as being
>>>>> valid without the original person being involved and more context.
>>>>> Therefore, they are completely stale and should be closed (as discussed).
>>>>>
>>>>> At this time, *do not close the tickets*. We will use a Bulk action
>>>>> to close them and give them the same tag/label: Cleanup22
>>>>>
>>>>> This is just the first effort to try to prioritize.
>>>>>
>>>>> Thanks,
>>>>> @jdailey
>>>>>
>>>>>
>>>>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io>
>>>>> wrote:
>>>>>
>>>>>> Thanks James,
>>>>>> So we don't create redundancies or duplications. Can we find a way to
>>>>>> coordinate this?
>>>>>> For example, Segregate the work among the ones who have raised their
>>>>>> hands. Something like:
>>>>>> Robert handles tickets with numbers from xxxy to xxzz and were
>>>>>> created at least 26 months.
>>>>>> Please let me know if that makes sense and suggest the range I can
>>>>>> take on.
>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>> *Robert Jakech* *| CTO*
>>>>>> *e:* robert@fiter.io
>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>> *m:* +61458166091
>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>
>>>>>>
>>>>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Robert
>>>>>>>
>>>>>>> First step is to get a filter in Jira that shows all tickets that
>>>>>>> were created over 26 months ago & remain open today. That filter should be
>>>>>>> shared here.
>>>>>>>
>>>>>>> Step two, go through any of those and indicate it is an active issue
>>>>>>> that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>>>>> recent months then it is stale. This step can be done by anyone but if you
>>>>>>> think a tix needs work then you’ll need to validate it.
>>>>>>>
>>>>>>> Step three - jira mass-action close all remaining in filter as
>>>>>>> described.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi James,
>>>>>>>> Has this process started yet?
>>>>>>>> I am happy to help, including going forward ensuring that all the
>>>>>>>> tickets created have the compliance needed (description, version numbers
>>>>>>>> etc). Please let me know.
>>>>>>>> Cheers
>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>> *e:* robert@fiter.io
>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>> *m:* +61458166091
>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>> youtube icon]
>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1 (binding)
>>>>>>>>>
>>>>>>>>> We have three binding votes (PMC members) and support from active
>>>>>>>>> community members. Thank you.
>>>>>>>>> We have left this open for community input for over two weeks.
>>>>>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>>>>>> implementation of this set of policies and actions.
>>>>>>>>>
>>>>>>>>> I shall move this to a wiki page with the clarifications that Avik
>>>>>>>>> offered.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi James, Devs,
>>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>>>>>> do.
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 1. *At each release cycle*, a further list of tickets will
>>>>>>>>>>> be sorted based on which versions are affected. Versions older than THREE
>>>>>>>>>>> ago will be considered "non-active".
>>>>>>>>>>>
>>>>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>>>>
>>>>>>>>>> With best regards,
>>>>>>>>>> Avik.
>>>>>>>>>>
>>>>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1
>>>>>>>>>>>
>>>>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>>>>
>>>>>>>>>>>> +1
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> +1
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Devs -
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>>>>>>> average days open being over 1000 days (over the past two
>>>>>>>>>>>>>>> years on any given day
>>>>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months
>>>>>>>>>>>>>>> will be generated and published to the list. The message will be to please
>>>>>>>>>>>>>>> review.
>>>>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT
>>>>>>>>>>>>>>> be archived, then that person should indicate by putting a comment on the
>>>>>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>>>>> 2. Otherwise within a set period of time (five days),
>>>>>>>>>>>>>>> all those tickets will be "Closed" with a tag added "Cleanup22", and a
>>>>>>>>>>>>>>> status of "Auto Closed"
>>>>>>>>>>>>>>> 2. Those closed tickets will be archived, and available
>>>>>>>>>>>>>>> for further review and may be re-opened, with cause.
>>>>>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets
>>>>>>>>>>>>>>> will be sorted based on which versions are affected. Versions older than
>>>>>>>>>>>>>>> THREE ago will be considered "non-active".
>>>>>>>>>>>>>>> 1. NB: This is a formalization of a practice we
>>>>>>>>>>>>>>> have, which is to deprecate older versions and encourage our users to
>>>>>>>>>>>>>>> upgrade to the most recent stable release. As we are on version 1.8 now,
>>>>>>>>>>>>>>> any issue affecting 1.4 or older would be "unsupported". As soon as we
>>>>>>>>>>>>>>> release 1.9, version 1.5 becomes "unsupported".
>>>>>>>>>>>>>>> 2. This led to a further discussion of release
>>>>>>>>>>>>>>> strategy - which I will start as a different thread. The main point being,
>>>>>>>>>>>>>>> if a release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>>>>> archived.
>>>>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require
>>>>>>>>>>>>>>> the tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage
>>>>>>>>>>>>>>> meeting to coordinate on tickets.
>>>>>>>>>>>>>>> 6. We noted that many of the issues on the list and some
>>>>>>>>>>>>>>> of the Jira tickets are related to configuration and setup and suggest
>>>>>>>>>>>>>>> better knowledge base management. We are interested in people taking an
>>>>>>>>>>>>>>> active role in that.
>>>>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a
>>>>>>>>>>>>>>> number of major improvements such that version 1.8 is very different from
>>>>>>>>>>>>>>> 1.5 (less than two years ago). A new topic is thus to move to a Major
>>>>>>>>>>>>>>> release cycle Version 2.0, and to consider a Long-Term-Support version of
>>>>>>>>>>>>>>> the Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>> Disclaimer:
>>>>>>>>>>
>>>>>>>>>> Privileged & confidential information is contained in this
>>>>>>>>>> message (including all attachments). If you are not an intended recipient
>>>>>>>>>> of this message, please destroy this message immediately and kindly notify
>>>>>>>>>> the sender by reply e-mail. Any unauthorised use or dissemination
>>>>>>>>>> of this message in any manner whatsoever, in whole or in part, is strictly
>>>>>>>>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>>>>>>>>> discussion purposes only and shall not be deemed or construed to be a
>>>>>>>>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>>>>>>>>> intended, written or sent to be used, and cannot and shall not be used, for
>>>>>>>>>> any unlawful purpose. This communication, including any attachments, may
>>>>>>>>>> not be free of viruses, interceptions or interference, and may not be
>>>>>>>>>> compatible with your systems. You should carry out your own virus checks
>>>>>>>>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>>>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any
>>>>>>>>>> damage that you may sustain as a result of viruses, incompleteness of this
>>>>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>>>>> experienced.
>>>>>>>>>>
>>>>>>>>> --
>>>>>>> Sent from Gmail Mobile
>>>>>>>
>>>>>> --
>>>> Sent from Gmail Mobile
>>>>
>>> --
>>> [image: Logo] <https://www.fiter.io>
>>> *Robert Jakech* *| CTO*
>>> *e:* robert@fiter.io
>>> *w:* fiter.io <http://www.fiter.io>
>>> *m:* +61458166091
>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>
>> --
Sent from Gmail Mobile
Re: Cleaning up the JIRA
Posted by Bharath Gowda <bg...@mifos.org>.
James,
I can take these tickets for clean up if it still not picked up by any
other volunteer over this weekend.
a third volunteer can pick up 849 to 525 (another 75 tickets) *VOLUNTEER
HERE*
Just to confirm if my understanding is correct
We'll have to review and add the label 'ROADMAP 2022' for useful Ideas and
label 'Cleanup 2022' for stale and invalid tickets
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, Oct 29, 2022 at 11:20 AM Awasum Yannick <aw...@apache.org> wrote:
> Just because a ticket is old does not mean it's not valid.
>
> What will should do is check old tickets and verify if they are still bugs
> and issues or new features.
>
>
> On Sat, Oct 29, 2022, 05:40 Robert Jakech <ro...@fiter.io> wrote:
>
>> Scheduled to go over mine this weekend too.
>>
>> On Sat, 29 Oct 2022 at 2:26 pm, James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> I’m still trying to look at my allotment of tix. Let’s give ourselves
>>> another 3 days.
>>>
>>>
>>>
>>> On Fri, Oct 21, 2022 at 10:43 AM James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>>>
>>>> I think I have set up the JIRA filter properly:
>>>> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
>>>> status = Open ORDER BY createdDate DESC
>>>>
>>>> This finds 342 tickets.
>>>> They do NOT need a full review.
>>>> See this: https://issues.apache.org/jira/issues/?filter=12352370
>>>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>>>
>>>> Again our community agreement is:
>>>>
>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>> generated and published to the list. The message will be to *please
>>>> review. * ** *DONE ***
>>>> 1. IF any reviewer finds that the ticket should NOT be archived,
>>>> then that person should indicate by putting a comment on the ticket
>>>> indicating their interest in working on the ticket further (validating
>>>> issue, specifying more, testing, fixing), ideally with the person
>>>> self-assigning it to themselves.
>>>> 2. Otherwise within a set period of time (five days), all those
>>>> tickets will be "Closed" with a tag added "Cleanup22", and a status of
>>>> "Auto Closed"
>>>> 2. Those closed tickets will be archived, and available for further
>>>> review and may be re-opened, with cause.
>>>>
>>>>
>>>> Let's give ourselves just five days to do a cursory review, but
>>>> starting on October 24th (72 hrs from now). IF we need more time, then for
>>>> sure we can do that, but we said five days because this isn't about
>>>> reviewing the tickets in detail.
>>>>
>>>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
>>>> different from your understanding.
>>>>
>>>> @Robert Jakech <ro...@fiter.io>
>>>> To not collide, let's use the filter above and modify as follows:
>>>>
>>>> Given DESCENDING order:
>>>>
>>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>>> open tickets)
>>>> a third volunteer can pick up 849 to 525 (another 75
>>>> tickets) *VOLUNTEER HERE*
>>>> a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets)
>>>> * VOLUNTEER HERE*
>>>>
>>>> James open tickets within ticket number range of 374 to 1 (142
>>>> open tickets)
>>>>
>>>> As we get into this, we may want to highlight certain tickets as a
>>>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>>>> (tag) . I will then add that list to a confluence page.
>>>>
>>>> it is unlikely that we can validate any of the BUG tickets as being
>>>> valid without the original person being involved and more context.
>>>> Therefore, they are completely stale and should be closed (as discussed).
>>>>
>>>> At this time, *do not close the tickets*. We will use a Bulk action
>>>> to close them and give them the same tag/label: Cleanup22
>>>>
>>>> This is just the first effort to try to prioritize.
>>>>
>>>> Thanks,
>>>> @jdailey
>>>>
>>>>
>>>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io> wrote:
>>>>
>>>>> Thanks James,
>>>>> So we don't create redundancies or duplications. Can we find a way to
>>>>> coordinate this?
>>>>> For example, Segregate the work among the ones who have raised their
>>>>> hands. Something like:
>>>>> Robert handles tickets with numbers from xxxy to xxzz and were created
>>>>> at least 26 months.
>>>>> Please let me know if that makes sense and suggest the range I can
>>>>> take on.
>>>>> [image: Logo] <https://www.fiter.io>
>>>>> *Robert Jakech* *| CTO*
>>>>> *e:* robert@fiter.io
>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>> *m:* +61458166091
>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>
>>>>>
>>>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Robert
>>>>>>
>>>>>> First step is to get a filter in Jira that shows all tickets that
>>>>>> were created over 26 months ago & remain open today. That filter should be
>>>>>> shared here.
>>>>>>
>>>>>> Step two, go through any of those and indicate it is an active issue
>>>>>> that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>>>> recent months then it is stale. This step can be done by anyone but if you
>>>>>> think a tix needs work then you’ll need to validate it.
>>>>>>
>>>>>> Step three - jira mass-action close all remaining in filter as
>>>>>> described.
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi James,
>>>>>>> Has this process started yet?
>>>>>>> I am happy to help, including going forward ensuring that all the
>>>>>>> tickets created have the compliance needed (description, version numbers
>>>>>>> etc). Please let me know.
>>>>>>> Cheers
>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>> *Robert Jakech* *| CTO*
>>>>>>> *e:* robert@fiter.io
>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>> *m:* +61458166091
>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>> youtube icon]
>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1 (binding)
>>>>>>>>
>>>>>>>> We have three binding votes (PMC members) and support from active
>>>>>>>> community members. Thank you.
>>>>>>>> We have left this open for community input for over two weeks.
>>>>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>>>>> implementation of this set of policies and actions.
>>>>>>>>
>>>>>>>> I shall move this to a wiki page with the clarifications that Avik
>>>>>>>> offered.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi James, Devs,
>>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>>>>> do.
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 1. *At each release cycle*, a further list of tickets will be
>>>>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>>>>> will be considered "non-active".
>>>>>>>>>>
>>>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>>>
>>>>>>>>> With best regards,
>>>>>>>>> Avik.
>>>>>>>>>
>>>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>>>
>>>>>>>>>>> +1
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> +1
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Devs -
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>>>>>> average days open being over 1000 days (over the past two
>>>>>>>>>>>>>> years on any given day
>>>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months
>>>>>>>>>>>>>> will be generated and published to the list. The message will be to please
>>>>>>>>>>>>>> review.
>>>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>>>> 2. Otherwise within a set period of time (five days),
>>>>>>>>>>>>>> all those tickets will be "Closed" with a tag added "Cleanup22", and a
>>>>>>>>>>>>>> status of "Auto Closed"
>>>>>>>>>>>>>> 2. Those closed tickets will be archived, and available
>>>>>>>>>>>>>> for further review and may be re-opened, with cause.
>>>>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets
>>>>>>>>>>>>>> will be sorted based on which versions are affected. Versions older than
>>>>>>>>>>>>>> THREE ago will be considered "non-active".
>>>>>>>>>>>>>> 1. NB: This is a formalization of a practice we have,
>>>>>>>>>>>>>> which is to deprecate older versions and encourage our users to upgrade to
>>>>>>>>>>>>>> the most recent stable release. As we are on version 1.8 now, any issue
>>>>>>>>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>>>>>>>>> version 1.5 becomes "unsupported".
>>>>>>>>>>>>>> 2. This led to a further discussion of release
>>>>>>>>>>>>>> strategy - which I will start as a different thread. The main point being,
>>>>>>>>>>>>>> if a release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>>>> archived.
>>>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require
>>>>>>>>>>>>>> the tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage
>>>>>>>>>>>>>> meeting to coordinate on tickets.
>>>>>>>>>>>>>> 6. We noted that many of the issues on the list and some
>>>>>>>>>>>>>> of the Jira tickets are related to configuration and setup and suggest
>>>>>>>>>>>>>> better knowledge base management. We are interested in people taking an
>>>>>>>>>>>>>> active role in that.
>>>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a
>>>>>>>>>>>>>> number of major improvements such that version 1.8 is very different from
>>>>>>>>>>>>>> 1.5 (less than two years ago). A new topic is thus to move to a Major
>>>>>>>>>>>>>> release cycle Version 2.0, and to consider a Long-Term-Support version of
>>>>>>>>>>>>>> the Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>> Disclaimer:
>>>>>>>>>
>>>>>>>>> Privileged & confidential information is contained in this message
>>>>>>>>> (including all attachments). If you are not an intended recipient of this
>>>>>>>>> message, please destroy this message immediately and kindly notify
>>>>>>>>> the sender by reply e-mail. Any unauthorised use or dissemination
>>>>>>>>> of this message in any manner whatsoever, in whole or in part, is strictly
>>>>>>>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>>>>>>>> discussion purposes only and shall not be deemed or construed to be a
>>>>>>>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>>>>>>>> intended, written or sent to be used, and cannot and shall not be used, for
>>>>>>>>> any unlawful purpose. This communication, including any attachments, may
>>>>>>>>> not be free of viruses, interceptions or interference, and may not be
>>>>>>>>> compatible with your systems. You should carry out your own virus checks
>>>>>>>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any
>>>>>>>>> damage that you may sustain as a result of viruses, incompleteness of this
>>>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>>>> experienced.
>>>>>>>>>
>>>>>>>> --
>>>>>> Sent from Gmail Mobile
>>>>>>
>>>>> --
>>> Sent from Gmail Mobile
>>>
>> --
>> [image: Logo] <https://www.fiter.io>
>> *Robert Jakech* *| CTO*
>> *e:* robert@fiter.io
>> *w:* fiter.io <http://www.fiter.io>
>> *m:* +61458166091
>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>
>
Re: Cleaning up the JIRA
Posted by Awasum Yannick <aw...@apache.org>.
Just because a ticket is old does not mean it's not valid.
What will should do is check old tickets and verify if they are still bugs
and issues or new features.
On Sat, Oct 29, 2022, 05:40 Robert Jakech <ro...@fiter.io> wrote:
> Scheduled to go over mine this weekend too.
>
> On Sat, 29 Oct 2022 at 2:26 pm, James Dailey <ja...@gmail.com>
> wrote:
>
>> I’m still trying to look at my allotment of tix. Let’s give ourselves
>> another 3 days.
>>
>>
>>
>> On Fri, Oct 21, 2022 at 10:43 AM James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>>
>>> I think I have set up the JIRA filter properly:
>>> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
>>> status = Open ORDER BY createdDate DESC
>>>
>>> This finds 342 tickets.
>>> They do NOT need a full review.
>>> See this: https://issues.apache.org/jira/issues/?filter=12352370
>>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>>
>>> Again our community agreement is:
>>>
>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>> generated and published to the list. The message will be to *please
>>> review. * ** *DONE ***
>>> 1. IF any reviewer finds that the ticket should NOT be archived,
>>> then that person should indicate by putting a comment on the ticket
>>> indicating their interest in working on the ticket further (validating
>>> issue, specifying more, testing, fixing), ideally with the person
>>> self-assigning it to themselves.
>>> 2. Otherwise within a set period of time (five days), all those
>>> tickets will be "Closed" with a tag added "Cleanup22", and a status of
>>> "Auto Closed"
>>> 2. Those closed tickets will be archived, and available for further
>>> review and may be re-opened, with cause.
>>>
>>>
>>> Let's give ourselves just five days to do a cursory review, but starting
>>> on October 24th (72 hrs from now). IF we need more time, then for sure we
>>> can do that, but we said five days because this isn't about reviewing the
>>> tickets in detail.
>>>
>>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
>>> different from your understanding.
>>>
>>> @Robert Jakech <ro...@fiter.io>
>>> To not collide, let's use the filter above and modify as follows:
>>>
>>> Given DESCENDING order:
>>>
>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>> open tickets)
>>> a third volunteer can pick up 849 to 525 (another 75
>>> tickets) *VOLUNTEER HERE*
>>> a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets)
>>> * VOLUNTEER HERE*
>>>
>>> James open tickets within ticket number range of 374 to 1 (142 open
>>> tickets)
>>>
>>> As we get into this, we may want to highlight certain tickets as a
>>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>>> (tag) . I will then add that list to a confluence page.
>>>
>>> it is unlikely that we can validate any of the BUG tickets as being
>>> valid without the original person being involved and more context.
>>> Therefore, they are completely stale and should be closed (as discussed).
>>>
>>> At this time, *do not close the tickets*. We will use a Bulk action to
>>> close them and give them the same tag/label: Cleanup22
>>>
>>> This is just the first effort to try to prioritize.
>>>
>>> Thanks,
>>> @jdailey
>>>
>>>
>>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io> wrote:
>>>
>>>> Thanks James,
>>>> So we don't create redundancies or duplications. Can we find a way to
>>>> coordinate this?
>>>> For example, Segregate the work among the ones who have raised their
>>>> hands. Something like:
>>>> Robert handles tickets with numbers from xxxy to xxzz and were created
>>>> at least 26 months.
>>>> Please let me know if that makes sense and suggest the range I can take
>>>> on.
>>>> [image: Logo] <https://www.fiter.io>
>>>> *Robert Jakech* *| CTO*
>>>> *e:* robert@fiter.io
>>>> *w:* fiter.io <http://www.fiter.io>
>>>> *m:* +61458166091
>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>
>>>>
>>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> Robert
>>>>>
>>>>> First step is to get a filter in Jira that shows all tickets that were
>>>>> created over 26 months ago & remain open today. That filter should be
>>>>> shared here.
>>>>>
>>>>> Step two, go through any of those and indicate it is an active issue
>>>>> that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>>> recent months then it is stale. This step can be done by anyone but if you
>>>>> think a tix needs work then you’ll need to validate it.
>>>>>
>>>>> Step three - jira mass-action close all remaining in filter as
>>>>> described.
>>>>>
>>>>>
>>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io> wrote:
>>>>>
>>>>>> Hi James,
>>>>>> Has this process started yet?
>>>>>> I am happy to help, including going forward ensuring that all the
>>>>>> tickets created have the compliance needed (description, version numbers
>>>>>> etc). Please let me know.
>>>>>> Cheers
>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>> *Robert Jakech* *| CTO*
>>>>>> *e:* robert@fiter.io
>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>> *m:* +61458166091
>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>
>>>>>>
>>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> +1 (binding)
>>>>>>>
>>>>>>> We have three binding votes (PMC members) and support from active
>>>>>>> community members. Thank you.
>>>>>>> We have left this open for community input for over two weeks.
>>>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>>>> implementation of this set of policies and actions.
>>>>>>>
>>>>>>> I shall move this to a wiki page with the clarifications that Avik
>>>>>>> offered.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi James, Devs,
>>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>>>> do.
>>>>>>>>
>>>>>>>>>
>>>>>>>>> 1. *At each release cycle*, a further list of tickets will be
>>>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>>>> will be considered "non-active".
>>>>>>>>>
>>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>>
>>>>>>>> With best regards,
>>>>>>>> Avik.
>>>>>>>>
>>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>>
>>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Devs -
>>>>>>>>>>>>>
>>>>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>>>>> average days open being over 1000 days (over the past two
>>>>>>>>>>>>> years on any given day
>>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months
>>>>>>>>>>>>> will be generated and published to the list. The message will be to please
>>>>>>>>>>>>> review.
>>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>>> 2. Otherwise within a set period of time (five days),
>>>>>>>>>>>>> all those tickets will be "Closed" with a tag added "Cleanup22", and a
>>>>>>>>>>>>> status of "Auto Closed"
>>>>>>>>>>>>> 2. Those closed tickets will be archived, and available
>>>>>>>>>>>>> for further review and may be re-opened, with cause.
>>>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets will
>>>>>>>>>>>>> be sorted based on which versions are affected. Versions older than THREE
>>>>>>>>>>>>> ago will be considered "non-active".
>>>>>>>>>>>>> 1. NB: This is a formalization of a practice we have,
>>>>>>>>>>>>> which is to deprecate older versions and encourage our users to upgrade to
>>>>>>>>>>>>> the most recent stable release. As we are on version 1.8 now, any issue
>>>>>>>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>>>>>>>> version 1.5 becomes "unsupported".
>>>>>>>>>>>>> 2. This led to a further discussion of release strategy
>>>>>>>>>>>>> - which I will start as a different thread. The main point being, if a
>>>>>>>>>>>>> release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>>> archived.
>>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require the
>>>>>>>>>>>>> tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage meeting
>>>>>>>>>>>>> to coordinate on tickets.
>>>>>>>>>>>>> 6. We noted that many of the issues on the list and some
>>>>>>>>>>>>> of the Jira tickets are related to configuration and setup and suggest
>>>>>>>>>>>>> better knowledge base management. We are interested in people taking an
>>>>>>>>>>>>> active role in that.
>>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a
>>>>>>>>>>>>> number of major improvements such that version 1.8 is very different from
>>>>>>>>>>>>> 1.5 (less than two years ago). A new topic is thus to move to a Major
>>>>>>>>>>>>> release cycle Version 2.0, and to consider a Long-Term-Support version of
>>>>>>>>>>>>> the Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>> Disclaimer:
>>>>>>>>
>>>>>>>> Privileged & confidential information is contained in this message
>>>>>>>> (including all attachments). If you are not an intended recipient of this
>>>>>>>> message, please destroy this message immediately and kindly notify
>>>>>>>> the sender by reply e-mail. Any unauthorised use or dissemination
>>>>>>>> of this message in any manner whatsoever, in whole or in part, is strictly
>>>>>>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>>>>>>> discussion purposes only and shall not be deemed or construed to be a
>>>>>>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>>>>>>> intended, written or sent to be used, and cannot and shall not be used, for
>>>>>>>> any unlawful purpose. This communication, including any attachments, may
>>>>>>>> not be free of viruses, interceptions or interference, and may not be
>>>>>>>> compatible with your systems. You should carry out your own virus checks
>>>>>>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any damage
>>>>>>>> that you may sustain as a result of viruses, incompleteness of this
>>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>>> experienced.
>>>>>>>>
>>>>>>> --
>>>>> Sent from Gmail Mobile
>>>>>
>>>> --
>> Sent from Gmail Mobile
>>
> --
> [image: Logo] <https://www.fiter.io>
> *Robert Jakech* *| CTO*
> *e:* robert@fiter.io
> *w:* fiter.io <http://www.fiter.io>
> *m:* +61458166091
> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>
Re: Cleaning up the JIRA
Posted by Robert Jakech <ro...@fiter.io>.
Scheduled to go over mine this weekend too.
On Sat, 29 Oct 2022 at 2:26 pm, James Dailey <ja...@gmail.com> wrote:
> I’m still trying to look at my allotment of tix. Let’s give ourselves
> another 3 days.
>
>
>
> On Fri, Oct 21, 2022 at 10:43 AM James Dailey <ja...@gmail.com>
> wrote:
>
>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>
>> I think I have set up the JIRA filter properly:
>> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
>> status = Open ORDER BY createdDate DESC
>>
>> This finds 342 tickets.
>> They do NOT need a full review.
>> See this: https://issues.apache.org/jira/issues/?filter=12352370
>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>
>> Again our community agreement is:
>>
>> 1. *Archiving*: A list of tickets older than 26 months will be
>> generated and published to the list. The message will be to *please
>> review. * ** *DONE ***
>> 1. IF any reviewer finds that the ticket should NOT be archived,
>> then that person should indicate by putting a comment on the ticket
>> indicating their interest in working on the ticket further (validating
>> issue, specifying more, testing, fixing), ideally with the person
>> self-assigning it to themselves.
>> 2. Otherwise within a set period of time (five days), all those
>> tickets will be "Closed" with a tag added "Cleanup22", and a status of
>> "Auto Closed"
>> 2. Those closed tickets will be archived, and available for further
>> review and may be re-opened, with cause.
>>
>>
>> Let's give ourselves just five days to do a cursory review, but starting
>> on October 24th (72 hrs from now). IF we need more time, then for sure we
>> can do that, but we said five days because this isn't about reviewing the
>> tickets in detail.
>>
>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
>> different from your understanding.
>>
>> @Robert Jakech <ro...@fiter.io>
>> To not collide, let's use the filter above and modify as follows:
>>
>> Given DESCENDING order:
>>
>> Robert open tickets within ticket number range of 1259 to 850 (75 open
>> tickets)
>> a third volunteer can pick up 849 to 525 (another 75
>> tickets) *VOLUNTEER HERE*
>> a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets)
>> * VOLUNTEER HERE*
>>
>> James open tickets within ticket number range of 374 to 1 (142 open
>> tickets)
>>
>> As we get into this, we may want to highlight certain tickets as a
>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>> (tag) . I will then add that list to a confluence page.
>>
>> it is unlikely that we can validate any of the BUG tickets as being valid
>> without the original person being involved and more context. Therefore,
>> they are completely stale and should be closed (as discussed).
>>
>> At this time, *do not close the tickets*. We will use a Bulk action to
>> close them and give them the same tag/label: Cleanup22
>>
>> This is just the first effort to try to prioritize.
>>
>> Thanks,
>> @jdailey
>>
>>
>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io> wrote:
>>
>>> Thanks James,
>>> So we don't create redundancies or duplications. Can we find a way to
>>> coordinate this?
>>> For example, Segregate the work among the ones who have raised their
>>> hands. Something like:
>>> Robert handles tickets with numbers from xxxy to xxzz and were created
>>> at least 26 months.
>>> Please let me know if that makes sense and suggest the range I can take
>>> on.
>>> [image: Logo] <https://www.fiter.io>
>>> *Robert Jakech* *| CTO*
>>> *e:* robert@fiter.io
>>> *w:* fiter.io <http://www.fiter.io>
>>> *m:* +61458166091
>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>
>>>
>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>>> Robert
>>>>
>>>> First step is to get a filter in Jira that shows all tickets that were
>>>> created over 26 months ago & remain open today. That filter should be
>>>> shared here.
>>>>
>>>> Step two, go through any of those and indicate it is an active issue
>>>> that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>> recent months then it is stale. This step can be done by anyone but if you
>>>> think a tix needs work then you’ll need to validate it.
>>>>
>>>> Step three - jira mass-action close all remaining in filter as
>>>> described.
>>>>
>>>>
>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io> wrote:
>>>>
>>>>> Hi James,
>>>>> Has this process started yet?
>>>>> I am happy to help, including going forward ensuring that all the
>>>>> tickets created have the compliance needed (description, version numbers
>>>>> etc). Please let me know.
>>>>> Cheers
>>>>> [image: Logo] <https://www.fiter.io>
>>>>> *Robert Jakech* *| CTO*
>>>>> *e:* robert@fiter.io
>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>> *m:* +61458166091
>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>
>>>>>
>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> +1 (binding)
>>>>>>
>>>>>> We have three binding votes (PMC members) and support from active
>>>>>> community members. Thank you.
>>>>>> We have left this open for community input for over two weeks.
>>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>>> implementation of this set of policies and actions.
>>>>>>
>>>>>> I shall move this to a wiki page with the clarifications that Avik
>>>>>> offered.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi James, Devs,
>>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>>> do.
>>>>>>>
>>>>>>>>
>>>>>>>> 1. *At each release cycle*, a further list of tickets will be
>>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>>> will be considered "non-active".
>>>>>>>>
>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>
>>>>>>> With best regards,
>>>>>>> Avik.
>>>>>>>
>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>
>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Devs -
>>>>>>>>>>>>
>>>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>>>> average days open being over 1000 days (over the past two
>>>>>>>>>>>> years on any given day
>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>
>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will
>>>>>>>>>>>> be generated and published to the list. The message will be to please
>>>>>>>>>>>> review.
>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>> 2. Otherwise within a set period of time (five days),
>>>>>>>>>>>> all those tickets will be "Closed" with a tag added "Cleanup22", and a
>>>>>>>>>>>> status of "Auto Closed"
>>>>>>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>>>>>>> further review and may be re-opened, with cause.
>>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets will
>>>>>>>>>>>> be sorted based on which versions are affected. Versions older than THREE
>>>>>>>>>>>> ago will be considered "non-active".
>>>>>>>>>>>> 1. NB: This is a formalization of a practice we have,
>>>>>>>>>>>> which is to deprecate older versions and encourage our users to upgrade to
>>>>>>>>>>>> the most recent stable release. As we are on version 1.8 now, any issue
>>>>>>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>>>>>>> version 1.5 becomes "unsupported".
>>>>>>>>>>>> 2. This led to a further discussion of release strategy
>>>>>>>>>>>> - which I will start as a different thread. The main point being, if a
>>>>>>>>>>>> release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>> archived.
>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require the
>>>>>>>>>>>> tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage meeting
>>>>>>>>>>>> to coordinate on tickets.
>>>>>>>>>>>> 6. We noted that many of the issues on the list and some of
>>>>>>>>>>>> the Jira tickets are related to configuration and setup and suggest better
>>>>>>>>>>>> knowledge base management. We are interested in people taking an active
>>>>>>>>>>>> role in that.
>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a number
>>>>>>>>>>>> of major improvements such that version 1.8 is very different from 1.5
>>>>>>>>>>>> (less than two years ago). A new topic is thus to move to a Major release
>>>>>>>>>>>> cycle Version 2.0, and to consider a Long-Term-Support version of the
>>>>>>>>>>>> Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>> Disclaimer:
>>>>>>>
>>>>>>> Privileged & confidential information is contained in this message
>>>>>>> (including all attachments). If you are not an intended recipient of this
>>>>>>> message, please destroy this message immediately and kindly notify
>>>>>>> the sender by reply e-mail. Any unauthorised use or dissemination of
>>>>>>> this message in any manner whatsoever, in whole or in part, is strictly
>>>>>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>>>>>> discussion purposes only and shall not be deemed or construed to be a
>>>>>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>>>>>> intended, written or sent to be used, and cannot and shall not be used, for
>>>>>>> any unlawful purpose. This communication, including any attachments, may
>>>>>>> not be free of viruses, interceptions or interference, and may not be
>>>>>>> compatible with your systems. You should carry out your own virus checks
>>>>>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any damage
>>>>>>> that you may sustain as a result of viruses, incompleteness of this
>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>> experienced.
>>>>>>>
>>>>>> --
>>>> Sent from Gmail Mobile
>>>>
>>> --
> Sent from Gmail Mobile
>
--
[image: Logo] <https://www.fiter.io>
*Robert Jakech* *| CTO*
*e:* robert@fiter.io
*w:* fiter.io <http://www.fiter.io>
*m:* +61458166091
[image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
<https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image: linkedin
icon] <https://www.linkedin.com/company/fiter-io>
Re: Cleaning up the JIRA
Posted by James Dailey <ja...@gmail.com>.
I’m still trying to look at my allotment of tix. Let’s give ourselves
another 3 days.
On Fri, Oct 21, 2022 at 10:43 AM James Dailey <ja...@gmail.com>
wrote:
> Robert - good idea. Let's proceed with PLEASE REVIEW.
>
> I think I have set up the JIRA filter properly:
> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
> status = Open ORDER BY createdDate DESC
>
> This finds 342 tickets.
> They do NOT need a full review.
> See this: https://issues.apache.org/jira/issues/?filter=12352370
> <https://issues.apache.org/jira/issues/?filter=12352370>
>
> Again our community agreement is:
>
> 1. *Archiving*: A list of tickets older than 26 months will be
> generated and published to the list. The message will be to *please
> review. * ** *DONE ***
> 1. IF any reviewer finds that the ticket should NOT be archived,
> then that person should indicate by putting a comment on the ticket
> indicating their interest in working on the ticket further (validating
> issue, specifying more, testing, fixing), ideally with the person
> self-assigning it to themselves.
> 2. Otherwise within a set period of time (five days), all those
> tickets will be "Closed" with a tag added "Cleanup22", and a status of
> "Auto Closed"
> 2. Those closed tickets will be archived, and available for further
> review and may be re-opened, with cause.
>
>
> Let's give ourselves just five days to do a cursory review, but starting
> on October 24th (72 hrs from now). IF we need more time, then for sure we
> can do that, but we said five days because this isn't about reviewing the
> tickets in detail.
>
> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
> different from your understanding.
>
> @Robert Jakech <ro...@fiter.io>
> To not collide, let's use the filter above and modify as follows:
>
> Given DESCENDING order:
>
> Robert open tickets within ticket number range of 1259 to 850 (75 open
> tickets)
> a third volunteer can pick up 849 to 525 (another 75
> tickets) *VOLUNTEER HERE*
> a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets)
> * VOLUNTEER HERE*
>
> James open tickets within ticket number range of 374 to 1 (142 open
> tickets)
>
> As we get into this, we may want to highlight certain tickets as a "USEFUL
> IDEA" for a roadmap discussion. Please use label "Roadmap2022" (tag) . I
> will then add that list to a confluence page.
>
> it is unlikely that we can validate any of the BUG tickets as being valid
> without the original person being involved and more context. Therefore,
> they are completely stale and should be closed (as discussed).
>
> At this time, *do not close the tickets*. We will use a Bulk action to
> close them and give them the same tag/label: Cleanup22
>
> This is just the first effort to try to prioritize.
>
> Thanks,
> @jdailey
>
>
> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io> wrote:
>
>> Thanks James,
>> So we don't create redundancies or duplications. Can we find a way to
>> coordinate this?
>> For example, Segregate the work among the ones who have raised their
>> hands. Something like:
>> Robert handles tickets with numbers from xxxy to xxzz and were created at
>> least 26 months.
>> Please let me know if that makes sense and suggest the range I can take
>> on.
>> [image: Logo] <https://www.fiter.io>
>> *Robert Jakech* *| CTO*
>> *e:* robert@fiter.io
>> *w:* fiter.io <http://www.fiter.io>
>> *m:* +61458166091
>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>
>>
>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Robert
>>>
>>> First step is to get a filter in Jira that shows all tickets that were
>>> created over 26 months ago & remain open today. That filter should be
>>> shared here.
>>>
>>> Step two, go through any of those and indicate it is an active issue
>>> that “should” be fixed. Ie if it doesn’t have any activity on it in
>>> recent months then it is stale. This step can be done by anyone but if you
>>> think a tix needs work then you’ll need to validate it.
>>>
>>> Step three - jira mass-action close all remaining in filter as
>>> described.
>>>
>>>
>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io> wrote:
>>>
>>>> Hi James,
>>>> Has this process started yet?
>>>> I am happy to help, including going forward ensuring that all the
>>>> tickets created have the compliance needed (description, version numbers
>>>> etc). Please let me know.
>>>> Cheers
>>>> [image: Logo] <https://www.fiter.io>
>>>> *Robert Jakech* *| CTO*
>>>> *e:* robert@fiter.io
>>>> *w:* fiter.io <http://www.fiter.io>
>>>> *m:* +61458166091
>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>
>>>>
>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> +1 (binding)
>>>>>
>>>>> We have three binding votes (PMC members) and support from active
>>>>> community members. Thank you.
>>>>> We have left this open for community input for over two weeks.
>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>> implementation of this set of policies and actions.
>>>>>
>>>>> I shall move this to a wiki page with the clarifications that Avik
>>>>> offered.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io> wrote:
>>>>>
>>>>>> Hi James, Devs,
>>>>>>
>>>>>> +1
>>>>>>
>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>> do.
>>>>>>
>>>>>>>
>>>>>>> 1. *At each release cycle*, a further list of tickets will be
>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>> will be considered "non-active".
>>>>>>>
>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>
>>>>>> With best regards,
>>>>>> Avik.
>>>>>>
>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>
>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Devs -
>>>>>>>>>>>
>>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>>> average days open being over 1000 days (over the past two years
>>>>>>>>>>> on any given day
>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>
>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will
>>>>>>>>>>> be generated and published to the list. The message will be to please
>>>>>>>>>>> review.
>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>>>>>>> of "Auto Closed"
>>>>>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>>>>>> further review and may be re-opened, with cause.
>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets will
>>>>>>>>>>> be sorted based on which versions are affected. Versions older than THREE
>>>>>>>>>>> ago will be considered "non-active".
>>>>>>>>>>> 1. NB: This is a formalization of a practice we have,
>>>>>>>>>>> which is to deprecate older versions and encourage our users to upgrade to
>>>>>>>>>>> the most recent stable release. As we are on version 1.8 now, any issue
>>>>>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>>>>>> version 1.5 becomes "unsupported".
>>>>>>>>>>> 2. This led to a further discussion of release strategy -
>>>>>>>>>>> which I will start as a different thread. The main point being, if a
>>>>>>>>>>> release is no longer a supported release, then those tickets are to be
>>>>>>>>>>> archived.
>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require the
>>>>>>>>>>> tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage meeting
>>>>>>>>>>> to coordinate on tickets.
>>>>>>>>>>> 6. We noted that many of the issues on the list and some of
>>>>>>>>>>> the Jira tickets are related to configuration and setup and suggest better
>>>>>>>>>>> knowledge base management. We are interested in people taking an active
>>>>>>>>>>> role in that.
>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a number
>>>>>>>>>>> of major improvements such that version 1.8 is very different from 1.5
>>>>>>>>>>> (less than two years ago). A new topic is thus to move to a Major release
>>>>>>>>>>> cycle Version 2.0, and to consider a Long-Term-Support version of the
>>>>>>>>>>> Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> Disclaimer:
>>>>>>
>>>>>> Privileged & confidential information is contained in this message
>>>>>> (including all attachments). If you are not an intended recipient of this
>>>>>> message, please destroy this message immediately and kindly notify
>>>>>> the sender by reply e-mail. Any unauthorised use or dissemination of
>>>>>> this message in any manner whatsoever, in whole or in part, is strictly
>>>>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>>>>> discussion purposes only and shall not be deemed or construed to be a
>>>>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>>>>> intended, written or sent to be used, and cannot and shall not be used, for
>>>>>> any unlawful purpose. This communication, including any attachments, may
>>>>>> not be free of viruses, interceptions or interference, and may not be
>>>>>> compatible with your systems. You should carry out your own virus checks
>>>>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any damage
>>>>>> that you may sustain as a result of viruses, incompleteness of this
>>>>>> message, a delay in receipt of this message or computer problems
>>>>>> experienced.
>>>>>>
>>>>> --
>>> Sent from Gmail Mobile
>>>
>> --
Sent from Gmail Mobile
Re: Cleaning up the JIRA
Posted by Bharath Gowda <bg...@mifos.org>.
Hi James,
+1 from my side.
Plan Sounds good
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 Tue, Nov 8, 2022 at 3:37 AM Aleksandar Vidakovic <al...@apache.org>
wrote:
> +1
>
> On Mon, Nov 7, 2022 at 10:43 PM Robert Jakech <ro...@fiter.io> wrote:
>
>> Thank you James and everyone involved.
>> I agree. 357 tickets is a lot.
>>
>> My suggestion would be we start operating this in sprint. We can start
>> with monthly sprint with showcase on the last day of sprint.
>>
>> I can take on the Sprint Master role for now. Or this can be alternate
>> role where every so sprint(s) someone else can take over.
>>
>> My suggestion is this can sync with releases so maybe priority tickets
>> take precedent.
>>
>> Devs can pick tickets and perhaps provide some indicative estimates for
>> the sprint.
>> Overall we can create some order and structure around how this runs with
>> contributions from members.
>>
>> Cheers
>>
>> On Tue, 8 Nov 2022 at 4:33 am, James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Hi Devs -
>>>
>>> As previously discussed:
>>> * we identified the open tickets that were older than 100 weeks with no
>>> updates in over 100 weeks. ==> STALE Tickets
>>> * just in case, we reviewed the open tickets, thank you Bharat and
>>> Robert.
>>> * we now are closing the remaining stale tickets
>>>
>>> I have applied two bulk actions on 294 tickets.
>>> 1) applied the Label: Cleanup2022
>>> 2) closed / with status "auto-closed"
>>>
>>> You can now find these tickets with this JQL
>>> project = FINERACT AND status = Closed AND labels = Cleanup2022 ORDER
>>> BY createdDate DESC
>>>
>>> That is also saved as this Filter:
>>> https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352409
>>> <https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352409>
>>>
>>> I mean to say that we are NOT deleting such tickets, we are simply
>>> putting them into the state that they are actually in:
>>> No one is working on them, no one has worked on them in over 100weeks.
>>> If you look at those tickets and have a desire to take one of them on,
>>> they are still there and you can re-open.
>>> but, please communicate on the list if you do so.
>>>
>>> There are 41 tickets that we identified that *might* be useful to review
>>> and incorporate into the roadmap.
>>> We probably will need to further trim these down or close (with same
>>> status as above) if we cannot verify that they are still open issues or
>>> interesting for the community.
>>>
>>> I will go back to the ROADMAP thread to discuss how we will trim and
>>> refine tickets. But, this is your project, so do speak up there.
>>>
>>> As we go forward, we will continuously add to the "Closed, auto-closed",
>>> as part of our normal practices during each release cycle.
>>> *We discussed and agreed on this approach. *
>>> This will give us a clearer view of open tickets and prioritization.
>>>
>>> After this action, we now have 357 tickets in "Status = open".
>>> BTW This is still very high, given that we have less than 10 active
>>> developers.
>>>
>>> My target would be less than 100 open tickets. Do you agree?
>>>
>>> I hope everyone is following along. How is this sounding?
>>>
>>> Thanks,
>>>
>>>
>>> On Thu, Nov 3, 2022 at 5:38 PM Robert Jakech <ro...@fiter.io> wrote:
>>>
>>>> Copy that.
>>>> Thanks James.
>>>>
>>>> On Fri, 4 Nov 2022 at 12:17 am, James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> Thank you Robert, Bharat. We've now done a quick review of the
>>>>> tickets.
>>>>> we have picked out 41 possible items to consider in a roadmap
>>>>> discussion
>>>>>
>>>>> Roadmap page:
>>>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=231117062
>>>>> (tickets at the bottom, suggested items for discussion )
>>>>>
>>>>> Out of 342 open / unresolved tickets (which were already filtered as
>>>>> older than 100 weeks)
>>>>> https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352370
>>>>>
>>>>> As previously discussed, our next step is to do a bulk action and
>>>>> close those other 302 tickets with a label.
>>>>> https://lists.apache.org/thread/b91nh3q919pro4wxg4pmqt0brfny9h1b
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Nov 3, 2022 at 6:04 AM Robert Jakech <ro...@fiter.io> wrote:
>>>>>
>>>>>> Hello James & Team.
>>>>>> This is done (apologies for lateness). I appended the label as
>>>>>> discussed to only user stories and not bugs.
>>>>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>>>>> open tickets)
>>>>>> Thanks Ed for the granting Edit access.
>>>>>> Cheers
>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>> *Robert Jakech* *| CTO*
>>>>>> *e:* robert@fiter.io
>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>> *m:* +61458166091
>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>
>>>>>>
>>>>>> On Sat, 22 Oct 2022 at 03:43, James Dailey <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>>>>>>
>>>>>>> I think I have set up the JIRA filter properly:
>>>>>>> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
>>>>>>> status = Open ORDER BY createdDate DESC
>>>>>>>
>>>>>>> This finds 342 tickets.
>>>>>>> They do NOT need a full review.
>>>>>>> See this: https://issues.apache.org/jira/issues/?filter=12352370
>>>>>>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>>>>>>
>>>>>>> Again our community agreement is:
>>>>>>>
>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>>>>> generated and published to the list. The message will be to *please
>>>>>>> review. * ** *DONE ***
>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>> person self-assigning it to themselves.
>>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>>> of "Auto Closed"
>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>> further review and may be re-opened, with cause.
>>>>>>>
>>>>>>>
>>>>>>> Let's give ourselves just five days to do a cursory review, but
>>>>>>> starting on October 24th (72 hrs from now). IF we need more time, then for
>>>>>>> sure we can do that, but we said five days because this isn't about
>>>>>>> reviewing the tickets in detail.
>>>>>>>
>>>>>>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
>>>>>>> different from your understanding.
>>>>>>>
>>>>>>> @Robert Jakech <ro...@fiter.io>
>>>>>>> To not collide, let's use the filter above and modify as follows:
>>>>>>>
>>>>>>> Given DESCENDING order:
>>>>>>>
>>>>>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>>>>>> open tickets)
>>>>>>> a third volunteer can pick up 849 to 525 (another 75
>>>>>>> tickets) *VOLUNTEER HERE*
>>>>>>> a fourth volunteer can pick up 524 to 374 ( ~ 50
>>>>>>> tickets) * VOLUNTEER HERE*
>>>>>>>
>>>>>>> James open tickets within ticket number range of 374 to 1 (142
>>>>>>> open tickets)
>>>>>>>
>>>>>>> As we get into this, we may want to highlight certain tickets as a
>>>>>>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>>>>>>> (tag) . I will then add that list to a confluence page.
>>>>>>>
>>>>>>> it is unlikely that we can validate any of the BUG tickets as being
>>>>>>> valid without the original person being involved and more context.
>>>>>>> Therefore, they are completely stale and should be closed (as discussed).
>>>>>>>
>>>>>>> At this time, *do not close the tickets*. We will use a Bulk
>>>>>>> action to close them and give them the same tag/label: Cleanup22
>>>>>>>
>>>>>>> This is just the first effort to try to prioritize.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> @jdailey
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thanks James,
>>>>>>>> So we don't create redundancies or duplications. Can we find a way
>>>>>>>> to coordinate this?
>>>>>>>> For example, Segregate the work among the ones who have raised
>>>>>>>> their hands. Something like:
>>>>>>>> Robert handles tickets with numbers from xxxy to xxzz and were
>>>>>>>> created at least 26 months.
>>>>>>>> Please let me know if that makes sense and suggest the range I can
>>>>>>>> take on.
>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>> *e:* robert@fiter.io
>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>> *m:* +61458166091
>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>> youtube icon]
>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Robert
>>>>>>>>>
>>>>>>>>> First step is to get a filter in Jira that shows all tickets that
>>>>>>>>> were created over 26 months ago & remain open today. That filter should be
>>>>>>>>> shared here.
>>>>>>>>>
>>>>>>>>> Step two, go through any of those and indicate it is an active
>>>>>>>>> issue that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>>>>>>> recent months then it is stale. This step can be done by anyone but if you
>>>>>>>>> think a tix needs work then you’ll need to validate it.
>>>>>>>>>
>>>>>>>>> Step three - jira mass-action close all remaining in filter as
>>>>>>>>> described.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi James,
>>>>>>>>>> Has this process started yet?
>>>>>>>>>> I am happy to help, including going forward ensuring that all the
>>>>>>>>>> tickets created have the compliance needed (description, version numbers
>>>>>>>>>> etc). Please let me know.
>>>>>>>>>> Cheers
>>>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>>>> *e:* robert@fiter.io
>>>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>>>> *m:* +61458166091
>>>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>>>> youtube icon]
>>>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <
>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1 (binding)
>>>>>>>>>>>
>>>>>>>>>>> We have three binding votes (PMC members) and support from
>>>>>>>>>>> active community members. Thank you.
>>>>>>>>>>> We have left this open for community input for over two weeks.
>>>>>>>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>>>>>>>> implementation of this set of policies and actions.
>>>>>>>>>>>
>>>>>>>>>>> I shall move this to a wiki page with the clarifications that
>>>>>>>>>>> Avik offered.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi James, Devs,
>>>>>>>>>>>>
>>>>>>>>>>>> +1
>>>>>>>>>>>>
>>>>>>>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>>>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>>>>>>>> do.
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 1. *At each release cycle*, a further list of tickets will
>>>>>>>>>>>>> be sorted based on which versions are affected. Versions older than THREE
>>>>>>>>>>>>> ago will be considered "non-active".
>>>>>>>>>>>>>
>>>>>>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>>>>>>
>>>>>>>>>>>> With best regards,
>>>>>>>>>>>> Avik.
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> +1
>>>>>>>>>>>>>
>>>>>>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>>>>>>
>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <
>>>>>>>>>>>>>>> bgowda@mifos.org> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Devs -
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> We currently have a lot of open and stale tickets, with
>>>>>>>>>>>>>>>>> the average days open being over 1000 days (over the past
>>>>>>>>>>>>>>>>> two years on any given day
>>>>>>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months
>>>>>>>>>>>>>>>>> will be generated and published to the list. The message will be to please
>>>>>>>>>>>>>>>>> review.
>>>>>>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT
>>>>>>>>>>>>>>>>> be archived, then that person should indicate by putting a comment on the
>>>>>>>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>>>>>>> 2. Otherwise within a set period of time (five
>>>>>>>>>>>>>>>>> days), all those tickets will be "Closed" with a tag added "Cleanup22", and
>>>>>>>>>>>>>>>>> a status of "Auto Closed"
>>>>>>>>>>>>>>>>> 2. Those closed tickets will be archived, and
>>>>>>>>>>>>>>>>> available for further review and may be re-opened, with cause.
>>>>>>>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets
>>>>>>>>>>>>>>>>> will be sorted based on which versions are affected. Versions older than
>>>>>>>>>>>>>>>>> THREE ago will be considered "non-active".
>>>>>>>>>>>>>>>>> 1. NB: This is a formalization of a practice we
>>>>>>>>>>>>>>>>> have, which is to deprecate older versions and encourage our users to
>>>>>>>>>>>>>>>>> upgrade to the most recent stable release. As we are on version 1.8 now,
>>>>>>>>>>>>>>>>> any issue affecting 1.4 or older would be "unsupported". As soon as we
>>>>>>>>>>>>>>>>> release 1.9, version 1.5 becomes "unsupported".
>>>>>>>>>>>>>>>>> 2. This led to a further discussion of release
>>>>>>>>>>>>>>>>> strategy - which I will start as a different thread. The main point being,
>>>>>>>>>>>>>>>>> if a release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>>>>>>> archived.
>>>>>>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require
>>>>>>>>>>>>>>>>> the tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>>>>>>>> out. This allows the sorting above and provides for
>>>>>>>>>>>>>>>>> the ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage
>>>>>>>>>>>>>>>>> meeting to coordinate on tickets.
>>>>>>>>>>>>>>>>> 6. We noted that many of the issues on the list and
>>>>>>>>>>>>>>>>> some of the Jira tickets are related to configuration and setup and suggest
>>>>>>>>>>>>>>>>> better knowledge base management. We are interested in people taking an
>>>>>>>>>>>>>>>>> active role in that.
>>>>>>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a
>>>>>>>>>>>>>>>>> number of major improvements such that version 1.8 is very different from
>>>>>>>>>>>>>>>>> 1.5 (less than two years ago). A new topic is thus to move to a Major
>>>>>>>>>>>>>>>>> release cycle Version 2.0, and to consider a Long-Term-Support version of
>>>>>>>>>>>>>>>>> the Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>> Disclaimer:
>>>>>>>>>>>>
>>>>>>>>>>>> Privileged & confidential information is contained in this
>>>>>>>>>>>> message (including all attachments). If you are not an intended recipient
>>>>>>>>>>>> of this message, please destroy this message immediately and kindly notify
>>>>>>>>>>>> the sender by reply e-mail. Any unauthorised use or
>>>>>>>>>>>> dissemination of this message in any manner whatsoever, in whole or in
>>>>>>>>>>>> part, is strictly prohibited. This e-mail, including all attachments
>>>>>>>>>>>> hereto, (i) is for discussion purposes only and shall not be deemed or
>>>>>>>>>>>> construed to be a professional opinion unless expressly stated otherwise,
>>>>>>>>>>>> and (ii) is not intended, written or sent to be used, and cannot and shall
>>>>>>>>>>>> not be used, for any unlawful purpose. This communication, including any
>>>>>>>>>>>> attachments, may not be free of viruses, interceptions or interference, and
>>>>>>>>>>>> may not be compatible with your systems. You should carry out your own
>>>>>>>>>>>> virus checks before opening any attachment to this e-mail. The sender of
>>>>>>>>>>>> this e-mail and
>>>>>>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any
>>>>>>>>>>>> damage that you may sustain as a result of viruses, incompleteness of this
>>>>>>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>>>>>>> experienced.
>>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>> Sent from Gmail Mobile
>>>>>>>>>
>>>>>>>> --
>>>> [image: Logo] <https://www.fiter.io>
>>>> *Robert Jakech* *| CTO*
>>>> *e:* robert@fiter.io
>>>> *w:* fiter.io <http://www.fiter.io>
>>>> *m:* +61458166091
>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>
>>> --
>> [image: Logo] <https://www.fiter.io>
>> *Robert Jakech* *| CTO*
>> *e:* robert@fiter.io
>> *w:* fiter.io <http://www.fiter.io>
>> *m:* +61458166091
>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>
>
Re: Cleaning up the JIRA
Posted by Aleksandar Vidakovic <al...@apache.org>.
+1
On Mon, Nov 7, 2022 at 10:43 PM Robert Jakech <ro...@fiter.io> wrote:
> Thank you James and everyone involved.
> I agree. 357 tickets is a lot.
>
> My suggestion would be we start operating this in sprint. We can start
> with monthly sprint with showcase on the last day of sprint.
>
> I can take on the Sprint Master role for now. Or this can be alternate
> role where every so sprint(s) someone else can take over.
>
> My suggestion is this can sync with releases so maybe priority tickets
> take precedent.
>
> Devs can pick tickets and perhaps provide some indicative estimates for
> the sprint.
> Overall we can create some order and structure around how this runs with
> contributions from members.
>
> Cheers
>
> On Tue, 8 Nov 2022 at 4:33 am, James Dailey <ja...@gmail.com>
> wrote:
>
>> Hi Devs -
>>
>> As previously discussed:
>> * we identified the open tickets that were older than 100 weeks with no
>> updates in over 100 weeks. ==> STALE Tickets
>> * just in case, we reviewed the open tickets, thank you Bharat and
>> Robert.
>> * we now are closing the remaining stale tickets
>>
>> I have applied two bulk actions on 294 tickets.
>> 1) applied the Label: Cleanup2022
>> 2) closed / with status "auto-closed"
>>
>> You can now find these tickets with this JQL
>> project = FINERACT AND status = Closed AND labels = Cleanup2022 ORDER
>> BY createdDate DESC
>>
>> That is also saved as this Filter:
>> https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352409
>> <https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352409>
>>
>> I mean to say that we are NOT deleting such tickets, we are simply
>> putting them into the state that they are actually in:
>> No one is working on them, no one has worked on them in over 100weeks.
>> If you look at those tickets and have a desire to take one of them on,
>> they are still there and you can re-open.
>> but, please communicate on the list if you do so.
>>
>> There are 41 tickets that we identified that *might* be useful to review
>> and incorporate into the roadmap.
>> We probably will need to further trim these down or close (with same
>> status as above) if we cannot verify that they are still open issues or
>> interesting for the community.
>>
>> I will go back to the ROADMAP thread to discuss how we will trim and
>> refine tickets. But, this is your project, so do speak up there.
>>
>> As we go forward, we will continuously add to the "Closed, auto-closed",
>> as part of our normal practices during each release cycle.
>> *We discussed and agreed on this approach. *
>> This will give us a clearer view of open tickets and prioritization.
>>
>> After this action, we now have 357 tickets in "Status = open".
>> BTW This is still very high, given that we have less than 10 active
>> developers.
>>
>> My target would be less than 100 open tickets. Do you agree?
>>
>> I hope everyone is following along. How is this sounding?
>>
>> Thanks,
>>
>>
>> On Thu, Nov 3, 2022 at 5:38 PM Robert Jakech <ro...@fiter.io> wrote:
>>
>>> Copy that.
>>> Thanks James.
>>>
>>> On Fri, 4 Nov 2022 at 12:17 am, James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>>> Thank you Robert, Bharat. We've now done a quick review of the
>>>> tickets.
>>>> we have picked out 41 possible items to consider in a roadmap
>>>> discussion
>>>>
>>>> Roadmap page:
>>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=231117062
>>>> (tickets at the bottom, suggested items for discussion )
>>>>
>>>> Out of 342 open / unresolved tickets (which were already filtered as
>>>> older than 100 weeks)
>>>> https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352370
>>>>
>>>> As previously discussed, our next step is to do a bulk action and close
>>>> those other 302 tickets with a label.
>>>> https://lists.apache.org/thread/b91nh3q919pro4wxg4pmqt0brfny9h1b
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Nov 3, 2022 at 6:04 AM Robert Jakech <ro...@fiter.io> wrote:
>>>>
>>>>> Hello James & Team.
>>>>> This is done (apologies for lateness). I appended the label as
>>>>> discussed to only user stories and not bugs.
>>>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>>>> open tickets)
>>>>> Thanks Ed for the granting Edit access.
>>>>> Cheers
>>>>> [image: Logo] <https://www.fiter.io>
>>>>> *Robert Jakech* *| CTO*
>>>>> *e:* robert@fiter.io
>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>> *m:* +61458166091
>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>
>>>>>
>>>>> On Sat, 22 Oct 2022 at 03:43, James Dailey <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>>>>>
>>>>>> I think I have set up the JIRA filter properly:
>>>>>> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
>>>>>> status = Open ORDER BY createdDate DESC
>>>>>>
>>>>>> This finds 342 tickets.
>>>>>> They do NOT need a full review.
>>>>>> See this: https://issues.apache.org/jira/issues/?filter=12352370
>>>>>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>>>>>
>>>>>> Again our community agreement is:
>>>>>>
>>>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>>>> generated and published to the list. The message will be to *please
>>>>>> review. * ** *DONE ***
>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>> ticket indicating their interest in working on the ticket further
>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>> person self-assigning it to themselves.
>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>> of "Auto Closed"
>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>> further review and may be re-opened, with cause.
>>>>>>
>>>>>>
>>>>>> Let's give ourselves just five days to do a cursory review, but
>>>>>> starting on October 24th (72 hrs from now). IF we need more time, then for
>>>>>> sure we can do that, but we said five days because this isn't about
>>>>>> reviewing the tickets in detail.
>>>>>>
>>>>>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
>>>>>> different from your understanding.
>>>>>>
>>>>>> @Robert Jakech <ro...@fiter.io>
>>>>>> To not collide, let's use the filter above and modify as follows:
>>>>>>
>>>>>> Given DESCENDING order:
>>>>>>
>>>>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>>>>> open tickets)
>>>>>> a third volunteer can pick up 849 to 525 (another 75
>>>>>> tickets) *VOLUNTEER HERE*
>>>>>> a fourth volunteer can pick up 524 to 374 ( ~ 50
>>>>>> tickets) * VOLUNTEER HERE*
>>>>>>
>>>>>> James open tickets within ticket number range of 374 to 1 (142
>>>>>> open tickets)
>>>>>>
>>>>>> As we get into this, we may want to highlight certain tickets as a
>>>>>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>>>>>> (tag) . I will then add that list to a confluence page.
>>>>>>
>>>>>> it is unlikely that we can validate any of the BUG tickets as being
>>>>>> valid without the original person being involved and more context.
>>>>>> Therefore, they are completely stale and should be closed (as discussed).
>>>>>>
>>>>>> At this time, *do not close the tickets*. We will use a Bulk action
>>>>>> to close them and give them the same tag/label: Cleanup22
>>>>>>
>>>>>> This is just the first effort to try to prioritize.
>>>>>>
>>>>>> Thanks,
>>>>>> @jdailey
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io>
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks James,
>>>>>>> So we don't create redundancies or duplications. Can we find a way
>>>>>>> to coordinate this?
>>>>>>> For example, Segregate the work among the ones who have raised their
>>>>>>> hands. Something like:
>>>>>>> Robert handles tickets with numbers from xxxy to xxzz and were
>>>>>>> created at least 26 months.
>>>>>>> Please let me know if that makes sense and suggest the range I can
>>>>>>> take on.
>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>> *Robert Jakech* *| CTO*
>>>>>>> *e:* robert@fiter.io
>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>> *m:* +61458166091
>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>> youtube icon]
>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Robert
>>>>>>>>
>>>>>>>> First step is to get a filter in Jira that shows all tickets that
>>>>>>>> were created over 26 months ago & remain open today. That filter should be
>>>>>>>> shared here.
>>>>>>>>
>>>>>>>> Step two, go through any of those and indicate it is an active
>>>>>>>> issue that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>>>>>> recent months then it is stale. This step can be done by anyone but if you
>>>>>>>> think a tix needs work then you’ll need to validate it.
>>>>>>>>
>>>>>>>> Step three - jira mass-action close all remaining in filter as
>>>>>>>> described.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi James,
>>>>>>>>> Has this process started yet?
>>>>>>>>> I am happy to help, including going forward ensuring that all the
>>>>>>>>> tickets created have the compliance needed (description, version numbers
>>>>>>>>> etc). Please let me know.
>>>>>>>>> Cheers
>>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>>> *e:* robert@fiter.io
>>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>>> *m:* +61458166091
>>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>>> youtube icon]
>>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1 (binding)
>>>>>>>>>>
>>>>>>>>>> We have three binding votes (PMC members) and support from active
>>>>>>>>>> community members. Thank you.
>>>>>>>>>> We have left this open for community input for over two weeks.
>>>>>>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>>>>>>> implementation of this set of policies and actions.
>>>>>>>>>>
>>>>>>>>>> I shall move this to a wiki page with the clarifications that
>>>>>>>>>> Avik offered.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi James, Devs,
>>>>>>>>>>>
>>>>>>>>>>> +1
>>>>>>>>>>>
>>>>>>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>>>>>>> do.
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 1. *At each release cycle*, a further list of tickets will
>>>>>>>>>>>> be sorted based on which versions are affected. Versions older than THREE
>>>>>>>>>>>> ago will be considered "non-active".
>>>>>>>>>>>>
>>>>>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>>>>>
>>>>>>>>>>> With best regards,
>>>>>>>>>>> Avik.
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> +1
>>>>>>>>>>>>
>>>>>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>>>>>
>>>>>>>>>>>>> +1
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> +1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Devs -
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>>>>>>>> average days open being over 1000 days (over the past two
>>>>>>>>>>>>>>>> years on any given day
>>>>>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months
>>>>>>>>>>>>>>>> will be generated and published to the list. The message will be to please
>>>>>>>>>>>>>>>> review.
>>>>>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT
>>>>>>>>>>>>>>>> be archived, then that person should indicate by putting a comment on the
>>>>>>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>>>>>> 2. Otherwise within a set period of time (five
>>>>>>>>>>>>>>>> days), all those tickets will be "Closed" with a tag added "Cleanup22", and
>>>>>>>>>>>>>>>> a status of "Auto Closed"
>>>>>>>>>>>>>>>> 2. Those closed tickets will be archived, and available
>>>>>>>>>>>>>>>> for further review and may be re-opened, with cause.
>>>>>>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets
>>>>>>>>>>>>>>>> will be sorted based on which versions are affected. Versions older than
>>>>>>>>>>>>>>>> THREE ago will be considered "non-active".
>>>>>>>>>>>>>>>> 1. NB: This is a formalization of a practice we
>>>>>>>>>>>>>>>> have, which is to deprecate older versions and encourage our users to
>>>>>>>>>>>>>>>> upgrade to the most recent stable release. As we are on version 1.8 now,
>>>>>>>>>>>>>>>> any issue affecting 1.4 or older would be "unsupported". As soon as we
>>>>>>>>>>>>>>>> release 1.9, version 1.5 becomes "unsupported".
>>>>>>>>>>>>>>>> 2. This led to a further discussion of release
>>>>>>>>>>>>>>>> strategy - which I will start as a different thread. The main point being,
>>>>>>>>>>>>>>>> if a release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>>>>>> archived.
>>>>>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require
>>>>>>>>>>>>>>>> the tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>>>>>>> out. This allows the sorting above and provides for
>>>>>>>>>>>>>>>> the ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage
>>>>>>>>>>>>>>>> meeting to coordinate on tickets.
>>>>>>>>>>>>>>>> 6. We noted that many of the issues on the list and
>>>>>>>>>>>>>>>> some of the Jira tickets are related to configuration and setup and suggest
>>>>>>>>>>>>>>>> better knowledge base management. We are interested in people taking an
>>>>>>>>>>>>>>>> active role in that.
>>>>>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a
>>>>>>>>>>>>>>>> number of major improvements such that version 1.8 is very different from
>>>>>>>>>>>>>>>> 1.5 (less than two years ago). A new topic is thus to move to a Major
>>>>>>>>>>>>>>>> release cycle Version 2.0, and to consider a Long-Term-Support version of
>>>>>>>>>>>>>>>> the Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>> Disclaimer:
>>>>>>>>>>>
>>>>>>>>>>> Privileged & confidential information is contained in this
>>>>>>>>>>> message (including all attachments). If you are not an intended recipient
>>>>>>>>>>> of this message, please destroy this message immediately and kindly notify
>>>>>>>>>>> the sender by reply e-mail. Any unauthorised use or
>>>>>>>>>>> dissemination of this message in any manner whatsoever, in whole or in
>>>>>>>>>>> part, is strictly prohibited. This e-mail, including all attachments
>>>>>>>>>>> hereto, (i) is for discussion purposes only and shall not be deemed or
>>>>>>>>>>> construed to be a professional opinion unless expressly stated otherwise,
>>>>>>>>>>> and (ii) is not intended, written or sent to be used, and cannot and shall
>>>>>>>>>>> not be used, for any unlawful purpose. This communication, including any
>>>>>>>>>>> attachments, may not be free of viruses, interceptions or interference, and
>>>>>>>>>>> may not be compatible with your systems. You should carry out your own
>>>>>>>>>>> virus checks before opening any attachment to this e-mail. The sender of
>>>>>>>>>>> this e-mail and
>>>>>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any
>>>>>>>>>>> damage that you may sustain as a result of viruses, incompleteness of this
>>>>>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>>>>>> experienced.
>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>> Sent from Gmail Mobile
>>>>>>>>
>>>>>>> --
>>> [image: Logo] <https://www.fiter.io>
>>> *Robert Jakech* *| CTO*
>>> *e:* robert@fiter.io
>>> *w:* fiter.io <http://www.fiter.io>
>>> *m:* +61458166091
>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>
>> --
> [image: Logo] <https://www.fiter.io>
> *Robert Jakech* *| CTO*
> *e:* robert@fiter.io
> *w:* fiter.io <http://www.fiter.io>
> *m:* +61458166091
> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>
Re: Cleaning up the JIRA
Posted by Robert Jakech <ro...@fiter.io>.
Thank you James and everyone involved.
I agree. 357 tickets is a lot.
My suggestion would be we start operating this in sprint. We can start with
monthly sprint with showcase on the last day of sprint.
I can take on the Sprint Master role for now. Or this can be alternate role
where every so sprint(s) someone else can take over.
My suggestion is this can sync with releases so maybe priority tickets take
precedent.
Devs can pick tickets and perhaps provide some indicative estimates for the
sprint.
Overall we can create some order and structure around how this runs with
contributions from members.
Cheers
On Tue, 8 Nov 2022 at 4:33 am, James Dailey <ja...@gmail.com> wrote:
> Hi Devs -
>
> As previously discussed:
> * we identified the open tickets that were older than 100 weeks with no
> updates in over 100 weeks. ==> STALE Tickets
> * just in case, we reviewed the open tickets, thank you Bharat and Robert.
>
> * we now are closing the remaining stale tickets
>
> I have applied two bulk actions on 294 tickets.
> 1) applied the Label: Cleanup2022
> 2) closed / with status "auto-closed"
>
> You can now find these tickets with this JQL
> project = FINERACT AND status = Closed AND labels = Cleanup2022 ORDER BY
> createdDate DESC
>
> That is also saved as this Filter:
> https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352409
> <https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352409>
>
> I mean to say that we are NOT deleting such tickets, we are simply putting
> them into the state that they are actually in:
> No one is working on them, no one has worked on them in over 100weeks.
> If you look at those tickets and have a desire to take one of them on,
> they are still there and you can re-open.
> but, please communicate on the list if you do so.
>
> There are 41 tickets that we identified that *might* be useful to review
> and incorporate into the roadmap.
> We probably will need to further trim these down or close (with same
> status as above) if we cannot verify that they are still open issues or
> interesting for the community.
>
> I will go back to the ROADMAP thread to discuss how we will trim and
> refine tickets. But, this is your project, so do speak up there.
>
> As we go forward, we will continuously add to the "Closed, auto-closed",
> as part of our normal practices during each release cycle.
> *We discussed and agreed on this approach. *
> This will give us a clearer view of open tickets and prioritization.
>
> After this action, we now have 357 tickets in "Status = open".
> BTW This is still very high, given that we have less than 10 active
> developers.
>
> My target would be less than 100 open tickets. Do you agree?
>
> I hope everyone is following along. How is this sounding?
>
> Thanks,
>
>
> On Thu, Nov 3, 2022 at 5:38 PM Robert Jakech <ro...@fiter.io> wrote:
>
>> Copy that.
>> Thanks James.
>>
>> On Fri, 4 Nov 2022 at 12:17 am, James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Thank you Robert, Bharat. We've now done a quick review of the tickets.
>>> we have picked out 41 possible items to consider in a roadmap
>>> discussion
>>>
>>> Roadmap page:
>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=231117062
>>> (tickets at the bottom, suggested items for discussion )
>>>
>>> Out of 342 open / unresolved tickets (which were already filtered as
>>> older than 100 weeks)
>>> https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352370
>>>
>>> As previously discussed, our next step is to do a bulk action and close
>>> those other 302 tickets with a label.
>>> https://lists.apache.org/thread/b91nh3q919pro4wxg4pmqt0brfny9h1b
>>>
>>>
>>>
>>>
>>> On Thu, Nov 3, 2022 at 6:04 AM Robert Jakech <ro...@fiter.io> wrote:
>>>
>>>> Hello James & Team.
>>>> This is done (apologies for lateness). I appended the label as
>>>> discussed to only user stories and not bugs.
>>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>>> open tickets)
>>>> Thanks Ed for the granting Edit access.
>>>> Cheers
>>>> [image: Logo] <https://www.fiter.io>
>>>> *Robert Jakech* *| CTO*
>>>> *e:* robert@fiter.io
>>>> *w:* fiter.io <http://www.fiter.io>
>>>> *m:* +61458166091
>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>
>>>>
>>>> On Sat, 22 Oct 2022 at 03:43, James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>>>>
>>>>> I think I have set up the JIRA filter properly:
>>>>> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
>>>>> status = Open ORDER BY createdDate DESC
>>>>>
>>>>> This finds 342 tickets.
>>>>> They do NOT need a full review.
>>>>> See this: https://issues.apache.org/jira/issues/?filter=12352370
>>>>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>>>>
>>>>> Again our community agreement is:
>>>>>
>>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>>> generated and published to the list. The message will be to *please
>>>>> review. * ** *DONE ***
>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>> archived, then that person should indicate by putting a comment on the
>>>>> ticket indicating their interest in working on the ticket further
>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>> person self-assigning it to themselves.
>>>>> 2. Otherwise within a set period of time (five days), all those
>>>>> tickets will be "Closed" with a tag added "Cleanup22", and a status of
>>>>> "Auto Closed"
>>>>> 2. Those closed tickets will be archived, and available for
>>>>> further review and may be re-opened, with cause.
>>>>>
>>>>>
>>>>> Let's give ourselves just five days to do a cursory review, but
>>>>> starting on October 24th (72 hrs from now). IF we need more time, then for
>>>>> sure we can do that, but we said five days because this isn't about
>>>>> reviewing the tickets in detail.
>>>>>
>>>>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
>>>>> different from your understanding.
>>>>>
>>>>> @Robert Jakech <ro...@fiter.io>
>>>>> To not collide, let's use the filter above and modify as follows:
>>>>>
>>>>> Given DESCENDING order:
>>>>>
>>>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>>>> open tickets)
>>>>> a third volunteer can pick up 849 to 525 (another 75
>>>>> tickets) *VOLUNTEER HERE*
>>>>> a fourth volunteer can pick up 524 to 374 ( ~ 50
>>>>> tickets) * VOLUNTEER HERE*
>>>>>
>>>>> James open tickets within ticket number range of 374 to 1 (142
>>>>> open tickets)
>>>>>
>>>>> As we get into this, we may want to highlight certain tickets as a
>>>>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>>>>> (tag) . I will then add that list to a confluence page.
>>>>>
>>>>> it is unlikely that we can validate any of the BUG tickets as being
>>>>> valid without the original person being involved and more context.
>>>>> Therefore, they are completely stale and should be closed (as discussed).
>>>>>
>>>>> At this time, *do not close the tickets*. We will use a Bulk action
>>>>> to close them and give them the same tag/label: Cleanup22
>>>>>
>>>>> This is just the first effort to try to prioritize.
>>>>>
>>>>> Thanks,
>>>>> @jdailey
>>>>>
>>>>>
>>>>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io>
>>>>> wrote:
>>>>>
>>>>>> Thanks James,
>>>>>> So we don't create redundancies or duplications. Can we find a way to
>>>>>> coordinate this?
>>>>>> For example, Segregate the work among the ones who have raised their
>>>>>> hands. Something like:
>>>>>> Robert handles tickets with numbers from xxxy to xxzz and were
>>>>>> created at least 26 months.
>>>>>> Please let me know if that makes sense and suggest the range I can
>>>>>> take on.
>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>> *Robert Jakech* *| CTO*
>>>>>> *e:* robert@fiter.io
>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>> *m:* +61458166091
>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>
>>>>>>
>>>>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Robert
>>>>>>>
>>>>>>> First step is to get a filter in Jira that shows all tickets that
>>>>>>> were created over 26 months ago & remain open today. That filter should be
>>>>>>> shared here.
>>>>>>>
>>>>>>> Step two, go through any of those and indicate it is an active issue
>>>>>>> that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>>>>> recent months then it is stale. This step can be done by anyone but if you
>>>>>>> think a tix needs work then you’ll need to validate it.
>>>>>>>
>>>>>>> Step three - jira mass-action close all remaining in filter as
>>>>>>> described.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi James,
>>>>>>>> Has this process started yet?
>>>>>>>> I am happy to help, including going forward ensuring that all the
>>>>>>>> tickets created have the compliance needed (description, version numbers
>>>>>>>> etc). Please let me know.
>>>>>>>> Cheers
>>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>>> *Robert Jakech* *| CTO*
>>>>>>>> *e:* robert@fiter.io
>>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>>> *m:* +61458166091
>>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>>> youtube icon]
>>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1 (binding)
>>>>>>>>>
>>>>>>>>> We have three binding votes (PMC members) and support from active
>>>>>>>>> community members. Thank you.
>>>>>>>>> We have left this open for community input for over two weeks.
>>>>>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>>>>>> implementation of this set of policies and actions.
>>>>>>>>>
>>>>>>>>> I shall move this to a wiki page with the clarifications that Avik
>>>>>>>>> offered.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi James, Devs,
>>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>>>>>> do.
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 1. *At each release cycle*, a further list of tickets will
>>>>>>>>>>> be sorted based on which versions are affected. Versions older than THREE
>>>>>>>>>>> ago will be considered "non-active".
>>>>>>>>>>>
>>>>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>>>>
>>>>>>>>>> With best regards,
>>>>>>>>>> Avik.
>>>>>>>>>>
>>>>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1
>>>>>>>>>>>
>>>>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>>>>
>>>>>>>>>>>> +1
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> +1
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Devs -
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>>>>>>> average days open being over 1000 days (over the past two
>>>>>>>>>>>>>>> years on any given day
>>>>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months
>>>>>>>>>>>>>>> will be generated and published to the list. The message will be to please
>>>>>>>>>>>>>>> review.
>>>>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT
>>>>>>>>>>>>>>> be archived, then that person should indicate by putting a comment on the
>>>>>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>>>>> 2. Otherwise within a set period of time (five days),
>>>>>>>>>>>>>>> all those tickets will be "Closed" with a tag added "Cleanup22", and a
>>>>>>>>>>>>>>> status of "Auto Closed"
>>>>>>>>>>>>>>> 2. Those closed tickets will be archived, and available
>>>>>>>>>>>>>>> for further review and may be re-opened, with cause.
>>>>>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets
>>>>>>>>>>>>>>> will be sorted based on which versions are affected. Versions older than
>>>>>>>>>>>>>>> THREE ago will be considered "non-active".
>>>>>>>>>>>>>>> 1. NB: This is a formalization of a practice we
>>>>>>>>>>>>>>> have, which is to deprecate older versions and encourage our users to
>>>>>>>>>>>>>>> upgrade to the most recent stable release. As we are on version 1.8 now,
>>>>>>>>>>>>>>> any issue affecting 1.4 or older would be "unsupported". As soon as we
>>>>>>>>>>>>>>> release 1.9, version 1.5 becomes "unsupported".
>>>>>>>>>>>>>>> 2. This led to a further discussion of release
>>>>>>>>>>>>>>> strategy - which I will start as a different thread. The main point being,
>>>>>>>>>>>>>>> if a release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>>>>> archived.
>>>>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require
>>>>>>>>>>>>>>> the tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage
>>>>>>>>>>>>>>> meeting to coordinate on tickets.
>>>>>>>>>>>>>>> 6. We noted that many of the issues on the list and some
>>>>>>>>>>>>>>> of the Jira tickets are related to configuration and setup and suggest
>>>>>>>>>>>>>>> better knowledge base management. We are interested in people taking an
>>>>>>>>>>>>>>> active role in that.
>>>>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a
>>>>>>>>>>>>>>> number of major improvements such that version 1.8 is very different from
>>>>>>>>>>>>>>> 1.5 (less than two years ago). A new topic is thus to move to a Major
>>>>>>>>>>>>>>> release cycle Version 2.0, and to consider a Long-Term-Support version of
>>>>>>>>>>>>>>> the Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>> Disclaimer:
>>>>>>>>>>
>>>>>>>>>> Privileged & confidential information is contained in this
>>>>>>>>>> message (including all attachments). If you are not an intended recipient
>>>>>>>>>> of this message, please destroy this message immediately and kindly notify
>>>>>>>>>> the sender by reply e-mail. Any unauthorised use or dissemination
>>>>>>>>>> of this message in any manner whatsoever, in whole or in part, is strictly
>>>>>>>>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>>>>>>>>> discussion purposes only and shall not be deemed or construed to be a
>>>>>>>>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>>>>>>>>> intended, written or sent to be used, and cannot and shall not be used, for
>>>>>>>>>> any unlawful purpose. This communication, including any attachments, may
>>>>>>>>>> not be free of viruses, interceptions or interference, and may not be
>>>>>>>>>> compatible with your systems. You should carry out your own virus checks
>>>>>>>>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>>>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any
>>>>>>>>>> damage that you may sustain as a result of viruses, incompleteness of this
>>>>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>>>>> experienced.
>>>>>>>>>>
>>>>>>>>> --
>>>>>>> Sent from Gmail Mobile
>>>>>>>
>>>>>> --
>> [image: Logo] <https://www.fiter.io>
>> *Robert Jakech* *| CTO*
>> *e:* robert@fiter.io
>> *w:* fiter.io <http://www.fiter.io>
>> *m:* +61458166091
>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>
> --
[image: Logo] <https://www.fiter.io>
*Robert Jakech* *| CTO*
*e:* robert@fiter.io
*w:* fiter.io <http://www.fiter.io>
*m:* +61458166091
[image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
<https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image: linkedin
icon] <https://www.linkedin.com/company/fiter-io>
Re: Cleaning up the JIRA
Posted by James Dailey <ja...@gmail.com>.
Hi Devs -
As previously discussed:
* we identified the open tickets that were older than 100 weeks with no
updates in over 100 weeks. ==> STALE Tickets
* just in case, we reviewed the open tickets, thank you Bharat and Robert.
* we now are closing the remaining stale tickets
I have applied two bulk actions on 294 tickets.
1) applied the Label: Cleanup2022
2) closed / with status "auto-closed"
You can now find these tickets with this JQL
project = FINERACT AND status = Closed AND labels = Cleanup2022 ORDER BY
createdDate DESC
That is also saved as this Filter:
https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352409
<https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352409>
I mean to say that we are NOT deleting such tickets, we are simply putting
them into the state that they are actually in:
No one is working on them, no one has worked on them in over 100weeks.
If you look at those tickets and have a desire to take one of them on, they
are still there and you can re-open.
but, please communicate on the list if you do so.
There are 41 tickets that we identified that *might* be useful to review
and incorporate into the roadmap.
We probably will need to further trim these down or close (with same status
as above) if we cannot verify that they are still open issues or
interesting for the community.
I will go back to the ROADMAP thread to discuss how we will trim and refine
tickets. But, this is your project, so do speak up there.
As we go forward, we will continuously add to the "Closed, auto-closed", as
part of our normal practices during each release cycle.
*We discussed and agreed on this approach. *
This will give us a clearer view of open tickets and prioritization.
After this action, we now have 357 tickets in "Status = open".
BTW This is still very high, given that we have less than 10 active
developers.
My target would be less than 100 open tickets. Do you agree?
I hope everyone is following along. How is this sounding?
Thanks,
On Thu, Nov 3, 2022 at 5:38 PM Robert Jakech <ro...@fiter.io> wrote:
> Copy that.
> Thanks James.
>
> On Fri, 4 Nov 2022 at 12:17 am, James Dailey <ja...@gmail.com>
> wrote:
>
>> Thank you Robert, Bharat. We've now done a quick review of the tickets.
>> we have picked out 41 possible items to consider in a roadmap
>> discussion
>>
>> Roadmap page:
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=231117062
>> (tickets at the bottom, suggested items for discussion )
>>
>> Out of 342 open / unresolved tickets (which were already filtered as
>> older than 100 weeks)
>> https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352370
>>
>> As previously discussed, our next step is to do a bulk action and close
>> those other 302 tickets with a label.
>> https://lists.apache.org/thread/b91nh3q919pro4wxg4pmqt0brfny9h1b
>>
>>
>>
>>
>> On Thu, Nov 3, 2022 at 6:04 AM Robert Jakech <ro...@fiter.io> wrote:
>>
>>> Hello James & Team.
>>> This is done (apologies for lateness). I appended the label as discussed
>>> to only user stories and not bugs.
>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>> open tickets)
>>> Thanks Ed for the granting Edit access.
>>> Cheers
>>> [image: Logo] <https://www.fiter.io>
>>> *Robert Jakech* *| CTO*
>>> *e:* robert@fiter.io
>>> *w:* fiter.io <http://www.fiter.io>
>>> *m:* +61458166091
>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>
>>>
>>> On Sat, 22 Oct 2022 at 03:43, James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>>>
>>>> I think I have set up the JIRA filter properly:
>>>> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
>>>> status = Open ORDER BY createdDate DESC
>>>>
>>>> This finds 342 tickets.
>>>> They do NOT need a full review.
>>>> See this: https://issues.apache.org/jira/issues/?filter=12352370
>>>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>>>
>>>> Again our community agreement is:
>>>>
>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>> generated and published to the list. The message will be to *please
>>>> review. * ** *DONE ***
>>>> 1. IF any reviewer finds that the ticket should NOT be archived,
>>>> then that person should indicate by putting a comment on the ticket
>>>> indicating their interest in working on the ticket further (validating
>>>> issue, specifying more, testing, fixing), ideally with the person
>>>> self-assigning it to themselves.
>>>> 2. Otherwise within a set period of time (five days), all those
>>>> tickets will be "Closed" with a tag added "Cleanup22", and a status of
>>>> "Auto Closed"
>>>> 2. Those closed tickets will be archived, and available for further
>>>> review and may be re-opened, with cause.
>>>>
>>>>
>>>> Let's give ourselves just five days to do a cursory review, but
>>>> starting on October 24th (72 hrs from now). IF we need more time, then for
>>>> sure we can do that, but we said five days because this isn't about
>>>> reviewing the tickets in detail.
>>>>
>>>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
>>>> different from your understanding.
>>>>
>>>> @Robert Jakech <ro...@fiter.io>
>>>> To not collide, let's use the filter above and modify as follows:
>>>>
>>>> Given DESCENDING order:
>>>>
>>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>>> open tickets)
>>>> a third volunteer can pick up 849 to 525 (another 75
>>>> tickets) *VOLUNTEER HERE*
>>>> a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets)
>>>> * VOLUNTEER HERE*
>>>>
>>>> James open tickets within ticket number range of 374 to 1 (142
>>>> open tickets)
>>>>
>>>> As we get into this, we may want to highlight certain tickets as a
>>>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>>>> (tag) . I will then add that list to a confluence page.
>>>>
>>>> it is unlikely that we can validate any of the BUG tickets as being
>>>> valid without the original person being involved and more context.
>>>> Therefore, they are completely stale and should be closed (as discussed).
>>>>
>>>> At this time, *do not close the tickets*. We will use a Bulk action
>>>> to close them and give them the same tag/label: Cleanup22
>>>>
>>>> This is just the first effort to try to prioritize.
>>>>
>>>> Thanks,
>>>> @jdailey
>>>>
>>>>
>>>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io> wrote:
>>>>
>>>>> Thanks James,
>>>>> So we don't create redundancies or duplications. Can we find a way to
>>>>> coordinate this?
>>>>> For example, Segregate the work among the ones who have raised their
>>>>> hands. Something like:
>>>>> Robert handles tickets with numbers from xxxy to xxzz and were created
>>>>> at least 26 months.
>>>>> Please let me know if that makes sense and suggest the range I can
>>>>> take on.
>>>>> [image: Logo] <https://www.fiter.io>
>>>>> *Robert Jakech* *| CTO*
>>>>> *e:* robert@fiter.io
>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>> *m:* +61458166091
>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>
>>>>>
>>>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Robert
>>>>>>
>>>>>> First step is to get a filter in Jira that shows all tickets that
>>>>>> were created over 26 months ago & remain open today. That filter should be
>>>>>> shared here.
>>>>>>
>>>>>> Step two, go through any of those and indicate it is an active issue
>>>>>> that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>>>> recent months then it is stale. This step can be done by anyone but if you
>>>>>> think a tix needs work then you’ll need to validate it.
>>>>>>
>>>>>> Step three - jira mass-action close all remaining in filter as
>>>>>> described.
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi James,
>>>>>>> Has this process started yet?
>>>>>>> I am happy to help, including going forward ensuring that all the
>>>>>>> tickets created have the compliance needed (description, version numbers
>>>>>>> etc). Please let me know.
>>>>>>> Cheers
>>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>>> *Robert Jakech* *| CTO*
>>>>>>> *e:* robert@fiter.io
>>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>>> *m:* +61458166091
>>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image:
>>>>>>> youtube icon]
>>>>>>> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1 (binding)
>>>>>>>>
>>>>>>>> We have three binding votes (PMC members) and support from active
>>>>>>>> community members. Thank you.
>>>>>>>> We have left this open for community input for over two weeks.
>>>>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>>>>> implementation of this set of policies and actions.
>>>>>>>>
>>>>>>>> I shall move this to a wiki page with the clarifications that Avik
>>>>>>>> offered.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi James, Devs,
>>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>>>>> do.
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 1. *At each release cycle*, a further list of tickets will be
>>>>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>>>>> will be considered "non-active".
>>>>>>>>>>
>>>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>>>
>>>>>>>>> With best regards,
>>>>>>>>> Avik.
>>>>>>>>>
>>>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>>>
>>>>>>>>>>> +1
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> +1
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Devs -
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>>>>>> average days open being over 1000 days (over the past two
>>>>>>>>>>>>>> years on any given day
>>>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months
>>>>>>>>>>>>>> will be generated and published to the list. The message will be to please
>>>>>>>>>>>>>> review.
>>>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>>>> 2. Otherwise within a set period of time (five days),
>>>>>>>>>>>>>> all those tickets will be "Closed" with a tag added "Cleanup22", and a
>>>>>>>>>>>>>> status of "Auto Closed"
>>>>>>>>>>>>>> 2. Those closed tickets will be archived, and available
>>>>>>>>>>>>>> for further review and may be re-opened, with cause.
>>>>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets
>>>>>>>>>>>>>> will be sorted based on which versions are affected. Versions older than
>>>>>>>>>>>>>> THREE ago will be considered "non-active".
>>>>>>>>>>>>>> 1. NB: This is a formalization of a practice we have,
>>>>>>>>>>>>>> which is to deprecate older versions and encourage our users to upgrade to
>>>>>>>>>>>>>> the most recent stable release. As we are on version 1.8 now, any issue
>>>>>>>>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>>>>>>>>> version 1.5 becomes "unsupported".
>>>>>>>>>>>>>> 2. This led to a further discussion of release
>>>>>>>>>>>>>> strategy - which I will start as a different thread. The main point being,
>>>>>>>>>>>>>> if a release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>>>> archived.
>>>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require
>>>>>>>>>>>>>> the tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage
>>>>>>>>>>>>>> meeting to coordinate on tickets.
>>>>>>>>>>>>>> 6. We noted that many of the issues on the list and some
>>>>>>>>>>>>>> of the Jira tickets are related to configuration and setup and suggest
>>>>>>>>>>>>>> better knowledge base management. We are interested in people taking an
>>>>>>>>>>>>>> active role in that.
>>>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a
>>>>>>>>>>>>>> number of major improvements such that version 1.8 is very different from
>>>>>>>>>>>>>> 1.5 (less than two years ago). A new topic is thus to move to a Major
>>>>>>>>>>>>>> release cycle Version 2.0, and to consider a Long-Term-Support version of
>>>>>>>>>>>>>> the Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>> Disclaimer:
>>>>>>>>>
>>>>>>>>> Privileged & confidential information is contained in this message
>>>>>>>>> (including all attachments). If you are not an intended recipient of this
>>>>>>>>> message, please destroy this message immediately and kindly notify
>>>>>>>>> the sender by reply e-mail. Any unauthorised use or dissemination
>>>>>>>>> of this message in any manner whatsoever, in whole or in part, is strictly
>>>>>>>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>>>>>>>> discussion purposes only and shall not be deemed or construed to be a
>>>>>>>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>>>>>>>> intended, written or sent to be used, and cannot and shall not be used, for
>>>>>>>>> any unlawful purpose. This communication, including any attachments, may
>>>>>>>>> not be free of viruses, interceptions or interference, and may not be
>>>>>>>>> compatible with your systems. You should carry out your own virus checks
>>>>>>>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any
>>>>>>>>> damage that you may sustain as a result of viruses, incompleteness of this
>>>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>>>> experienced.
>>>>>>>>>
>>>>>>>> --
>>>>>> Sent from Gmail Mobile
>>>>>>
>>>>> --
> [image: Logo] <https://www.fiter.io>
> *Robert Jakech* *| CTO*
> *e:* robert@fiter.io
> *w:* fiter.io <http://www.fiter.io>
> *m:* +61458166091
> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>
Re: Cleaning up the JIRA
Posted by Robert Jakech <ro...@fiter.io>.
Copy that.
Thanks James.
On Fri, 4 Nov 2022 at 12:17 am, James Dailey <ja...@gmail.com> wrote:
> Thank you Robert, Bharat. We've now done a quick review of the tickets.
> we have picked out 41 possible items to consider in a roadmap
> discussion
>
> Roadmap page:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=231117062
> (tickets at the bottom, suggested items for discussion )
>
> Out of 342 open / unresolved tickets (which were already filtered as older
> than 100 weeks)
> https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352370
>
> As previously discussed, our next step is to do a bulk action and close
> those other 302 tickets with a label.
> https://lists.apache.org/thread/b91nh3q919pro4wxg4pmqt0brfny9h1b
>
>
>
>
> On Thu, Nov 3, 2022 at 6:04 AM Robert Jakech <ro...@fiter.io> wrote:
>
>> Hello James & Team.
>> This is done (apologies for lateness). I appended the label as discussed
>> to only user stories and not bugs.
>> Robert open tickets within ticket number range of 1259 to 850 (75
>> open tickets)
>> Thanks Ed for the granting Edit access.
>> Cheers
>> [image: Logo] <https://www.fiter.io>
>> *Robert Jakech* *| CTO*
>> *e:* robert@fiter.io
>> *w:* fiter.io <http://www.fiter.io>
>> *m:* +61458166091
>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>
>>
>> On Sat, 22 Oct 2022 at 03:43, James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>>
>>> I think I have set up the JIRA filter properly:
>>> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
>>> status = Open ORDER BY createdDate DESC
>>>
>>> This finds 342 tickets.
>>> They do NOT need a full review.
>>> See this: https://issues.apache.org/jira/issues/?filter=12352370
>>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>>
>>> Again our community agreement is:
>>>
>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>> generated and published to the list. The message will be to *please
>>> review. * ** *DONE ***
>>> 1. IF any reviewer finds that the ticket should NOT be archived,
>>> then that person should indicate by putting a comment on the ticket
>>> indicating their interest in working on the ticket further (validating
>>> issue, specifying more, testing, fixing), ideally with the person
>>> self-assigning it to themselves.
>>> 2. Otherwise within a set period of time (five days), all those
>>> tickets will be "Closed" with a tag added "Cleanup22", and a status of
>>> "Auto Closed"
>>> 2. Those closed tickets will be archived, and available for further
>>> review and may be re-opened, with cause.
>>>
>>>
>>> Let's give ourselves just five days to do a cursory review, but starting
>>> on October 24th (72 hrs from now). IF we need more time, then for sure we
>>> can do that, but we said five days because this isn't about reviewing the
>>> tickets in detail.
>>>
>>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
>>> different from your understanding.
>>>
>>> @Robert Jakech <ro...@fiter.io>
>>> To not collide, let's use the filter above and modify as follows:
>>>
>>> Given DESCENDING order:
>>>
>>> Robert open tickets within ticket number range of 1259 to 850 (75
>>> open tickets)
>>> a third volunteer can pick up 849 to 525 (another 75
>>> tickets) *VOLUNTEER HERE*
>>> a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets)
>>> * VOLUNTEER HERE*
>>>
>>> James open tickets within ticket number range of 374 to 1 (142 open
>>> tickets)
>>>
>>> As we get into this, we may want to highlight certain tickets as a
>>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>>> (tag) . I will then add that list to a confluence page.
>>>
>>> it is unlikely that we can validate any of the BUG tickets as being
>>> valid without the original person being involved and more context.
>>> Therefore, they are completely stale and should be closed (as discussed).
>>>
>>> At this time, *do not close the tickets*. We will use a Bulk action to
>>> close them and give them the same tag/label: Cleanup22
>>>
>>> This is just the first effort to try to prioritize.
>>>
>>> Thanks,
>>> @jdailey
>>>
>>>
>>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io> wrote:
>>>
>>>> Thanks James,
>>>> So we don't create redundancies or duplications. Can we find a way to
>>>> coordinate this?
>>>> For example, Segregate the work among the ones who have raised their
>>>> hands. Something like:
>>>> Robert handles tickets with numbers from xxxy to xxzz and were created
>>>> at least 26 months.
>>>> Please let me know if that makes sense and suggest the range I can take
>>>> on.
>>>> [image: Logo] <https://www.fiter.io>
>>>> *Robert Jakech* *| CTO*
>>>> *e:* robert@fiter.io
>>>> *w:* fiter.io <http://www.fiter.io>
>>>> *m:* +61458166091
>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>
>>>>
>>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> Robert
>>>>>
>>>>> First step is to get a filter in Jira that shows all tickets that were
>>>>> created over 26 months ago & remain open today. That filter should be
>>>>> shared here.
>>>>>
>>>>> Step two, go through any of those and indicate it is an active issue
>>>>> that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>>> recent months then it is stale. This step can be done by anyone but if you
>>>>> think a tix needs work then you’ll need to validate it.
>>>>>
>>>>> Step three - jira mass-action close all remaining in filter as
>>>>> described.
>>>>>
>>>>>
>>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io> wrote:
>>>>>
>>>>>> Hi James,
>>>>>> Has this process started yet?
>>>>>> I am happy to help, including going forward ensuring that all the
>>>>>> tickets created have the compliance needed (description, version numbers
>>>>>> etc). Please let me know.
>>>>>> Cheers
>>>>>> [image: Logo] <https://www.fiter.io>
>>>>>> *Robert Jakech* *| CTO*
>>>>>> *e:* robert@fiter.io
>>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>>> *m:* +61458166091
>>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>>
>>>>>>
>>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> +1 (binding)
>>>>>>>
>>>>>>> We have three binding votes (PMC members) and support from active
>>>>>>> community members. Thank you.
>>>>>>> We have left this open for community input for over two weeks.
>>>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>>>> implementation of this set of policies and actions.
>>>>>>>
>>>>>>> I shall move this to a wiki page with the clarifications that Avik
>>>>>>> offered.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi James, Devs,
>>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>>>> do.
>>>>>>>>
>>>>>>>>>
>>>>>>>>> 1. *At each release cycle*, a further list of tickets will be
>>>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>>>> will be considered "non-active".
>>>>>>>>>
>>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>>
>>>>>>>> With best regards,
>>>>>>>> Avik.
>>>>>>>>
>>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>>
>>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Devs -
>>>>>>>>>>>>>
>>>>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>>>>> average days open being over 1000 days (over the past two
>>>>>>>>>>>>> years on any given day
>>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months
>>>>>>>>>>>>> will be generated and published to the list. The message will be to please
>>>>>>>>>>>>> review.
>>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>>> 2. Otherwise within a set period of time (five days),
>>>>>>>>>>>>> all those tickets will be "Closed" with a tag added "Cleanup22", and a
>>>>>>>>>>>>> status of "Auto Closed"
>>>>>>>>>>>>> 2. Those closed tickets will be archived, and available
>>>>>>>>>>>>> for further review and may be re-opened, with cause.
>>>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets will
>>>>>>>>>>>>> be sorted based on which versions are affected. Versions older than THREE
>>>>>>>>>>>>> ago will be considered "non-active".
>>>>>>>>>>>>> 1. NB: This is a formalization of a practice we have,
>>>>>>>>>>>>> which is to deprecate older versions and encourage our users to upgrade to
>>>>>>>>>>>>> the most recent stable release. As we are on version 1.8 now, any issue
>>>>>>>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>>>>>>>> version 1.5 becomes "unsupported".
>>>>>>>>>>>>> 2. This led to a further discussion of release strategy
>>>>>>>>>>>>> - which I will start as a different thread. The main point being, if a
>>>>>>>>>>>>> release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>>> archived.
>>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require the
>>>>>>>>>>>>> tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage meeting
>>>>>>>>>>>>> to coordinate on tickets.
>>>>>>>>>>>>> 6. We noted that many of the issues on the list and some
>>>>>>>>>>>>> of the Jira tickets are related to configuration and setup and suggest
>>>>>>>>>>>>> better knowledge base management. We are interested in people taking an
>>>>>>>>>>>>> active role in that.
>>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a
>>>>>>>>>>>>> number of major improvements such that version 1.8 is very different from
>>>>>>>>>>>>> 1.5 (less than two years ago). A new topic is thus to move to a Major
>>>>>>>>>>>>> release cycle Version 2.0, and to consider a Long-Term-Support version of
>>>>>>>>>>>>> the Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>> Disclaimer:
>>>>>>>>
>>>>>>>> Privileged & confidential information is contained in this message
>>>>>>>> (including all attachments). If you are not an intended recipient of this
>>>>>>>> message, please destroy this message immediately and kindly notify
>>>>>>>> the sender by reply e-mail. Any unauthorised use or dissemination
>>>>>>>> of this message in any manner whatsoever, in whole or in part, is strictly
>>>>>>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>>>>>>> discussion purposes only and shall not be deemed or construed to be a
>>>>>>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>>>>>>> intended, written or sent to be used, and cannot and shall not be used, for
>>>>>>>> any unlawful purpose. This communication, including any attachments, may
>>>>>>>> not be free of viruses, interceptions or interference, and may not be
>>>>>>>> compatible with your systems. You should carry out your own virus checks
>>>>>>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any damage
>>>>>>>> that you may sustain as a result of viruses, incompleteness of this
>>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>>> experienced.
>>>>>>>>
>>>>>>> --
>>>>> Sent from Gmail Mobile
>>>>>
>>>> --
[image: Logo] <https://www.fiter.io>
*Robert Jakech* *| CTO*
*e:* robert@fiter.io
*w:* fiter.io <http://www.fiter.io>
*m:* +61458166091
[image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
<https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image: linkedin
icon] <https://www.linkedin.com/company/fiter-io>
Re: Cleaning up the JIRA
Posted by James Dailey <ja...@gmail.com>.
Thank you Robert, Bharat. We've now done a quick review of the tickets.
we have picked out 41 possible items to consider in a roadmap discussion
Roadmap page:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=231117062
(tickets at the bottom, suggested items for discussion )
Out of 342 open / unresolved tickets (which were already filtered as older
than 100 weeks)
https://issues.apache.org/jira/browse/FINERACT-1268?filter=12352370
As previously discussed, our next step is to do a bulk action and close
those other 302 tickets with a label.
https://lists.apache.org/thread/b91nh3q919pro4wxg4pmqt0brfny9h1b
On Thu, Nov 3, 2022 at 6:04 AM Robert Jakech <ro...@fiter.io> wrote:
> Hello James & Team.
> This is done (apologies for lateness). I appended the label as discussed
> to only user stories and not bugs.
> Robert open tickets within ticket number range of 1259 to 850 (75 open
> tickets)
> Thanks Ed for the granting Edit access.
> Cheers
> [image: Logo] <https://www.fiter.io>
> *Robert Jakech* *| CTO*
> *e:* robert@fiter.io
> *w:* fiter.io <http://www.fiter.io>
> *m:* +61458166091
> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>
>
> On Sat, 22 Oct 2022 at 03:43, James Dailey <ja...@gmail.com> wrote:
>
>> Robert - good idea. Let's proceed with PLEASE REVIEW.
>>
>> I think I have set up the JIRA filter properly:
>> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
>> status = Open ORDER BY createdDate DESC
>>
>> This finds 342 tickets.
>> They do NOT need a full review.
>> See this: https://issues.apache.org/jira/issues/?filter=12352370
>> <https://issues.apache.org/jira/issues/?filter=12352370>
>>
>> Again our community agreement is:
>>
>> 1. *Archiving*: A list of tickets older than 26 months will be
>> generated and published to the list. The message will be to *please
>> review. * ** *DONE ***
>> 1. IF any reviewer finds that the ticket should NOT be archived,
>> then that person should indicate by putting a comment on the ticket
>> indicating their interest in working on the ticket further (validating
>> issue, specifying more, testing, fixing), ideally with the person
>> self-assigning it to themselves.
>> 2. Otherwise within a set period of time (five days), all those
>> tickets will be "Closed" with a tag added "Cleanup22", and a status of
>> "Auto Closed"
>> 2. Those closed tickets will be archived, and available for further
>> review and may be re-opened, with cause.
>>
>>
>> Let's give ourselves just five days to do a cursory review, but starting
>> on October 24th (72 hrs from now). IF we need more time, then for sure we
>> can do that, but we said five days because this isn't about reviewing the
>> tickets in detail.
>>
>> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
>> different from your understanding.
>>
>> @Robert Jakech <ro...@fiter.io>
>> To not collide, let's use the filter above and modify as follows:
>>
>> Given DESCENDING order:
>>
>> Robert open tickets within ticket number range of 1259 to 850 (75 open
>> tickets)
>> a third volunteer can pick up 849 to 525 (another 75
>> tickets) *VOLUNTEER HERE*
>> a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets)
>> * VOLUNTEER HERE*
>>
>> James open tickets within ticket number range of 374 to 1 (142 open
>> tickets)
>>
>> As we get into this, we may want to highlight certain tickets as a
>> "USEFUL IDEA" for a roadmap discussion. Please use label "Roadmap2022"
>> (tag) . I will then add that list to a confluence page.
>>
>> it is unlikely that we can validate any of the BUG tickets as being valid
>> without the original person being involved and more context. Therefore,
>> they are completely stale and should be closed (as discussed).
>>
>> At this time, *do not close the tickets*. We will use a Bulk action to
>> close them and give them the same tag/label: Cleanup22
>>
>> This is just the first effort to try to prioritize.
>>
>> Thanks,
>> @jdailey
>>
>>
>> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io> wrote:
>>
>>> Thanks James,
>>> So we don't create redundancies or duplications. Can we find a way to
>>> coordinate this?
>>> For example, Segregate the work among the ones who have raised their
>>> hands. Something like:
>>> Robert handles tickets with numbers from xxxy to xxzz and were created
>>> at least 26 months.
>>> Please let me know if that makes sense and suggest the range I can take
>>> on.
>>> [image: Logo] <https://www.fiter.io>
>>> *Robert Jakech* *| CTO*
>>> *e:* robert@fiter.io
>>> *w:* fiter.io <http://www.fiter.io>
>>> *m:* +61458166091
>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>
>>>
>>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>>> Robert
>>>>
>>>> First step is to get a filter in Jira that shows all tickets that were
>>>> created over 26 months ago & remain open today. That filter should be
>>>> shared here.
>>>>
>>>> Step two, go through any of those and indicate it is an active issue
>>>> that “should” be fixed. Ie if it doesn’t have any activity on it in
>>>> recent months then it is stale. This step can be done by anyone but if you
>>>> think a tix needs work then you’ll need to validate it.
>>>>
>>>> Step three - jira mass-action close all remaining in filter as
>>>> described.
>>>>
>>>>
>>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io> wrote:
>>>>
>>>>> Hi James,
>>>>> Has this process started yet?
>>>>> I am happy to help, including going forward ensuring that all the
>>>>> tickets created have the compliance needed (description, version numbers
>>>>> etc). Please let me know.
>>>>> Cheers
>>>>> [image: Logo] <https://www.fiter.io>
>>>>> *Robert Jakech* *| CTO*
>>>>> *e:* robert@fiter.io
>>>>> *w:* fiter.io <http://www.fiter.io>
>>>>> *m:* +61458166091
>>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>>
>>>>>
>>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> +1 (binding)
>>>>>>
>>>>>> We have three binding votes (PMC members) and support from active
>>>>>> community members. Thank you.
>>>>>> We have left this open for community input for over two weeks.
>>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>>> implementation of this set of policies and actions.
>>>>>>
>>>>>> I shall move this to a wiki page with the clarifications that Avik
>>>>>> offered.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi James, Devs,
>>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>>> do.
>>>>>>>
>>>>>>>>
>>>>>>>> 1. *At each release cycle*, a further list of tickets will be
>>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>>> will be considered "non-active".
>>>>>>>>
>>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>>
>>>>>>> With best regards,
>>>>>>> Avik.
>>>>>>>
>>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>>
>>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Devs -
>>>>>>>>>>>>
>>>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>>>> average days open being over 1000 days (over the past two
>>>>>>>>>>>> years on any given day
>>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>>
>>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will
>>>>>>>>>>>> be generated and published to the list. The message will be to please
>>>>>>>>>>>> review.
>>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>>> 2. Otherwise within a set period of time (five days),
>>>>>>>>>>>> all those tickets will be "Closed" with a tag added "Cleanup22", and a
>>>>>>>>>>>> status of "Auto Closed"
>>>>>>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>>>>>>> further review and may be re-opened, with cause.
>>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets will
>>>>>>>>>>>> be sorted based on which versions are affected. Versions older than THREE
>>>>>>>>>>>> ago will be considered "non-active".
>>>>>>>>>>>> 1. NB: This is a formalization of a practice we have,
>>>>>>>>>>>> which is to deprecate older versions and encourage our users to upgrade to
>>>>>>>>>>>> the most recent stable release. As we are on version 1.8 now, any issue
>>>>>>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>>>>>>> version 1.5 becomes "unsupported".
>>>>>>>>>>>> 2. This led to a further discussion of release strategy
>>>>>>>>>>>> - which I will start as a different thread. The main point being, if a
>>>>>>>>>>>> release is no longer a supported release, then those tickets are to be
>>>>>>>>>>>> archived.
>>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require the
>>>>>>>>>>>> tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage meeting
>>>>>>>>>>>> to coordinate on tickets.
>>>>>>>>>>>> 6. We noted that many of the issues on the list and some of
>>>>>>>>>>>> the Jira tickets are related to configuration and setup and suggest better
>>>>>>>>>>>> knowledge base management. We are interested in people taking an active
>>>>>>>>>>>> role in that.
>>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a number
>>>>>>>>>>>> of major improvements such that version 1.8 is very different from 1.5
>>>>>>>>>>>> (less than two years ago). A new topic is thus to move to a Major release
>>>>>>>>>>>> cycle Version 2.0, and to consider a Long-Term-Support version of the
>>>>>>>>>>>> Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>> Disclaimer:
>>>>>>>
>>>>>>> Privileged & confidential information is contained in this message
>>>>>>> (including all attachments). If you are not an intended recipient of this
>>>>>>> message, please destroy this message immediately and kindly notify
>>>>>>> the sender by reply e-mail. Any unauthorised use or dissemination of
>>>>>>> this message in any manner whatsoever, in whole or in part, is strictly
>>>>>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>>>>>> discussion purposes only and shall not be deemed or construed to be a
>>>>>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>>>>>> intended, written or sent to be used, and cannot and shall not be used, for
>>>>>>> any unlawful purpose. This communication, including any attachments, may
>>>>>>> not be free of viruses, interceptions or interference, and may not be
>>>>>>> compatible with your systems. You should carry out your own virus checks
>>>>>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any damage
>>>>>>> that you may sustain as a result of viruses, incompleteness of this
>>>>>>> message, a delay in receipt of this message or computer problems
>>>>>>> experienced.
>>>>>>>
>>>>>> --
>>>> Sent from Gmail Mobile
>>>>
>>>
Re: Cleaning up the JIRA
Posted by Robert Jakech <ro...@fiter.io>.
Hello James & Team.
This is done (apologies for lateness). I appended the label as discussed to
only user stories and not bugs.
Robert open tickets within ticket number range of 1259 to 850 (75 open
tickets)
Thanks Ed for the granting Edit access.
Cheers
[image: Logo] <https://www.fiter.io>
*Robert Jakech* *| CTO*
*e:* robert@fiter.io
*w:* fiter.io <http://www.fiter.io>
*m:* +61458166091
[image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
<https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image: linkedin
icon] <https://www.linkedin.com/company/fiter-io>
On Sat, 22 Oct 2022 at 03:43, James Dailey <ja...@gmail.com> wrote:
> Robert - good idea. Let's proceed with PLEASE REVIEW.
>
> I think I have set up the JIRA filter properly:
> project = FINERACT AND createdDate <= -100w AND updated <=-100w AND
> status = Open ORDER BY createdDate DESC
>
> This finds 342 tickets.
> They do NOT need a full review.
> See this: https://issues.apache.org/jira/issues/?filter=12352370
> <https://issues.apache.org/jira/issues/?filter=12352370>
>
> Again our community agreement is:
>
> 1. *Archiving*: A list of tickets older than 26 months will be
> generated and published to the list. The message will be to *please
> review. * ** *DONE ***
> 1. IF any reviewer finds that the ticket should NOT be archived,
> then that person should indicate by putting a comment on the ticket
> indicating their interest in working on the ticket further (validating
> issue, specifying more, testing, fixing), ideally with the person
> self-assigning it to themselves.
> 2. Otherwise within a set period of time (five days), all those
> tickets will be "Closed" with a tag added "Cleanup22", and a status of
> "Auto Closed"
> 2. Those closed tickets will be archived, and available for further
> review and may be re-opened, with cause.
>
>
> Let's give ourselves just five days to do a cursory review, but starting
> on October 24th (72 hrs from now). IF we need more time, then for sure we
> can do that, but we said five days because this isn't about reviewing the
> tickets in detail.
>
> @Aleksandar Vidakovic <al...@apache.org> / let me know if this is
> different from your understanding.
>
> @Robert Jakech <ro...@fiter.io>
> To not collide, let's use the filter above and modify as follows:
>
> Given DESCENDING order:
>
> Robert open tickets within ticket number range of 1259 to 850 (75 open
> tickets)
> a third volunteer can pick up 849 to 525 (another 75
> tickets) *VOLUNTEER HERE*
> a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets)
> * VOLUNTEER HERE*
>
> James open tickets within ticket number range of 374 to 1 (142 open
> tickets)
>
> As we get into this, we may want to highlight certain tickets as a "USEFUL
> IDEA" for a roadmap discussion. Please use label "Roadmap2022" (tag) . I
> will then add that list to a confluence page.
>
> it is unlikely that we can validate any of the BUG tickets as being valid
> without the original person being involved and more context. Therefore,
> they are completely stale and should be closed (as discussed).
>
> At this time, *do not close the tickets*. We will use a Bulk action to
> close them and give them the same tag/label: Cleanup22
>
> This is just the first effort to try to prioritize.
>
> Thanks,
> @jdailey
>
>
> On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io> wrote:
>
>> Thanks James,
>> So we don't create redundancies or duplications. Can we find a way to
>> coordinate this?
>> For example, Segregate the work among the ones who have raised their
>> hands. Something like:
>> Robert handles tickets with numbers from xxxy to xxzz and were created at
>> least 26 months.
>> Please let me know if that makes sense and suggest the range I can take
>> on.
>> [image: Logo] <https://www.fiter.io>
>> *Robert Jakech* *| CTO*
>> *e:* robert@fiter.io
>> *w:* fiter.io <http://www.fiter.io>
>> *m:* +61458166091
>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>
>>
>> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Robert
>>>
>>> First step is to get a filter in Jira that shows all tickets that were
>>> created over 26 months ago & remain open today. That filter should be
>>> shared here.
>>>
>>> Step two, go through any of those and indicate it is an active issue
>>> that “should” be fixed. Ie if it doesn’t have any activity on it in
>>> recent months then it is stale. This step can be done by anyone but if you
>>> think a tix needs work then you’ll need to validate it.
>>>
>>> Step three - jira mass-action close all remaining in filter as
>>> described.
>>>
>>>
>>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io> wrote:
>>>
>>>> Hi James,
>>>> Has this process started yet?
>>>> I am happy to help, including going forward ensuring that all the
>>>> tickets created have the compliance needed (description, version numbers
>>>> etc). Please let me know.
>>>> Cheers
>>>> [image: Logo] <https://www.fiter.io>
>>>> *Robert Jakech* *| CTO*
>>>> *e:* robert@fiter.io
>>>> *w:* fiter.io <http://www.fiter.io>
>>>> *m:* +61458166091
>>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>>
>>>>
>>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> +1 (binding)
>>>>>
>>>>> We have three binding votes (PMC members) and support from active
>>>>> community members. Thank you.
>>>>> We have left this open for community input for over two weeks.
>>>>> So, to re-enforce our process: this is closed and we proceed to
>>>>> implementation of this set of policies and actions.
>>>>>
>>>>> I shall move this to a wiki page with the clarifications that Avik
>>>>> offered.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io> wrote:
>>>>>
>>>>>> Hi James, Devs,
>>>>>>
>>>>>> +1
>>>>>>
>>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>>> do.
>>>>>>
>>>>>>>
>>>>>>> 1. *At each release cycle*, a further list of tickets will be
>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>> will be considered "non-active".
>>>>>>>
>>>>>>> To clarify for other readers, the bold part is applicable to
>>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>>
>>>>>> With best regards,
>>>>>> Avik.
>>>>>>
>>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>>> lukumubarth@gmail.com> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>>
>>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Devs -
>>>>>>>>>>>
>>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>>> average days open being over 1000 days (over the past two years
>>>>>>>>>>> on any given day
>>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>>> See details I shared on wiki
>>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>>
>>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will
>>>>>>>>>>> be generated and published to the list. The message will be to please
>>>>>>>>>>> review.
>>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>>>>>>> of "Auto Closed"
>>>>>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>>>>>> further review and may be re-opened, with cause.
>>>>>>>>>>> 3. *At each release cycle*, a further list of tickets will
>>>>>>>>>>> be sorted based on which versions are affected. Versions older than THREE
>>>>>>>>>>> ago will be considered "non-active".
>>>>>>>>>>> 1. NB: This is a formalization of a practice we have,
>>>>>>>>>>> which is to deprecate older versions and encourage our users to upgrade to
>>>>>>>>>>> the most recent stable release. As we are on version 1.8 now, any issue
>>>>>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>>>>>> version 1.5 becomes "unsupported".
>>>>>>>>>>> 2. This led to a further discussion of release strategy -
>>>>>>>>>>> which I will start as a different thread. The main point being, if a
>>>>>>>>>>> release is no longer a supported release, then those tickets are to be
>>>>>>>>>>> archived.
>>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require the
>>>>>>>>>>> tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>>> 5. We will hold a regular - monthly - issue triage meeting
>>>>>>>>>>> to coordinate on tickets.
>>>>>>>>>>> 6. We noted that many of the issues on the list and some of
>>>>>>>>>>> the Jira tickets are related to configuration and setup and suggest better
>>>>>>>>>>> knowledge base management. We are interested in people taking an active
>>>>>>>>>>> role in that.
>>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a number
>>>>>>>>>>> of major improvements such that version 1.8 is very different from 1.5
>>>>>>>>>>> (less than two years ago). A new topic is thus to move to a Major release
>>>>>>>>>>> cycle Version 2.0, and to consider a Long-Term-Support version of the
>>>>>>>>>>> Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> Disclaimer:
>>>>>>
>>>>>> Privileged & confidential information is contained in this message
>>>>>> (including all attachments). If you are not an intended recipient of this
>>>>>> message, please destroy this message immediately and kindly notify
>>>>>> the sender by reply e-mail. Any unauthorised use or dissemination of
>>>>>> this message in any manner whatsoever, in whole or in part, is strictly
>>>>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>>>>> discussion purposes only and shall not be deemed or construed to be a
>>>>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>>>>> intended, written or sent to be used, and cannot and shall not be used, for
>>>>>> any unlawful purpose. This communication, including any attachments, may
>>>>>> not be free of viruses, interceptions or interference, and may not be
>>>>>> compatible with your systems. You should carry out your own virus checks
>>>>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>>>>> *Fynarfin Tech Private Limited* shall not be liable for any damage
>>>>>> that you may sustain as a result of viruses, incompleteness of this
>>>>>> message, a delay in receipt of this message or computer problems
>>>>>> experienced.
>>>>>>
>>>>> --
>>> Sent from Gmail Mobile
>>>
>>
Re: Cleaning up the JIRA
Posted by James Dailey <ja...@gmail.com>.
Robert - good idea. Let's proceed with PLEASE REVIEW.
I think I have set up the JIRA filter properly:
project = FINERACT AND createdDate <= -100w AND updated <=-100w AND status
= Open ORDER BY createdDate DESC
This finds 342 tickets.
They do NOT need a full review.
See this: https://issues.apache.org/jira/issues/?filter=12352370
<https://issues.apache.org/jira/issues/?filter=12352370>
Again our community agreement is:
1. *Archiving*: A list of tickets older than 26 months will be generated
and published to the list. The message will be to *please review.
* ** *DONE
***
1. IF any reviewer finds that the ticket should NOT be archived, then
that person should indicate by putting a comment on the ticket indicating
their interest in working on the ticket further (validating issue,
specifying more, testing, fixing), ideally with the person self-assigning
it to themselves.
2. Otherwise within a set period of time (five days), all those
tickets will be "Closed" with a tag added "Cleanup22", and a status of
"Auto Closed"
2. Those closed tickets will be archived, and available for further
review and may be re-opened, with cause.
Let's give ourselves just five days to do a cursory review, but starting on
October 24th (72 hrs from now). IF we need more time, then for sure we can
do that, but we said five days because this isn't about reviewing the
tickets in detail.
@Aleksandar Vidakovic <al...@apache.org> / let me know if this is
different from your understanding.
@Robert Jakech <ro...@fiter.io>
To not collide, let's use the filter above and modify as follows:
Given DESCENDING order:
Robert open tickets within ticket number range of 1259 to 850 (75 open
tickets)
a third volunteer can pick up 849 to 525 (another 75 tickets)
*VOLUNTEER HERE*
a fourth volunteer can pick up 524 to 374 ( ~ 50 tickets)
* VOLUNTEER HERE*
James open tickets within ticket number range of 374 to 1 (142 open
tickets)
As we get into this, we may want to highlight certain tickets as a "USEFUL
IDEA" for a roadmap discussion. Please use label "Roadmap2022" (tag) . I
will then add that list to a confluence page.
it is unlikely that we can validate any of the BUG tickets as being valid
without the original person being involved and more context. Therefore,
they are completely stale and should be closed (as discussed).
At this time, *do not close the tickets*. We will use a Bulk action to
close them and give them the same tag/label: Cleanup22
This is just the first effort to try to prioritize.
Thanks,
@jdailey
On Wed, Oct 19, 2022 at 11:54 PM Robert Jakech <ro...@fiter.io> wrote:
> Thanks James,
> So we don't create redundancies or duplications. Can we find a way to
> coordinate this?
> For example, Segregate the work among the ones who have raised their
> hands. Something like:
> Robert handles tickets with numbers from xxxy to xxzz and were created at
> least 26 months.
> Please let me know if that makes sense and suggest the range I can take on.
> [image: Logo] <https://www.fiter.io>
> *Robert Jakech* *| CTO*
> *e:* robert@fiter.io
> *w:* fiter.io <http://www.fiter.io>
> *m:* +61458166091
> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>
>
> On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com> wrote:
>
>> Robert
>>
>> First step is to get a filter in Jira that shows all tickets that were
>> created over 26 months ago & remain open today. That filter should be
>> shared here.
>>
>> Step two, go through any of those and indicate it is an active issue that
>> “should” be fixed. Ie if it doesn’t have any activity on it in
>> recent months then it is stale. This step can be done by anyone but if you
>> think a tix needs work then you’ll need to validate it.
>>
>> Step three - jira mass-action close all remaining in filter as described.
>>
>>
>>
>> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io> wrote:
>>
>>> Hi James,
>>> Has this process started yet?
>>> I am happy to help, including going forward ensuring that all the
>>> tickets created have the compliance needed (description, version numbers
>>> etc). Please let me know.
>>> Cheers
>>> [image: Logo] <https://www.fiter.io>
>>> *Robert Jakech* *| CTO*
>>> *e:* robert@fiter.io
>>> *w:* fiter.io <http://www.fiter.io>
>>> *m:* +61458166091
>>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>>
>>>
>>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>>> +1 (binding)
>>>>
>>>> We have three binding votes (PMC members) and support from active
>>>> community members. Thank you.
>>>> We have left this open for community input for over two weeks.
>>>> So, to re-enforce our process: this is closed and we proceed to
>>>> implementation of this set of policies and actions.
>>>>
>>>> I shall move this to a wiki page with the clarifications that Avik
>>>> offered.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io> wrote:
>>>>
>>>>> Hi James, Devs,
>>>>>
>>>>> +1
>>>>>
>>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>>> pipelines / actions to make it simpler to execute as many other communities
>>>>> do.
>>>>>
>>>>>>
>>>>>> 1. *At each release cycle*, a further list of tickets will be
>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>> will be considered "non-active".
>>>>>>
>>>>>> To clarify for other readers, the bold part is applicable to
>>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>>
>>>>> With best regards,
>>>>> Avik.
>>>>>
>>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <
>>>>> lukumubarth@gmail.com> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1 for the suggested approach.
>>>>>>>>>
>>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Devs -
>>>>>>>>>>
>>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>>> average days open being over 1000 days (over the past two years
>>>>>>>>>> on any given day
>>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>>> See details I shared on wiki
>>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>>> clean up in the next week or so.
>>>>>>>>>>
>>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will
>>>>>>>>>> be generated and published to the list. The message will be to please
>>>>>>>>>> review.
>>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>>>>>> of "Auto Closed"
>>>>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>>>>> further review and may be re-opened, with cause.
>>>>>>>>>> 3. *At each release cycle*, a further list of tickets will be
>>>>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>>>>> will be considered "non-active".
>>>>>>>>>> 1. NB: This is a formalization of a practice we have,
>>>>>>>>>> which is to deprecate older versions and encourage our users to upgrade to
>>>>>>>>>> the most recent stable release. As we are on version 1.8 now, any issue
>>>>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>>>>> version 1.5 becomes "unsupported".
>>>>>>>>>> 2. This led to a further discussion of release strategy -
>>>>>>>>>> which I will start as a different thread. The main point being, if a
>>>>>>>>>> release is no longer a supported release, then those tickets are to be
>>>>>>>>>> archived.
>>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require the
>>>>>>>>>> tickets to include "Version affected" and "Component" to be filled
>>>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>>> 5. We will hold a regular - monthly - issue triage meeting to
>>>>>>>>>> coordinate on tickets.
>>>>>>>>>> 6. We noted that many of the issues on the list and some of
>>>>>>>>>> the Jira tickets are related to configuration and setup and suggest better
>>>>>>>>>> knowledge base management. We are interested in people taking an active
>>>>>>>>>> role in that.
>>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a number
>>>>>>>>>> of major improvements such that version 1.8 is very different from 1.5
>>>>>>>>>> (less than two years ago). A new topic is thus to move to a Major release
>>>>>>>>>> cycle Version 2.0, and to consider a Long-Term-Support version of the
>>>>>>>>>> Fineract1.x . I can kick that off on a new thread as well.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>> Disclaimer:
>>>>>
>>>>> Privileged & confidential information is contained in this message
>>>>> (including all attachments). If you are not an intended recipient of this
>>>>> message, please destroy this message immediately and kindly notify
>>>>> the sender by reply e-mail. Any unauthorised use or dissemination of
>>>>> this message in any manner whatsoever, in whole or in part, is strictly
>>>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>>>> discussion purposes only and shall not be deemed or construed to be a
>>>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>>>> intended, written or sent to be used, and cannot and shall not be used, for
>>>>> any unlawful purpose. This communication, including any attachments, may
>>>>> not be free of viruses, interceptions or interference, and may not be
>>>>> compatible with your systems. You should carry out your own virus checks
>>>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>>>> *Fynarfin Tech Private Limited* shall not be liable for any damage
>>>>> that you may sustain as a result of viruses, incompleteness of this
>>>>> message, a delay in receipt of this message or computer problems
>>>>> experienced.
>>>>>
>>>> --
>> Sent from Gmail Mobile
>>
>
Re: Cleaning up the JIRA
Posted by Robert Jakech <ro...@fiter.io>.
Thanks James,
So we don't create redundancies or duplications. Can we find a way to
coordinate this?
For example, Segregate the work among the ones who have raised their hands.
Something like:
Robert handles tickets with numbers from xxxy to xxzz and were created at
least 26 months.
Please let me know if that makes sense and suggest the range I can take on.
[image: Logo] <https://www.fiter.io>
*Robert Jakech* *| CTO*
*e:* robert@fiter.io
*w:* fiter.io <http://www.fiter.io>
*m:* +61458166091
[image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
<https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image: linkedin
icon] <https://www.linkedin.com/company/fiter-io>
On Thu, 20 Oct 2022 at 14:28, James Dailey <ja...@gmail.com> wrote:
> Robert
>
> First step is to get a filter in Jira that shows all tickets that were
> created over 26 months ago & remain open today. That filter should be
> shared here.
>
> Step two, go through any of those and indicate it is an active issue that
> “should” be fixed. Ie if it doesn’t have any activity on it in
> recent months then it is stale. This step can be done by anyone but if you
> think a tix needs work then you’ll need to validate it.
>
> Step three - jira mass-action close all remaining in filter as described.
>
>
> On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io> wrote:
>
>> Hi James,
>> Has this process started yet?
>> I am happy to help, including going forward ensuring that all the tickets
>> created have the compliance needed (description, version numbers etc).
>> Please let me know.
>> Cheers
>> [image: Logo] <https://www.fiter.io>
>> *Robert Jakech* *| CTO*
>> *e:* robert@fiter.io
>> *w:* fiter.io <http://www.fiter.io>
>> *m:* +61458166091
>> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube
>> icon] <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
>> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>>
>>
>> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> +1 (binding)
>>>
>>> We have three binding votes (PMC members) and support from active
>>> community members. Thank you.
>>> We have left this open for community input for over two weeks.
>>> So, to re-enforce our process: this is closed and we proceed to
>>> implementation of this set of policies and actions.
>>>
>>> I shall move this to a wiki page with the clarifications that Avik
>>> offered.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io> wrote:
>>>
>>>> Hi James, Devs,
>>>>
>>>> +1
>>>>
>>>> There should be some bulk interfaces or JIRA APIs to drive via
>>>> pipelines / actions to make it simpler to execute as many other communities
>>>> do.
>>>>
>>>>>
>>>>> 1. *At each release cycle*, a further list of tickets will be
>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>> will be considered "non-active".
>>>>>
>>>>> To clarify for other readers, the bold part is applicable to
>>>> minor/major release cycles and not for patch / hotfix releases.
>>>>
>>>> With best regards,
>>>> Avik.
>>>>
>>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <lu...@gmail.com>
>>>> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>>> cheetah@monkeysintown.com> a écrit :
>>>>>
>>>>>> +1
>>>>>>
>>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1 for the suggested approach.
>>>>>>>>
>>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Devs -
>>>>>>>>>
>>>>>>>>> We currently have a lot of open and stale tickets, with the
>>>>>>>>> average days open being over 1000 days (over the past two years
>>>>>>>>> on any given day
>>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>>> See details I shared on wiki
>>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>>> clean up in the next week or so.
>>>>>>>>>
>>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>>>>>>> generated and published to the list. The message will be to please review.
>>>>>>>>>
>>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>>> person self-assigning it to themselves.
>>>>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>>>>> of "Auto Closed"
>>>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>>>> further review and may be re-opened, with cause.
>>>>>>>>> 3. *At each release cycle*, a further list of tickets will be
>>>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>>>> will be considered "non-active".
>>>>>>>>> 1. NB: This is a formalization of a practice we have,
>>>>>>>>> which is to deprecate older versions and encourage our users to upgrade to
>>>>>>>>> the most recent stable release. As we are on version 1.8 now, any issue
>>>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>>>> version 1.5 becomes "unsupported".
>>>>>>>>> 2. This led to a further discussion of release strategy -
>>>>>>>>> which I will start as a different thread. The main point being, if a
>>>>>>>>> release is no longer a supported release, then those tickets are to be
>>>>>>>>> archived.
>>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require the
>>>>>>>>> tickets to include "Version affected" and "Component" to be filled
>>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>>> 5. We will hold a regular - monthly - issue triage meeting to
>>>>>>>>> coordinate on tickets.
>>>>>>>>> 6. We noted that many of the issues on the list and some of
>>>>>>>>> the Jira tickets are related to configuration and setup and suggest better
>>>>>>>>> knowledge base management. We are interested in people taking an active
>>>>>>>>> role in that.
>>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a number of
>>>>>>>>> major improvements such that version 1.8 is very different from 1.5 (less
>>>>>>>>> than two years ago). A new topic is thus to move to a Major release cycle
>>>>>>>>> Version 2.0, and to consider a Long-Term-Support version of the Fineract1.x
>>>>>>>>> . I can kick that off on a new thread as well.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>> Disclaimer:
>>>>
>>>> Privileged & confidential information is contained in this message
>>>> (including all attachments). If you are not an intended recipient of this
>>>> message, please destroy this message immediately and kindly notify
>>>> the sender by reply e-mail. Any unauthorised use or dissemination of
>>>> this message in any manner whatsoever, in whole or in part, is strictly
>>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>>> discussion purposes only and shall not be deemed or construed to be a
>>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>>> intended, written or sent to be used, and cannot and shall not be used, for
>>>> any unlawful purpose. This communication, including any attachments, may
>>>> not be free of viruses, interceptions or interference, and may not be
>>>> compatible with your systems. You should carry out your own virus checks
>>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>>> *Fynarfin Tech Private Limited* shall not be liable for any damage
>>>> that you may sustain as a result of viruses, incompleteness of this
>>>> message, a delay in receipt of this message or computer problems
>>>> experienced.
>>>>
>>> --
> Sent from Gmail Mobile
>
Re: Cleaning up the JIRA
Posted by James Dailey <ja...@gmail.com>.
Robert
First step is to get a filter in Jira that shows all tickets that were
created over 26 months ago & remain open today. That filter should be
shared here.
Step two, go through any of those and indicate it is an active issue that
“should” be fixed. Ie if it doesn’t have any activity on it in
recent months then it is stale. This step can be done by anyone but if you
think a tix needs work then you’ll need to validate it.
Step three - jira mass-action close all remaining in filter as described.
On Wed, Oct 19, 2022 at 2:42 PM Robert Jakech <ro...@fiter.io> wrote:
> Hi James,
> Has this process started yet?
> I am happy to help, including going forward ensuring that all the tickets
> created have the compliance needed (description, version numbers etc).
> Please let me know.
> Cheers
> [image: Logo] <https://www.fiter.io>
> *Robert Jakech* *| CTO*
> *e:* robert@fiter.io
> *w:* fiter.io <http://www.fiter.io>
> *m:* +61458166091
> [image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
> <https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image:
> linkedin icon] <https://www.linkedin.com/company/fiter-io>
>
>
> On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com> wrote:
>
>> +1 (binding)
>>
>> We have three binding votes (PMC members) and support from active
>> community members. Thank you.
>> We have left this open for community input for over two weeks.
>> So, to re-enforce our process: this is closed and we proceed to
>> implementation of this set of policies and actions.
>>
>> I shall move this to a wiki page with the clarifications that Avik
>> offered.
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io> wrote:
>>
>>> Hi James, Devs,
>>>
>>> +1
>>>
>>> There should be some bulk interfaces or JIRA APIs to drive via pipelines
>>> / actions to make it simpler to execute as many other communities do.
>>>
>>>>
>>>> 1. *At each release cycle*, a further list of tickets will be
>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>> will be considered "non-active".
>>>>
>>>> To clarify for other readers, the bold part is applicable to
>>> minor/major release cycles and not for patch / hotfix releases.
>>>
>>> With best regards,
>>> Avik.
>>>
>>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <lu...@gmail.com>
>>> wrote:
>>>
>>>> +1
>>>>
>>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>>> cheetah@monkeysintown.com> a écrit :
>>>>
>>>>> +1
>>>>>
>>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org> wrote:
>>>>>>
>>>>>>> +1 for the suggested approach.
>>>>>>>
>>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <
>>>>>>> jamespdailey@gmail.com> wrote:
>>>>>>>
>>>>>>>> Devs -
>>>>>>>>
>>>>>>>> We currently have a lot of open and stale tickets, with the average
>>>>>>>> days open being over 1000 days (over the past two years on any
>>>>>>>> given day
>>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>>> See details I shared on wiki
>>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>>> including recording. If there is no objection we will begin this
>>>>>>>> clean up in the next week or so.
>>>>>>>>
>>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>>>>>> generated and published to the list. The message will be to please review.
>>>>>>>>
>>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>>> person self-assigning it to themselves.
>>>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>>>> of "Auto Closed"
>>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>>> further review and may be re-opened, with cause.
>>>>>>>> 3. *At each release cycle*, a further list of tickets will be
>>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>>> will be considered "non-active".
>>>>>>>> 1. NB: This is a formalization of a practice we have, which
>>>>>>>> is to deprecate older versions and encourage our users to upgrade to the
>>>>>>>> most recent stable release. As we are on version 1.8 now, any issue
>>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>>> version 1.5 becomes "unsupported".
>>>>>>>> 2. This led to a further discussion of release strategy -
>>>>>>>> which I will start as a different thread. The main point being, if a
>>>>>>>> release is no longer a supported release, then those tickets are to be
>>>>>>>> archived.
>>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require the
>>>>>>>> tickets to include "Version affected" and "Component" to be filled
>>>>>>>> out. This allows the sorting above and provides for the
>>>>>>>> ability to trace the origin of the issue. We also seek to have better
>>>>>>>> ticket reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>>> 5. We will hold a regular - monthly - issue triage meeting to
>>>>>>>> coordinate on tickets.
>>>>>>>> 6. We noted that many of the issues on the list and some of
>>>>>>>> the Jira tickets are related to configuration and setup and suggest better
>>>>>>>> knowledge base management. We are interested in people taking an active
>>>>>>>> role in that.
>>>>>>>> 7. *Release Cycles: *We noted that we have gotten a number of
>>>>>>>> major improvements such that version 1.8 is very different from 1.5 (less
>>>>>>>> than two years ago). A new topic is thus to move to a Major release cycle
>>>>>>>> Version 2.0, and to consider a Long-Term-Support version of the Fineract1.x
>>>>>>>> . I can kick that off on a new thread as well.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>> Disclaimer:
>>>
>>> Privileged & confidential information is contained in this message
>>> (including all attachments). If you are not an intended recipient of this
>>> message, please destroy this message immediately and kindly notify
>>> the sender by reply e-mail. Any unauthorised use or dissemination of
>>> this message in any manner whatsoever, in whole or in part, is strictly
>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>> discussion purposes only and shall not be deemed or construed to be a
>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>> intended, written or sent to be used, and cannot and shall not be used, for
>>> any unlawful purpose. This communication, including any attachments, may
>>> not be free of viruses, interceptions or interference, and may not be
>>> compatible with your systems. You should carry out your own virus checks
>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>> *Fynarfin Tech Private Limited* shall not be liable for any damage that
>>> you may sustain as a result of viruses, incompleteness of this message, a
>>> delay in receipt of this message or computer problems experienced.
>>>
>> --
Sent from Gmail Mobile
Re: Cleaning up the JIRA
Posted by Robert Jakech <ro...@fiter.io>.
Hi James,
Has this process started yet?
I am happy to help, including going forward ensuring that all the tickets
created have the compliance needed (description, version numbers etc).
Please let me know.
Cheers
[image: Logo] <https://www.fiter.io>
*Robert Jakech* *| CTO*
*e:* robert@fiter.io
*w:* fiter.io <http://www.fiter.io>
*m:* +61458166091
[image: twitter icon] <https://twitter.com/Fiter_io> [image: youtube icon]
<https://www.youtube.com/channel/UCfWztdFtHI3PwaSLAEcwTNQ> [image: linkedin
icon] <https://www.linkedin.com/company/fiter-io>
On Tue, 11 Oct 2022 at 03:27, James Dailey <ja...@gmail.com> wrote:
> +1 (binding)
>
> We have three binding votes (PMC members) and support from active
> community members. Thank you.
> We have left this open for community input for over two weeks.
> So, to re-enforce our process: this is closed and we proceed to
> implementation of this set of policies and actions.
>
> I shall move this to a wiki page with the clarifications that Avik
> offered.
>
>
>
>
>
>
>
> On Mon, Sep 19, 2022 at 7:39 AM Avik Ganguly <av...@fynarfin.io> wrote:
>
>> Hi James, Devs,
>>
>> +1
>>
>> There should be some bulk interfaces or JIRA APIs to drive via pipelines
>> / actions to make it simpler to execute as many other communities do.
>>
>>>
>>> 1. *At each release cycle*, a further list of tickets will be sorted
>>> based on which versions are affected. Versions older than THREE ago will be
>>> considered "non-active".
>>>
>>> To clarify for other readers, the bold part is applicable to minor/major
>> release cycles and not for patch / hotfix releases.
>>
>> With best regards,
>> Avik.
>>
>> On Fri, Sep 16, 2022 at 8:11 PM Chantilly Muyaya <lu...@gmail.com>
>> wrote:
>>
>>> +1
>>>
>>> Le ven. 16 sept. 2022 à 15:25, Aleksandar Vidakovic <
>>> cheetah@monkeysintown.com> a écrit :
>>>
>>>> +1
>>>>
>>>> On Fri, Sep 16, 2022 at 9:10 AM Bruce <br...@gmail.com> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> On Fri, Sep 16, 2022, 9:48 AM Bharath Gowda <bg...@mifos.org> wrote:
>>>>>
>>>>>> +1 for the suggested approach.
>>>>>>
>>>>>> 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 Fri, Sep 16, 2022 at 10:42 AM James Dailey <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Devs -
>>>>>>>
>>>>>>> We currently have a lot of open and stale tickets, with the average
>>>>>>> days open being over 1000 days (over the past two years on any
>>>>>>> given day
>>>>>>> <https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12319420&periodName=monthly&daysprevious=730&selectedProjectId=12319420&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Aaverageage-report&atl_token=A5KQ-2QAV-T4JA-FDED_27535cfecdbfc0e03095e17815dc0d6cf7af61a1_lin&Next=Next>).
>>>>>>> A group of us met on Zoom to discuss and we propose the below approach.
>>>>>>> See details I shared on wiki
>>>>>>> <https://cwiki.apache.org/confluence/display/FINERACT/Jira+Clean+Up>,
>>>>>>> including recording. If there is no objection we will begin this
>>>>>>> clean up in the next week or so.
>>>>>>>
>>>>>>> 1. *Archiving*: A list of tickets older than 26 months will be
>>>>>>> generated and published to the list. The message will be to please review.
>>>>>>>
>>>>>>> 1. IF any reviewer finds that the ticket should NOT be
>>>>>>> archived, then that person should indicate by putting a comment on the
>>>>>>> ticket indicating their interest in working on the ticket further
>>>>>>> (validating issue, specifying more, testing, fixing), ideally with the
>>>>>>> person self-assigning it to themselves.
>>>>>>> 2. Otherwise within a set period of time (five days), all
>>>>>>> those tickets will be "Closed" with a tag added "Cleanup22", and a status
>>>>>>> of "Auto Closed"
>>>>>>> 2. Those closed tickets will be archived, and available for
>>>>>>> further review and may be re-opened, with cause.
>>>>>>> 3. *At each release cycle*, a further list of tickets will be
>>>>>>> sorted based on which versions are affected. Versions older than THREE ago
>>>>>>> will be considered "non-active".
>>>>>>> 1. NB: This is a formalization of a practice we have, which
>>>>>>> is to deprecate older versions and encourage our users to upgrade to the
>>>>>>> most recent stable release. As we are on version 1.8 now, any issue
>>>>>>> affecting 1.4 or older would be "unsupported". As soon as we release 1.9,
>>>>>>> version 1.5 becomes "unsupported".
>>>>>>> 2. This led to a further discussion of release strategy -
>>>>>>> which I will start as a different thread. The main point being, if a
>>>>>>> release is no longer a supported release, then those tickets are to be
>>>>>>> archived.
>>>>>>> 4. *Issue Reporting and Cleanliness: *We will require the
>>>>>>> tickets to include "Version affected" and "Component" to be filled
>>>>>>> out. This allows the sorting above and provides for the ability
>>>>>>> to trace the origin of the issue. We also seek to have better ticket
>>>>>>> reporting, meaning a clear set of criteria for "Bug" vs
>>>>>>> "Configuration/Documentation" vs "New Feature".
>>>>>>> 5. We will hold a regular - monthly - issue triage meeting to
>>>>>>> coordinate on tickets.
>>>>>>> 6. We noted that many of the issues on the list and some of
>>>>>>> the Jira tickets are related to configuration and setup and suggest better
>>>>>>> knowledge base management. We are interested in people taking an active
>>>>>>> role in that.
>>>>>>> 7. *Release Cycles: *We noted that we have gotten a number of
>>>>>>> major improvements such that version 1.8 is very different from 1.5 (less
>>>>>>> than two years ago). A new topic is thus to move to a Major release cycle
>>>>>>> Version 2.0, and to consider a Long-Term-Support version of the Fineract1.x
>>>>>>> . I can kick that off on a new thread as well.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>> Disclaimer:
>>
>> Privileged & confidential information is contained in this message
>> (including all attachments). If you are not an intended recipient of this
>> message, please destroy this message immediately and kindly notify
>> the sender by reply e-mail. Any unauthorised use or dissemination of this
>> message in any manner whatsoever, in whole or in part, is strictly
>> prohibited. This e-mail, including all attachments hereto, (i) is for
>> discussion purposes only and shall not be deemed or construed to be a
>> professional opinion unless expressly stated otherwise, and (ii) is not
>> intended, written or sent to be used, and cannot and shall not be used, for
>> any unlawful purpose. This communication, including any attachments, may
>> not be free of viruses, interceptions or interference, and may not be
>> compatible with your systems. You should carry out your own virus checks
>> before opening any attachment to this e-mail. The sender of this e-mail and
>> *Fynarfin Tech Private Limited* shall not be liable for any damage that
>> you may sustain as a result of viruses, incompleteness of this message, a
>> delay in receipt of this message or computer problems experienced.
>>
>