Hi All, I want to share few concerns regarding the usage of JIRA during the release process. I think a lot of things and contributions are duplicated and scattered across different areas. Github for PR review, jira for tracking issues and then dev list for discussions.
Currently, several aspects of JIRA usage are slowing down our processes. 1. New Contributor Onboarding - As the project grows within the community, many contributors are requesting JIRA account approval, and I think PMC members are currently approving those manually. 2. Tracking and referencing them for closure - During part of release process. One of the crucial step of release process documented at https://fineract.apache.org/docs/develop/#_release_process is to freeze JIRA and cleanup the JIRA for include issues that are merged for the specific release. As JIRA issues gets piled up and need to manually review each linked PR and close them. (This is one of the longer steps) 3. After the release vote period, both JIRA and GitHub need updating. I wanted to start a discussion so we can make this process more efficient. I think it is the right time to discuss this as we are finishing up the current release vote. I wanted to hear what the community thinks about this before proposing anything. Regards Aman
