Alex, I would like to see and understand the steps we need to take w regard to quality assurance (QA). It is vital that we have enough test coverage. If we don't have that, then we may need to hold off on the release until we do.
In previous releases we always relied heavily on users going through each user interface screen to identify bugs. There were even bug finding rewards. This was true for the decade + that the code lived as Mifos. Since the Mifos front end UIs (multiple) are not yet at the same development state, I believe we need to make sure that test coverage is adequate at the unit level and end to end level. Perhaps other devs could tell is what has been done to ensure the QA is there. If there are additional testing needs, let's also make sure we have jira tickets for those. If the Mifos UIs on the Mifos dev branches are tracking w this 1.4 release exactly, then perhaps that can be used for the testing here. QA should also include a look at any security issues that were solved. Thanks, @jdailey On Fri, Aug 21, 2020, 5:42 AM Aleksandar Vidakovic < [email protected]> wrote: > Hi Everyone, > > As previously announced, I've just created the release branch for our > upcoming 1.4.0 release. > > You can continue working and merging PRs to the develop branch for future > releases, as always. > > The DRAFT release notes are on > https://cwiki.apache.org/confluence/display/FINERACT/1.4.0+-+Apache+Fineract. > Does anyone see anything missing? > > Does anyone have any last minute changes they would like to see > cherry-picked to branch 1.4.0, or are we good to go and actually cut the > release based on this branch as it is? > > I'll start the final stage of actually creating the release in 3 days > (Monday, August 24) if nobody objects. > > Cheers, > > Aleks > >
