Hi, I have couple of questions, For testing the issues I need jira access. I already created my account in jira [email protected], is that I can use for testing ? I need to test the issues under resolved status? eg. https://issues.apache.org/jira/browse/FINERACT-957. assign to myself ? Is the issues under resolved status are moved to https://staging.mifos.io/#/
I saw there are 31 issues under resolved status in 1.4.0 release Regards, Subbu On Tue, May 5, 2020 at 1:41 AM Ed Cable <[email protected]> wrote: > James, > > Thanks for bringing this thread top of mind, the issues that we were > previously waiting to get fixed have luckily been fixed and merged. I don't > think we need to wait on all those tickets in the filters you listed. > Here's my take on what was in the two filters you shared. Concerning > release manager, we're trying to pin that down for this cycle - @Nazeer > Hussain Shaik <[email protected]> @Steve Conrad > <[email protected]> are you able to take that on this > cycle? > > For QA, I'll work with @Santosh Math <[email protected]> > and [email protected] and any other willing participants from the > community. > > Of the in-progress issues > https://issues.apache.org/jira/browse/FINERACT-919?jql=project%20%3D%20FINERACT%20AND%20fixVersion%20%3D%201.4.0%20AND%20statusCategory%20%3D%20indeterminate > > We should wait to include: > > *Pull Requests Merged* > - https://issues.apache.org/jira/browse/FINERACT-603 - Feedback has been > incorporated and addressed at https://github.com/apache/fineract/pull/738/ > - https://issues.apache.org/jira/browse/FINERACT-722 - Michael rebased > Dylan's PR and merged at https://github.com/apache/fineract/pull/671 > - https://issues.apache.org/jira/browse/FINERACT-730 - Michael and Awasum > have been swiiftly reviewing the work of Petri at > https://github.com/apache/fineract/pull/807 and it looks close to merge. > > *To be Included in 1.4.0* > https://issues.apache.org/jira/browse/FINERACT-894 - This is a P1 issue > that came up in our testing and Nazeer is working on a fix (this hadn't > been tagged with 1.4.0 so I tagged it). > https://issues.apache.org/jira/browse/FINERACT-893 looks ready to be > merged once @Manoj VM <[email protected]> fixes the failed build at > https://github.com/apache/fineract/pull/769 > > > *Do these need to be fixed for 1.4.0?* > https://issues.apache.org/jira/browse/FINERACT-914/ > https://issues.apache.org/jira/browse/FINERACT-915 @Michael Vorburger > <[email protected]> These don't need to be completed for 1.4.0, correct? > Likewise for Fineract 922, 926, 927, these shouldn't block the release? > https://issues.apache.org/jira/browse/FINERACT-906 - Same with this > Michael, we can wait, right? > https://github.com/apache/fineract/pull/762 - @Nazeer Hussain Shaik > <[email protected]> @Santosh Math > <[email protected]> are you able to look into this? > > Of the open issues at > https://issues.apache.org/jira/browse/FINERACT-904?jql=project%20%3D%20FINERACT%20AND%20fixVersion%20%3D%201.4.0%20AND%20statusCategory%20%3D%20new > > I think all those can go to a future release. @Santosh Math > <[email protected]> @Yannick Awasum > <[email protected]> want to start a regular triage session once > again? > > Perhaps we could include > https://issues.apache.org/jira/browse/FINERACT-821 in the 1.4.0 release? > > Once we address the issues above, we should be able to move into the > release process. @Steve Conrad <[email protected]> Do you > have some time to help with the above or below? > > > - Create Release Artifacts (from > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67640333 > ) > - Call for a Vote > - Upload artifacts, ship and announce release, and update website. > > > Ed > > Previous conversation > > On Wed, Mar 4, 2020 at 9:55 PM Ed Cable <[email protected]> wrote: > >> Hi all, >> >> Once we get to clarity on what is outstanding for this release, we can >> update the list on one of the various threads pertaining to this. As far as >> I can tell, we had fixed the outstanding issues that we wanted to see >> completed and hope that we're ready to call for a vote on this release - >> is that correct? >> >> https://issues.apache.org/jira/browse/FINERACT-820 >> >> Seems like for Fineract-802 ( >> https://issues.apache.org/jira/browse/FINERACT-802) we can merge >> https://github.com/apache/fineract/pull/664? >> > > PR: https://github.com/apache/fineract/pull/664 has now being merged into > Develop branch. > >> >> https://issues.apache.org/jira/browse/FINERACT-803, >> >> PRs 684 and 685 seem to have been merged. >> >> I would really like to get this out the door and then use the 1.5 release as >> a fresh slate to start to more actively get partner contributions and have >> a strong release cycle going forward. >> >> Following up on my January email, >> >> Nazeer, are you able to once again help with these tasks: >> Ed >> -- >> *Ed Cable* >> President/CEO, Mifos Initiative >> [email protected] | Skype: edcable | Mobile: +1.484.477.8649 >> >> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org >> <http://facebook.com/mifos> <http://www.twitter.com/mifos> >> >> > > On Sat, May 2, 2020 at 8:46 PM James Dailey <[email protected]> > wrote: > >> @Michael Vorburger <[email protected]> @Awasum Yannick >> <[email protected]> @Santosh Math <[email protected]> >> >> I see that there are a few thorny issues remaining to get to a 1.4.0 >> release. (71 issues closed!!!). >> >> So, if someone (like me, or others with more dev skill) has available >> TIME TO HELP, where should they spend their time? >> >> 9 jira issues in process: >> >> https://issues.apache.org/jira/browse/FINERACT-919?jql=project%20%3D%20FINERACT%20AND%20fixVersion%20%3D%201.4.0%20AND%20statusCategory%20%3D%20indeterminate >> >> 6 jira issues to do >> >> >> https://issues.apache.org/jira/browse/FINERACT-904?jql=project%20%3D%20FINERACT%20AND%20fixVersion%20%3D%201.4.0%20AND%20statusCategory%20%3D%20new >> <https://issues.apache.org/jira/browse/FINERACT-904?jql=project%20%3D%20FINERACT%20AND%20fixVersion%20%3D%201.4.0%20AND%20statusCategory%20%3D%20new> >> >> I think it would be a great goal to have this out by June 1st, 2020. >> >> Who is the release manager? >> Who is leading QA? >> >> @jdailey >> >> On Fri, Nov 22, 2019 at 6:08 PM Ed Cable <[email protected]> wrote: >> >>> Hello community, >>> >>> Just an update on the status of the release. We were awaiting changes to >>> be made to a number of open PRs that were to be merged. >>> >>> Some of those have fixes have remaining and will be part of the 1.5 >>> release: >>> >>> These include Fineract-428 >>> <https://issues.apache.org/jira/browse/FINERACT-428>, Fineract-614 >>> <https://issues.apache.org/jira/browse/FINERACT-614> and Fineract-609 >>> <https://issues.apache.org/jira/browse/FINERACT-609> >>> >>> The following tickets and their corresponding PRs are nearly completion >>> and to be merged for this release and then we'll move forward with a vote. >>> >>> https://issues.apache.org/jira/browse/FINERACT-773 >>> https://issues.apache.org/jira/browse/FINERACT-753 >>> https://issues.apache.org/jira/browse/FINERACT-724 >>> https://issues.apache.org/jira/browse/FINERACT-787 >>> >>> Thanks to @Yannick Awasum <[email protected]> and @Michael >>> Vorburger <[email protected]> @Santosh Math >>> <[email protected]> for all their work in reviewing PRs. >>> >>> >>> On Wed, Nov 13, 2019 at 7:00 AM Ed Cable <[email protected]> wrote: >>> >>>> Hello Fineract community, >>>> >>>> Final QA is underway on the Fineract 1.4 release and we've just >>>> sanitized JIRA, updating tickets that have been resolved for 1.4 and moving >>>> tickets that were't completed to the 1.5 release. >>>> >>>> These release notes have been published at https://s.apache.org/xivc8 >>>> >>>> They've also been added to the release page at >>>> https://wiki.apache.org/confluence/display/FINERACT/1.4.0+-+Apache+Fineract >>>> >>>> The following week will be used to complete QA on the last pull >>>> requests that have been merged. You can access the staging server located >>>> at https://staging.openmf.org (mifos/password) >>>> >>>> We aim to bring this release to a vote next week and then release it >>>> the following week. >>>> >>>> We will be sending out a separate email kicking off the planning >>>> process for Fineract 1.5. >>>> >>>> Cheers, >>>> >>>> Ed >>>> >>>> >>>> >>> >>> -- >>> *Ed Cable* >>> President/CEO, Mifos Initiative >>> [email protected] | Skype: edcable | Mobile: +1.484.477.8649 >>> >>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org >>> <http://facebook.com/mifos> <http://www.twitter.com/mifos> >>> >>> > > -- > *Ed Cable* > President/CEO, Mifos Initiative > [email protected] | Skype: edcable | Mobile: +1.484.477.8649 > > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org > <http://facebook.com/mifos> <http://www.twitter.com/mifos> > >
