You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by Aleksandar Vidakovic <ch...@monkeysintown.com> on 2025/10/28 11:28:36 UTC
New command processing self assignments...
Hi Kapil,
... I'd like to ask you a favor and stop for a moment self assigning
yourself to tickets related to the new command processing... I randomly
opened one of the tickets you put yourself on to (FINERACT-2290) and just
saw closed pull requests associated with it.
This is creating quite some noise and I honestly don't have any overview
anymore of what is being worked on. I think I already suggested to you to
have one PR properly reviewed... and if that one passes then let's assign
another one. I still have a feeling that not everything is clear here. Your
current multi-tasking approach creates more work than necessary. So please
choose one (I think we agreed already on one), let's finish this from top
to bottom and then let's move to the next one.
I am also working on a large chunk of these tickets and Yu also took on one
ticket. There is no need for duplicate work.
Thanks,
Aleks
Re: New command processing self assignments...
Posted by Kapil Panchal <ka...@gmail.com>.
Hi Aleks,
Sure, these are old tickets and are closed. The one that I need clarity on
is this ticket https://github.com/apache/fineract/pull/5126, I agree to
complete this ticket first.
Thanks,
Kapil
On Tue, Oct 28, 2025 at 4:58 PM Aleksandar Vidakovic <
cheetah@monkeysintown.com> wrote:
> Hi Kapil,
>
> ... I'd like to ask you a favor and stop for a moment self assigning
> yourself to tickets related to the new command processing... I randomly
> opened one of the tickets you put yourself on to (FINERACT-2290) and just
> saw closed pull requests associated with it.
>
> This is creating quite some noise and I honestly don't have any overview
> anymore of what is being worked on. I think I already suggested to you to
> have one PR properly reviewed... and if that one passes then let's assign
> another one. I still have a feeling that not everything is clear here. Your
> current multi-tasking approach creates more work than necessary. So please
> choose one (I think we agreed already on one), let's finish this from top
> to bottom and then let's move to the next one.
>
> I am also working on a large chunk of these tickets and Yu also took on
> one ticket. There is no need for duplicate work.
>
> Thanks,
>
> Aleks
>