FINERACT-1106 reschedule-loan-first-pay-day-holiday-fix#1209
FINERACT-1106 reschedule-loan-first-pay-day-holiday-fix#1209avikganguly01 merged 1 commit intoapache:developfrom
Conversation
42266f2 to
a0e89dd
Compare
|
@avikganguly01 knowing that @fynmanoj works with you, and assuming that you are still an active committer to this project (are you?), I was wondering if you would like to engage on code review feedback and possible evental merge of PRs such as this one? (I don't want to be a bottleneck on this project, and won't have the spare time to help review changes like this. If there are other active commiters such as @awasum @ptuomola @xurror or others reading this who want to engage on this PR, please don't let me hold you up / wait for me - I'll ignore this one, and try to help on others.) |
|
@fynmanoj this PR needs to have a JIRA issue on the ASF JIRA, instead of referencing an issue on https://mifosforge.jira.com. |
|
We are planning to move all the tickets to fineract tracker, and I will
correct the PR issues parallelly
…On Sat, 1 Aug, 2020, 19:44 Michael Vorburger ⛑️, ***@***.***> wrote:
@fynmanoj <https://github.com/fynmanoj> this PR needs to have a JIRA
issue on the ASF JIRA, instead of referencing an issue on
https://mifosforge.jira.com.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1209 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANQLL2W5UMCPED3B7XJRWPDR6QPKZANCNFSM4PLWWUPQ>
.
--
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.
|
|
@vorburger I opened up tickets on JIRA for these pull requests and referenced them in the title of the PR. I tagged @avikganguly01 as a reviewer and assume he can do the needful in reviewing and merging the PRs as we are going to start testing this development branch with these pull requests merged on the user's test server. |
Description
Describe the changes made and why they were made. Ignore if these details are present on the associated Jira ticket at https://issues.apache.org/jira/browse/FINERACT-1106
Originally listed at https://mifosforge.jira.com/browse/AL-2
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!
Commit message starts with the issue number from https://issues.apache.org/jira/projects/FINERACT/. Ex: FINERACT-646 Pockets API.
Coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions have been followed.
API documentation at fineract-provider/src/main/resources/static/api-docs/apiLive.htm has been updated with details of any API changes.
Integration tests have been created/updated for verifying the changes made.
All Integrations tests are passing with the new commits.
Submission is not a "code dump". (Large changes can be made "in repository" via a branch. Ask on the list.)
Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide