separate releases by db functionality

[Ilhan-Personal]

Important

Please provide the requested parameters below to help us review your pull request.

Pull requests without a body or explanation will be rejected.

Describe your changes

Issue ticket number and link

Closes #

Checklist before requesting a review

• I have performed a self-review of my code
• If it is a core feature, I have added tests.
• I have run make check and there are no failures.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

[pouriyajamshidi]

ooofff yea, no 😄
let's put this on hold till the refactoring

[Ilhan-Personal]

True felt the same too 😅 Shall I take up the refactoring?

[pouriyajamshidi]

True felt the same too 😅 Shall I take up the refactoring?

not yet. I am discussing it internally to see what structure would kinda save us less refactoring in the future.

will keep you posted

[pouriyajamshidi]

ok, we had a discussion and I will do some preliminary refactoring of the project structure, enabling others to chime in and improve it further.

That will happen after the 2.7.0 release which I aim to be this weekend.

[Ilhan-Personal]

Sounds good @pouriyajamshidi Happy to help in any way :)